Frequently Asked Questions (FAQs)

Yes, the customer can take a backup and upgrade the OS themselves, but, any issue arising due to upgradation is completely the customer’s responsibility and the backup needs to be maintained by the customer.

The customer will get full access to the machines so he can install any additional software and packages on the machine.

Yes, the customer can take a backup and upgrade the OS themselves, but, any issue arising due to upgradation is completely the customer’s responsibility and the backup needs to be maintained by the customer.

E2E Cloud has the standard SLAs mentioned at https://www.e2enetworks.com/policies/service-level-agreement. The general operational readiness to replace a server in case of physical hardware failures is around 30 mins on an average.

E2E Cloud provides standard block storage with multiple redundant copies in the backend. These block storage have a 1:1 mapping and can be attached to only one VM at a time.

Typically Intel/AMD with 2.5Ghz and above.

You can enable snapshots for block storage. For machines, you can set up a CDP backup.

E2E Cloud’s volumes are based on linstor/Drbd technology.

E2E Cloud does not have a step function equivalent.

E2E Cloud Storage data is not automatically available over E2E CLoud’s CDN. The customer would need to set up a CDN for the bucket that they intend to use.

E2E Cloud and CDN do support HTTP range requests.

At E2E Cloud, We follow standard API limits subjected to fair usage. Typically write and read depend on the object sizes and write/read the profile. Customers can let us know their concurrency expectations so that we can help further.

At E2E Object storage, we calculate the maximum usage of the bucket at any point in time. So, E2E will charge for 1 GB Object size only.

For HA, the customer needs to buy any C3/M3/SDC3 series which has quick failover in case of hardware issues.

Regarding Jitsi, its similar to big blue button and there are benchmarks available on the Jitsi site and a scalable system documented at https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-scalable
Suffice it to say, the customer needs to benchmark this and we haven't benchmarked for all configurations here.

We provide Kubernetes as a service but it's not managed in the traditional sense. We can support you if you are facing any issues related to the functioning of the cluster like a node not joined etc but we cannot support native Kubernetes issues. The master nodes are fault-tolerant by default.

Yes, E2E Cloud supports persistent storage based on CEPH. It's documented at https://docs.e2enetworks.com/kubernetes/kubernetes.html#persistent-volume-pvc. Once you add a persistent volume, you can use it from within k8s.

In E2E K8S, we use the concept of LB IP Pool. You can use the expose keyword after assigning an IP on the LB IP pool. Please refer to documentation at https://docs.e2enetworks.com/kubernetes/kubernetes.html#loadbalancer

Customers can continue to use docker hub itself for now. Alternatively, customer can setup a caching mirror using the documentation at https://docs.docker.com/registry/recipes/mirror/#how-does-it-work

Cpanel has many web servers available and has apache by default which is recommended by Cpanel. He can use any of the standard documents available on Cpanel site for WordPress hosting. something like this can also help:https://docs.cpanel.net/knowledge-base/third-party/how-to-install-wordpress-with-cpanel/

E2E Cloud doesn't have managed Cpanel plans. These are just instances with licensed Cpanel pre-installed. Cpanel has many web servers available and has apache by default which is recommended by Cpanel.

There is a separate process if a customer wants to bring their own IP and ASN. We don't support customer ASN on E2E IPs. If a customer wants his own ASN, he needs to route his own IPs on E2E Cloud for which there is a separate cost.

The document at https://learn.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2017?view=sql-server-ver16 explains the different versions of SQL and what's the features and limitations of each.

This is a breakdown of services of reporting service with respect to editions https://learn.microsoft.com/en-us/sql/reporting-services/reporting-services-features-supported-by-the-editions-of-sql-server-2016?view=sql-server-ver16

Redis has an enterprise plan which can be procured by the customer. Should be similar in cost. They can also use our C3/SDC3 instances for failover instances. Alternatively, customers can also use https://redis.com/redis-enterprise/redis-insight/ for management of the Redis cluster

Here at E2E Cloud, we recommend using apisix. https://apisix.apache.org.

The customer needs to procure an E2E firewall which is based on FortiGate which is on a chargeable basis. Please note that customers would incur outbound bandwidth costs on AWS.Please check the pricing of Cloud Firewall here:https://www.e2enetworks.com/pricing#Cloud-Firewall

The customer has to set up his/her own SIEM tool. https://www.elastic.co/security/siem is a good choice for a lot of deployments. It's a standard Linux setup and nothing specific to E2E.

Fortigate can be used to create a VPN tunnel between customer premises and a VPC on E2E Cloud created by the customer.

Cloud uses a single storage class with high IOPS instead of multiple storage classes. E2E Cloud uses CEPH provisioner in its persistent volume.

E2E Cloud has full-fledged APIs and a collection that is published on postman but as of now, E2E does not have ansible or terraform integration.

E2E’s servers are co-located in Netmagic’s DC in Noida and Mumbai regions. We can offer signed certificates with customers’ IPs for data localization proof.

Currently, E2E Cloud is not MEITY empaneled but we are in the process of getting it registered.  Please keep on checking the release notes for the latest updates:https://docs.e2enetworks.com/release.html

This has been a part of E2E Cloud’s roadmap and E2E Cloud will start providing an option for GPU with managed Kubernetes soon. Please keep on checking the release notes for latest
the updates:https://docs.e2enetworks.com/release.html

E2E Cloud GPUs provide basic images with nvidia drivers, cuda toolkit and other allied packages with integration to docker Ngc.E2E Cloud GPUs includes NVIDIA GPU driver and CUDA toolkit pre-installed for rapid onboarding.

It also bundles tools to deploy NVIDIA GPU Cloud(NGC) containers in 1 click.

Any other libraries, client can install by himself. 

‍Software Versions pre-installed:
‍NVIDIA Driver: 515.65v
‍CUDA : 11.7v
‍cuDNN : 8.4v
‍Python : 3.8.10v
‍Docker : 20.10v
‍NVIDIA-docker: 2.11v
NGC (NVIDIA GPU Cloud) CLI: 3.5v
Ubuntu Desktop: Xrdp [port:3389]

No, this feature is not available as of now. If a customer wants image backup, we can dump it on their S3 bucket from backend. Client can request by sending an email to cloud-platform@e2enetworks.com

Customer needs to do his own CI/CD setup using either GitHub actions assuming his code is on GitHub or using gitlab CI/CD.
Example: https://resources.github.com/ci-cd/. 
Customer has to setup a build process and automate his deployment. 

A customer can refer to the below API documentation to start and stop the GPU servers:
‍https://docs.e2enetworks.com/developersguide/api/index.html
‍https://documenter.getpostman.com/view/18257960/UzR1Khv6

A customer needs to check the process manager. It should show the correct number of cores assigned to the machine which the customer has got.

A customer can follow the instructions mentioned in the document below to resolve this issue.

‍https://docs.e2enetworks.com/gpucloud/gpu/faq_session.html?highlight=rds

 No. We don’t have the option of SAN storage as of now. For E2E customers, there are options of block storage and EOS only. 

No! There is no way to attach node and volume space.

Customer cannot resize E2E Block storage.

Every customer get 512 IPs by default per VPC.

E2E Cloud use either Intel or AMD processors. Please note that processor series/cpu is at the discretion of E2E and its subject to change based on availability.

Yes. Client has to take Cloud Firewall and VPC in both E2E Cloud and AWS cloud for this to happen.

Yes. We provide basic monitoring of resources like CPU, RAM, Disk and Network stats. We provide Zabbix monitoring tool for the same.

Follow below steps:

1. Install minio client (mc) using the document at https://docs.min.io/docs/minio-client-quickstart-guide.html the mc client needs to be install on E2E to fasten up transfer speeds

2. Enable interoperability mode in the GCP object browser and create a key. please refer to https://objectivefs.com/howto/how-to-get-google-cloud-storage-s3-interoperability-keys

‍3. Create a bucket on E2E EOS, create and assign keys to the bucket 

4. Setup GCP ObjectStorage on the linux machine as followsmc config host add gcpbucket https://storage.googleapis.com <GCP-Access-Key> <GCP-Secret-Key> --api S3v2
   
a. create a bucket on the GCP console   
b. list the bucket as follows#mc ls gcpbucket
‍
5. Setup E2E EOS on the same machine as follows mc config host add e2e https://objectstore.e2enetworks.net <E2E-Access-Key> <E2E-Secret-Key>   
‍
a. create a bucket on the E2E console 
b. list the bucket using #mc ls e2e

6. Start the transfer as follows
mc cp --recursive gcpbucket/bucketongcp e2e/bucketone2e

The customer can take E2E CDN. For WAF, he can add Bitninja to his instances which has a WAF module. 

Client needs to do his own CI/CD setup using either GitHub actions assuming his code is on GitHub or using gitlab CI/CD, something like this: https://resources.github.com/ci-cd/. Client has to setup a build process and automate his deployment. 

No. This is not possible currently with E2E Cloud. The solution for a client is to use custom scripts which can rsync a folder to EOS (E2E Object Storage).

Customized policies in terms of retention points are currently not possible in E2E CDP backup plan. Client can use EOS where they can configure lifecycle policies:
‍

https://docs.e2enetworks.com/storage/objectstore/object_storage.html#lifecycle-rule

Please check the following link for setting up CDP backup from E2E Cloud platform: https://docs.e2enetworks.com/storage/cdpbackup/cdpbackup.html

E2E Cloud use either Intel or AMD processors. Please note that processor series/cpu is at the discretion of E2E and its subject to change based on availability.

Saved image based recovery would involve creation of an image, then transferring the image to a secondary location and then creating a machine from that image. I

If the customer is looking for an actual DR solution, he needs to fire up additional instances in a secondary location, keep the code/DB in sync and flip them via DNS when required.  Saved image based recovery would take anything from 10-12 hours considering a 1 TB C2 plan.

Saved image based recovery would involve creation of an image, then transferring the image to a secondary location and then creating a machine from that image. I

If the customer is looking for an actual DR solution, he needs to fire up additional instances in a secondary location, keep the code/DB in sync and flip them via DNS when required.  Saved image based recovery would take anything from 10-12 hours considering a 1 TB C2 plan.

Saved image based recovery would take anything from 10-12 hours considering a 1 TB plan.

AWS doesn't support adding instances from external providers on sagemaker.

We can use reserved IP to migrate traffic from one machine to another.

An alternative is to use an E2E LB, where customers can launch an internal load balancer.

Internal Load Balancer: The Internal Load Balancer has only a private IP address and can only route requests from clients over the private subnets only to the backend node that is registered with the Load Balancer.

This can be used to have a permanent IP for your service and the backend can be changed as per requirement. 

All outbound traffic from VPC will have a unique IP for that customer that can be used to whitelist with any other vendors if the customer wants.

For more security, Client can also take a Cloud Firewall with static public IP and connect it with more than one VPC within the E2E Cloud.

This static public IP of Cloud firewall can be used to whitelist with any other vendors if the customer wants.

Client can take the help of these articles to setup SSL VPN on Fortinet Appliance:
‍
‍https://docs.fortinet.com/document/fortigate/6.0.0/cookbook/690301/configuring-the-ssl-vpn-tunnel 
‍
‍https://www.youtube.com/watch?v=IFqsfz6Bto0 Download SSL Client. 

‍https://drive.google.com/drive/u/0/folders/1bCjuuZgOLUtp80NC-Xbst8n1uW-IkOBZ

The customer needs to manage EOS by themselves. 

Yes. Please check this sample MySQL backup script: 

https://docs.e2enetworks.com/storage/objectstore/mysql_backup.html