Transit VPC
A hub-and-spoke architecture where a central VPC (transit VPC) connects multiple other VPCs and on-premises networks using VPNs or Direct Connect.
- Transit VPC is a user-implemented custom solution that involves setting up a central VPC as a hub for connecting multiple VPCs and on-premises networks in a hub-and-spoke model.
- The central VPC contains third-party VPN appliances (typically virtual instances running on EC2).
- Unlike Transit Gateway, AWS does not manage or automate the setup of Transit VPCs.
- Users are responsible for deploying, configuring, and maintaining the VPN appliances and the networking architecture.
Use Case:
- You need to connect multiple VPCs or hybrid environments but do not yet use Transit Gateway.
- Centralized control with third-party appliances (e.g., Cisco, Palo Alto) is required for advanced network functionality.
- You are already leveraging third-party VPN appliances in a hub-and-spoke model.
Example
Managing hybrid networks with advanced monitoring or security requirements.
Key Takeaway
- Transit Gateway: Preferred for modern cloud architectures due to its AWS-managed nature, scalability, and ease of use.
- Transit VPC: Still a valid option when specific third-party VPN or networking tools are needed but comes with higher maintenance and complexity.