Customers may wish to use a multi-cloud deployment strategy when using Cloudmersive Private Cloud and Cloudmersive Managed Instance products. There are several possible configurations:

• Multiple Customer-Managed Private Cloud Deployments: This could, for example, be multiple regions within one cloud such as AWS, or multiple clouds such as AWS and Azure, all running Cloudmersive Private Cloud on customer managed infrastructure

• One or More Customer-Managed Private Cloud Deployments and Cloudmersive Managed Instance: This scenario is similar to the previous one, but in addition to customer-managed infrastructure, Cloudmersive Managed Instance is also used. This infrastructure differs because it is managed by Cloudmersive.

Both deployments are possible using the Cloudmersive Reverse Proxy product as a load balancer across all regions and clouds, which can be deployed on-premises on customer-owned infrastructure or it can be provided as a managed service.

Option 1: Managed Load Balancing

In this option, Cloudmersive Reverse Proxy is deployed and managed by Cloudmersive as a Managed Instance. Traffic is load balanced across the customer Managed Instance(s) if any, as well as customer managed Private Cloud servers. IP whitelisting is used to limit access to the origin servers to only the Reverse Proxy load balancing server. This server will maintain an active-active DR failover with DNS load balancing to ensure redundancy in the event a region goes down. Cloudmersive Reverse Proxy operates over HTTPS and will be configured with TLS 1.2.

Option 2: Customer-Deployed Load Balancing

In this option, Cloudmersive Reverse Proxy is deployed by the customer using Cloudmersive Private Cloud. Reverse Proxy Server is installed on one or more VMs or Kubernetes Containers in one or more regions. Traffic is load balanced across the customer Managed Instance(s) if any, as well as customer managed Private Cloud servers. IP whitelisting is used to limit access to the origin servers to only the Reverse Proxy load balancing server. This server will maintain an active-active DR failover with DNS load balancing to ensure redundancy in the event a region goes down. Cloudmersive Reverse Proxy operates over HTTPS and will be configured with TLS 1.2.

AWS Best Practices

For AWS, Active-Active DR failover is achieved using Route 53 health checks. Each Reverse Proxy Server exposes a healthcheck endpoint that can be used for this purpose.