Transit VPC Workflow Instructions¶
This workflow provides you with a step by step instructions to build a Global Transit Network. It abstracts and combines multiple existing Aviatrix features, such Encrypted Peering, Transitive Peering and Site2Cloud to bring you a wizard like experience so that you do not have to go to multiple pages on the Controller console when building the Transit group.
This Global Transit Network consists of a Transit gateway and a set of Spoke gateways, to faciliate communication between Spoke VPC EC2 instances and on-prem network.
For description purpose, gateway and GW are used interchangebly.
The Global Transit Network diagram is described as below.
Planning and Prerequisites¶
- Identify a VPC, call it Transit VPC, in a region where you want to launch the Transit GW.
- Create a VGW in the same region. The VGW can be either attached to the Transit VPC or detached. This VGW can be connect to on-prem either over Direct Connect or over Internet.
- If this is your first time using Aviatrix, make sure you go through the Aviatrix Controller on-boarding process to create Aviatrix account that corresponds to an IAM role. For instructions on how to launch an Aviatrix Controller, check out this link.
1. Launch a Transit Gateway¶
The Transit GW is the hub gateway, it servers to move traffic between a Spoke VPC and on-prem network.
2. (Optionally) Enable HA for the Transit Gateway¶
When HA is enabled, a second Transit GW will be launched. Note both Transit GWs will be forwarding traffic in any event of tunnel failure between a Spoke VPC and Transit VPC, and between the Transit GW and VGW.
3. Connect the Transit GW to AWS VGW¶
This step builds a site2cloud IPSEC tunnel with VGW and establishes BGP session with VGW to exchange routes between on-prem and the cloud.
4. Launch a Spoke Gateway¶
5. (Optionally) Enable HA for the Spoke Gateway¶
6. Join a Spoke GW to Transit GW Group¶
This step builds a Aviatrix encrypted peering and transitive peering between the Spoke GW and the Transit GW. The Controller also instructs the Transit GW to start advertise the Spoke VPC CIDR to VGW via the established BGP session.
7. Remove a Spoke GW from a Transit GW Group¶
This step removes the Aviatrix encrypted peering and transitive peering between the Spoke GW and the Transit GW built in the previous step. The Controller also instructs the Transit GW to stop advertising the Spoke VPC CIDR to VGW.
Note the Spoke GW is not deleted and you can go to step 6 to join the Transit GW group again.
To delete a Spoke GW, go to Gateway on the main navigation tab, select the gateway and click Delete.
8. Add More Spoke VPCs¶
Repeat step 4 to 6 to add more Spoke VPCs to the Transit GW group.
9. View the Network Topology¶
You can view the network topology by going to the Dashboard. Click on the Map View to switch to Logical View. In the Logical View, each gateway is represented by a dot. You can rearrange the initial drawing by moving the dot, zoom in or zoom out, move the graph around. After you are done moving, click the Save icon.
10. Remove Transit GW to VGW Connection¶
You can remove the BGP and IPSEC connection to VGW via this step.
You can go to Step 3 to build the connection again.
11. Troubleshoot BGP¶
Under Advanced Config on the main navigation bar, click BGP. The Transit GW will have BGP Mode as Enabled. Click the Transit GW and click Details to see Advertised Networks and Learned Networks. Learned Networks are network CIDR blocks that BGP learned from VGW. Advertised Networks are Spoke VPC CIDRs.
You can also click Diagnostics. Select one of the show commands or type in yourself if you know the commands to see more BGP details.