Information About Deploying Transit VPC
This is a summary about the deploying the three main components of the transit VPC design. To follow the detailed procedures, go to Launching a Transit VPC Hub.
- Launching a Transit VPC Hub
The first procedure deploys the transit VPC, which acts as the central hub for traffic flowing to other destinations (other VPCs or remote networks). The transit VPC hub hosts two Cisco CSR 1000v instances, which allow for VPN termination and routing.
For full details, see: Launching a Transit VPC Hub
- Launching a Spoke VPC
This procedure creates a spoke VPC, which connects to the transit VPC hub through dynamically routed VPN connections. The VPN connections of spoke VPCs allow the spoke VPCs to use routing and failover capabilities to maintain highly available network connections.
For full details, see: Launching a Spoke VPC.
- Launching DMVPN for Transit VPC
Dynamic Multipoint VPN (DMVPN) is a combination of GRE, NHRP, and IPsec. After the launch of the transit VPC stack launch has completed (see Launching a Transit VPC Hub), you can launch DMVPN using an AWS CloudFormation one-click template, which connects the transit VPC network to a private DMVPN hub. The transit VPC hub is treated as a DMVPN spoke.
For full details, see: Launching DMVPN for Transit VPC.