How to ensure successful cluster creation & management [BYOC]

There are several reasons a cluster could get stuck at "Creating" like the below. 

One of the prominent reasons could be due to the ScaleGrid agent not being able to communicate with the VM(s) being created due to firewall configuration issues in your cloud profile.

Symptoms

1. Typically, the cluster creation process will exceed 60 minutes.

2. The creation process will eventually fail with an exception 

Exception: An error occurred while communicating to the agent on server XX-XX-XX86X(IP:)

3. Support actions do not succeed in recovering the server(s) when in the failed state as a result of being unable to complete the server creation task.

Recommendation

To mitigate the issue related to the firewall/security/network configuration in your cloud profile, please make sure you have all the IP ranges below open for the ScaleGrid servers to be able to communicate with the 'agents' in those VMs, so we can manage smoothly the new clusters you want to create. 
 
The agent in the VMs must have:
 
Connectivity to TCP port 80 with servers:

52.1.125.87
13.58.72.37
52.41.150.71
35.155.95.238
54.237.160.204
18.191.62.220

 
Connectivity to TCP port 443 with servers:

52.1.125.87
13.58.72.37
52.41.150.71
35.155.95.238
54.237.160.204
18.191.62.220

 
Connectivity to TCP port 5671 with servers:

msgserver1.servers.mongodirector.com
msgserver2.servers.mongodirector.com
msgserver3.servers.mongodirector.com

 
For monitoring, please allow outgoing traffic TCP port 443 for:

159.223.109.80 
104.248.5.85

These IPs are associated with monitoring.scalegrid.io

---

NOTE: Always delete clusters that failed during the creation process since they cannot be recovered.

Should the issue persist after making changes to the firewall configuration, please Submit a support request via the ScaleGrid Support Portal. Alternatively, email the ScaleGrid Support Team at [e-mail].