Shared VPCs and Multi-Account Networking
What you'll learn: How to share network resources across multiple cloud accounts while keeping them logically separated and governed.
Why Share Network Resources?
As organizations grow, they often manage dozens or hundreds of cloud accounts—one per team, environment, or business unit. Creating a separate VPC in each account can lead to fragmented networks, IP address conflicts, and management nightmares. Shared VPCs solve this by letting one central account own and manage network infrastructure, while other accounts can use those networks without owning them.
How It Works
Think of a shared VPC like an apartment building. The building owner (central networking team) manages the infrastructure—hallways, elevators, utilities. Tenants (application teams in different accounts) get their own apartments (subnets or portions of subnets) but don't manage the shared plumbing or electrical systems.
In practice:
- A central networking account creates and owns the VPC
- Participant accounts get permission to launch resources (like EC2 instances) into specific subnets
- Security groups, route tables, and internet gateways remain centrally managed
- Each account's resources stay isolated via security groups and IAM policies
Key Benefits
- Centralized governance: Network admins control routing, DNS, and connectivity patterns
- Reduced complexity: No need for dozens of VPC peering connections
- Cost efficiency: Share NAT gateways, VPC endpoints, and Transit Gateways
- Consistent security: Enforce uniform network ACLs and flow logs across all accounts
Key Takeaway: Shared VPCs enable multi-account architectures to share network infrastructure centrally while maintaining account-level resource isolation and billing separation.