Question

A media company runs 12 AWS accounts, each with its own VPC in us-east-1. Currently every VPC is connected to every other VPC using VPC peering, creating a full-mesh topology that has become difficult to manage as new accounts are added. The networking team wants to reduce operational overhead, enable centralized route management, and allow new accounts to connect to all existing VPCs without creating dozens of new individual connections. The solution must keep all traffic on the AWS backbone and support transitive routing between VPCs. Which approach best meets these requirements?

Accepted Answer

Deploy a Transit Gateway in a central networking account, share it with the organization using AWS Resource Access Manager (RAM), and attach each VPC to the Transit Gateway.

Answer

Continue using VPC peering but consolidate the peering connections into a single hub VPC that all other VPCs peer with, relying on the hub for transitive routing.

Answer

Create AWS PrivateLink endpoint services in each account and connect them so that every VPC can reach every other VPC's resources.

Answer

Establish a Site-to-Site VPN between each pair of accounts through a customer gateway to centralize connectivity.