Frequently Asked Questions

Q: Do I have to run ATCM in a VPC?

Yes, it is required.

Q: Does ATCM work in a private VPC?

Yes, you can use ATCM in a private VPC. For more information, see Running the Cluster Manager in a Private VPC.

Q: Do we require the use of Elastic IP addresses?

No. It is not required. ATCM supports Elastic IP addresses for customers who require whitelisting IP addresses.

Q: How will Route 53 work with VPC?

Route 53 can assign both public and private IPs. To configure Route 53 for a private IP, edit your Cluster Configuration and modify the "dns_manager_config" section:

...  
"dns_manager_config": {    
    "type":"AWS_Route 53",
    "dns_names": {
          "all_public": "c1-all",     
          "available_public": "c1",
          "all_private": "c1-all-prv",   
          "available_private": "c1-prv" 
    },    
    ...  
},  
...

Q: Can the cluster run servers in multiple availability zones?

Yes, if the cluster is launched into a VPC defined with multiple subnets in different availability zones. ATCM automatically distributes nodes across all VPC subnets defined in the cluster configuration in a round-robin fashion.

Q: Where can I find the the API docs for the cluster manager?

You can access the API docs via the cluster manager at

https://atcm_hostname:4999/docs/#!/