Question

A company currently connects 6 VPCs in a single Region using VPC peering in a full-mesh topology. Over the next year they plan to grow to approximately 40 VPCs, all of which must be able to communicate with each other and with a shared services VPC hosting central logging and authentication. The networking team wants to minimize the number of connections they must manage and avoid the operational burden of updating route tables across every VPC as new VPCs are added. Which connectivity design BEST meets these requirements?

Accepted Answer

Deploy a Transit Gateway and attach each VPC to it, using Transit Gateway route tables to control routing between the VPCs and the shared services VPC.

Answer

Continue with full-mesh VPC peering and use a script to automatically create peering connections and route table entries as new VPCs are added.

Answer

Create a hub VPC and configure VPC peering from every spoke VPC to the hub, relying on the hub to route traffic transitively between spokes.

Answer

Use AWS PrivateLink endpoint services in each VPC to expose applications to all other VPCs across the environment.