A healthcare provider operates a multi-account AWS environment with spoke VPCs in the `us-west-2` Region and spoke VPCs in the `us-east-1` Region. The provider requires a private, high-bandwidth hybrid network configuration to connect all VPCs to their on-premises data center. The connection must use a primary AWS Direct Connect connection and a backup AWS Site-to-Site VPN connection. The architecture must allow all VPCs to communicate with the on-premises network and with each other. Which architecture and routing strategy will meet these requirements with the least administrative overhead?
- Provision a Transit Gateway in each Region, attach the local VPCs to their respective Transit Gateway, and peer the two Transit Gateways. Link a central Direct Connect Gateway with both Transit Gateways to terminate the primary Direct Connect connection, and establish a Site-to-Site VPN connection to each Transit Gateway as a backup. Advertise on-premises routes via BGP over both paths, prepending the AS path on the VPN to ensure the Direct Connect path is preferred.Cevap
- BLink a central Direct Connect Gateway directly with the Virtual Private Gateway (VGW) of all VPCs to establish the primary connection, and set up a Site-to-Site VPN connection to each VGW as a backup. Rely on BGP routing to prefer the Direct Connect path over the VPN connection for all hybrid and inter-VPC traffic.
- CProvision a single AWS Transit Gateway in the primary Region and attach all VPCs across both Regions directly to this Transit Gateway. Link a central Direct Connect Gateway with the Transit Gateway for the primary connection, and configure a Site-to-Site VPN connection to the Transit Gateway as a backup. Use BGP routing to manage failover between the paths.
- DEstablish a full mesh of VPC Peering connections among all VPCs to handle inter-VPC traffic. Link a central Direct Connect Gateway associated with a Virtual Private Gateway (VGW) in each VPC for primary hybrid connectivity, and configure a backup Site-to-Site VPN connection to each VPC's VGW. Configure BGP path attributes to prefer the Direct Connect connections.
Cevap
Provision a Transit Gateway in each Region, attach the local VPCs to their respective Transit Gateway, and peer the two Transit Gateways. Link a central Direct Connect Gateway with both Transit Gateways to terminate the primary Direct Connect connection, and establish a Site-to-Site VPN connection to each Transit Gateway as a backup. Advertise on-premises routes via BGP over both paths, prepending the AS path on the VPN to ensure the Direct Connect path is preferred.
The correct architecture uses local Transit Gateways in each Region, peered together to support inter-Region VPC communication. For hybrid connectivity, a central Direct Connect Gateway is linked with both Transit Gateways, and a backup Site-to-Site VPN is configured on each Transit Gateway. By prepending the AS path on the VPN connection, BGP routing naturally prefers the shorter AS path of the Direct Connect connection for outbound and inbound traffic, providing automated failover.
Adım Adım Çözüm
Anahtar Kavram
Multi-region hybrid network design with Transit Gateway peering, Direct Connect Gateway, and BGP failover.