This section discusses the steps to configure the Controller Cluster in AWS.

To provide high availability (HA) for the Controller, add two additional Controller nodes to create a 3-node Controller cluster. For detailed instructions to configure an NSX Advanced Load Balancer, see Deploying an NSX Advanced Load Balancer Controller Cluster.

In AWS environments, AWS Availability Zones (AZs) provide redundancy and separate fault domains. All AWS regions support a minimum of two AZs. To leverage the HA provided by AWS AZs, it is recommended to deploy different Controller instances of a cluster in different AZs.

Managing a Controller Cluster across AZs

Each Controller receives an IP address from a different subnet given that an AWS subnet does not span across AZs.

In this scenario, it is recommended to create an FQDN in AWS Route 53 and associate all three Controller IPs with this FQDN. In addition, Route 53 health checks can be used in conjunction with multivalue routing when the FQDN is added to a public zone. This ensures that only healthy controller IPs are returned.

For AWS deployments where Controllers are on different subnets, Route 53 configuration with health checks enables resolving the Cluster's domain name to a Controller IP address directly. For detailed information on cluster configuration in AWS, see the Controller Cluster Configuration in AWS.