An enterprise is reviewing its existing AWS network setup to optimize performance and latency. The architecture consists of multiple VPCs, including a shared services VPC containing a Route 53 Private Hosted Zone (PHZ) for internal service discovery. The instances in the private subnets of a new application VPC need to download software updates from the internet and resolve DNS names hosted in the shared services VPC. Currently, they experience high inter-zone latency and name resolution failures. Which two actions should the solutions architect take to resolve these issues and optimize performance?
- Deploy a NAT Gateway in each Availability Zone and configure the route tables of the private subnets to route outbound traffic through the NAT Gateway in their respective zone.Answer
- Associate the Route 53 Private Hosted Zone of the shared services VPC with the new application VPC to allow local, low-latency DNS resolution.Answer
- CConfigure all private subnets across multiple Availability Zones to route outbound internet traffic through a single NAT Gateway deployed in a single Availability Zone to reduce costs.
- DEstablish VPC peering between the VPCs and rely on the default VPC DNS server without associating the Route 53 Private Hosted Zone with the new application VPC.
- EConfigure a Direct Connect gateway to route transitive traffic directly between the VPCs to handle internal service name resolution and data transfer.
Answer
Deploy a NAT Gateway in each Availability Zone and associate the Route 53 Private Hosted Zone of the shared services VPC with the new application VPC.
Deploying a NAT Gateway in each Availability Zone ensures that outbound traffic stays within the same zone, eliminating cross-AZ latency and improving overall performance and availability. Explicitly associating the Route 53 Private Hosted Zone of the shared services VPC with the new application VPC allows resources in the application VPC to perform local and low-latency DNS resolution for internal services.
Step-by-Step Solution
Key Concept
Optimizing multi-VPC network latency and redundancy by utilizing local NAT Gateways per Availability Zone and associating Route 53 Private Hosted Zones with consumer VPCs.