A media company is establishing a new environment in the ap-northeast-1 Region, consisting of two spoke VPCs (vpc-media-ingest and vpc-media-process) across two Availability Zones, and a shared services VPC (vpc-shared-core). The spoke VPCs require outbound-only internet connectivity for updates. They also need to resolve internal DNS names in a Route 53 Private Hosted Zone (media.internal) created in the shared services VPC. An AWS Transit Gateway is deployed to interconnect all three VPCs. Which configuration should the solutions architect implement to satisfy these requirements while ensuring high availability for outbound traffic?
- ADeploy a single NAT Gateway in one Availability Zone of the shared services VPC. In the spoke VPC route tables, point the default route to the Transit Gateway. In the Route 53 console, associate the Private Hosted Zone with the shared services VPC and both spoke VPCs.
- BDeploy one NAT Gateway in each Availability Zone of the shared services VPC. In the spoke VPC route tables, point the default route to the Transit Gateway. Associate the Private Hosted Zone only with the shared services VPC, relying on Transit Gateway routing to automatically resolve DNS queries from the spoke VPCs.
- Deploy one NAT Gateway in each Availability Zone of the shared services VPC. In the spoke VPC route tables, point the default route to the Transit Gateway. In the Route 53 console, associate the Private Hosted Zone with the shared services VPC and both spoke VPCs.Cevap
- DAttach the spoke VPCs directly to a Direct Connect Gateway to enable transitive spoke-to-spoke network routing and shared internet egress via the shared services VPC, and associate the Private Hosted Zone with all VPCs.
Cevap
Deploy one NAT Gateway in each Availability Zone of the shared services VPC, point the spoke VPC route tables default route to the Transit Gateway, and associate the Route 53 Private Hosted Zone with the shared services VPC and both spoke VPCs.
Deploying one NAT Gateway per Availability Zone in the shared services VPC ensures Availability Zone redundancy for outbound internet traffic. Associating the Route 53 Private Hosted Zone with all VPCs enables name resolution across the entire environment because Private Hosted Zones are not transitively resolvable across VPC associations via Transit Gateway alone. This design fully achieves high availability and correct DNS resolution.
Adım Adım Çözüm
Anahtar Kavram
Designing highly available centralized egress architectures and configuring cross-VPC DNS resolution using Route 53 Private Hosted Zones.