An enterprise is designing a new network architecture in the `us-east-1` region to support three spoke VPCs (`vpc-prod`, `vpc-dev`, and `vpc-test`) and a central egress VPC (`vpc-egress`). An AWS Transit Gateway (`tgw-central`) connects all four VPCs. The workloads in the spoke VPCs are distributed across two Availability Zones ( and ) and require outbound internet access to download software updates. The design must ensure that the failure of a single Availability Zone does not disrupt outbound internet connectivity for any of the workloads, while minimizing overall NAT Gateway costs. Which of the following architectures should the Solutions Architect recommend?
- Deploy two NAT Gateways in `vpc-egress`, with one in a public subnet in and the other in a public subnet in . Configure the Transit Gateway route table to route traffic from the spoke VPCs to the `vpc-egress` attachment. Within `vpc-egress`, configure the route tables of the Transit Gateway subnets in each Availability Zone to route outbound traffic to the local NAT Gateway in the same zone.Cevap
- BDeploy a single NAT Gateway in `vpc-egress` in a public subnet in . Configure the Transit Gateway route table to route all traffic from the spoke VPCs to the `vpc-egress` attachment. Within `vpc-egress`, configure the route tables of the Transit Gateway subnets in both and to route outbound traffic to this single NAT Gateway.
- CDeploy two NAT Gateways in `vpc-egress`, with one in and one in . In the spoke VPCs, associate a Route 53 Private Hosted Zone (PHZ) for the update endpoints with `vpc-egress` only. Rely on the Transit Gateway to transitively forward the DNS queries from the spoke VPCs to the PHZ associated with `vpc-egress` to resolve update endpoint domain names.
- DDeploy two NAT Gateways in `vpc-egress` across and . Instead of using AWS Transit Gateway, configure AWS Direct Connect Gateway to establish transitive routing connections between the spoke VPCs and the central egress VPC for all outbound internet traffic.
Cevap
Deploying two NAT Gateways in the central egress VPC (one in each Availability Zone) and routing traffic from the spoke VPCs through the Transit Gateway to the egress VPC, where zone-specific routing directs traffic to the local NAT Gateway.
The correct architecture centralizes outbound internet egress in a shared `vpc-egress` VPC by deploying two NAT Gateways across two Availability Zones ( and ). Outbound traffic from the spoke VPCs is sent to the AWS Transit Gateway, which routes it to the egress VPC. By configuring the route tables in `vpc-egress` to send traffic from the Transit Gateway subnet attachment in each zone to the corresponding local NAT Gateway, the architecture ensures full Availability Zone redundancy while keeping the NAT Gateway count to a minimum of two instead of deploying two per spoke VPC.
Adım Adım Çözüm
Anahtar Kavram
Centralized egress VPC architecture with multi-AZ NAT Gateway redundancy and Transit Gateway routing.
Tahmini Süre:2m 0s