Question

A company runs production workloads across three AWS accounts in us-east-1 and is expanding into eu-west-1 to serve European customers. Each region already has a Transit Gateway shared with member accounts via AWS RAM, connecting dozens of VPCs. The networking team needs private, high-bandwidth connectivity between VPCs in the two regions so that application tiers can communicate without traversing the public internet. They want to minimize operational overhead and avoid managing separate encryption appliances. Which approach best meets these requirements?

Accepted Answer

Establish a Transit Gateway inter-region peering attachment between the us-east-1 and eu-west-1 Transit Gateways, then add static routes in each TGW route table pointing to the peering attachment for the remote region's CIDRs.

Answer

Create VPC peering connections between every VPC in us-east-1 and every VPC in eu-west-1, and update each VPC route table with routes to the remote VPC CIDRs.

Answer

Deploy Site-to-Site VPN connections over the public internet between the two Transit Gateways and enable BGP for dynamic route propagation across regions.

Answer

Provision AWS Direct Connect gateways in both regions and associate each Transit Gateway to enable inter-region routing through the Direct Connect backbone.