Best Practices

Cloud Suite load balances using the public IP address from your egress (public) gateway or the connecting IP address. To help ensure best performance from the web service, your egress gateway should have a sufficiently large enough external IP addresses pool so that requests will be spread across multiple Cloud Suite web nodes. Typically, the IP address pool would have at least 8 unique external IP addresses.

Cloud Clients Scalability Egress

While every environment is different, in general, if using Remote Desktop Protocol or remote SSH, for every 200 Cloud Clients, you should have 2 connectors and each connector should have 2 to 4 external IP addresses. In environments where the Connectors do not handle large amounts of SSH/RDP or LDAP traffic, one Connector serves as a proxy for 500 Cloud Clients without degradation. Unique IP addresses optimize for best load balancing performance.

Also, routing multiple Cloud Clients through a single gateway can undermine load balancing efforts.

Cloud Connector Scalability Egress

Connectors could serve as a gateway for many systems on your local networks. It is advised that adding more public IP addresses will improve the likelihood that a connector's web traffic is properly distributed across the service. The recommended ratio is 8 public addresses for every 2 connectors.