QuestionQ64

VerifiedDesign Solutions for Organizational Complexity

A company is designing its network configuration in the AWS Cloud. It uses AWS Organizations to manage a multi-account environment. The company has three OUs. Each OU contains more than 100 AWS accounts. Every account has one VPC, and all VPCs within each OU are in the same AWS Region.

The CIDR ranges of all AWS accounts do not overlap. The company needs a solution where VPCs within the same OU can communicate with one another, but cannot communicate with VPCs in other OUs.

Which solution meets these requirements with the LEAST operational overhead?

Explanation

AWS Transit Gateway centrally routes traffic among attached VPCs across accounts. Deploying one transit gateway per OU creates separate routing domains: attachments within an OU can exchange routes through that OU’s gateway, while no gateway route or attachment connects them to another OU. AWS RAM can share each transit gateway with accounts in AWS Organizations so those accounts can create VPC attachments. This hub-and-spoke design scales far better operationally than creating a mesh of VPC peering connections. A peering-based hub VPC also cannot provide transitive spoke-to-spoke routing.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!