A company is designing a network architecture to connect spoke VPCs spread across AWS accounts in a single AWS Region. The architecture must support low-latency, any-to-any communication between the VPCs and provide a highly available, dedicated connection to their on-premises data center. The solutions architect must minimize administrative overhead and ensure that routing scales easily as new spoke VPCs are added. Which of the following architectures meets these requirements?
- ADeploy a centralized AWS Direct Connect Gateway and associate it directly with the virtual private gateways of all spoke VPCs using private virtual interfaces, relying on the Direct Connect Gateway to route traffic between the spoke VPCs and the on-premises data center.
- BEstablish a full mesh of VPC peering connections between all spoke VPCs to handle inter-VPC communication. Connect the on-premises data center to a central hub VPC using a Direct Connect Gateway and a transit virtual interface, and configure a Route Private Hosted Zone in the hub VPC without associating it with the spoke VPCs.
- Provision an AWS Transit Gateway in a centralized network account, share it with the other accounts using AWS Resource Access Manager (RAM), and attach the spoke VPCs. Associate the Transit Gateway with an AWS Direct Connect Gateway connected to the on-premises data center via a transit virtual interface.Cevap
- DCreate a hub-and-spoke topology by sharing a Transit Gateway across accounts. Connect the Transit Gateway to the on-premises data center using a Site-to-Site VPN. Route all outbound internet and hybrid traffic through a single NAT Gateway located in a central egress VPC's single Availability Zone to minimize NAT charges.
Cevap
Provision an AWS Transit Gateway in a centralized network account, share it with the other accounts using AWS Resource Access Manager (RAM), and attach the spoke VPCs. Associate the Transit Gateway with an AWS Direct Connect Gateway connected to the on-premises data center via a transit virtual interface.
The correct architecture leverages AWS Transit Gateway to act as a cloud router, providing any-to-any connectivity among the spoke VPCs. Sharing the Transit Gateway via AWS Resource Access Manager (RAM) allows the spoke VPCs in different accounts to attach to the same gateway seamlessly. To connect to the on-premises data center, a Direct Connect Gateway is associated with the Transit Gateway using a transit virtual interface (Transit VIF), which supports routing to multiple VPCs via the Transit Gateway over a dedicated, low-latency connection.
Adım Adım Çözüm
Anahtar Kavram
Hub-and-Spoke hybrid network design using Transit Gateway, RAM, and Direct Connect Gateway with a Transit VIF to achieve scale, transitive routing, and high availability.
Tahmini Süre:2m 0s