This repository demonstrates the usage of Transit Gateway (TGW) connect and accelerates your integration of SDWAN appliances with AWS Transit Gateway.
For more details, checkout the Documentation and our Blog Article.
Example ip ranges see architecture diagram and pre-requisites folder in this repository
- Pick a region from the Documentation
- Transit Gateway setup with unused CIDR attached
- VPC with two public subnets
- VPC attached to Transit Gateway
- Public subnets route table entries with destination TGW CIDR pointing to TGW
- (Optional) Deploy tgw_vpc_basics.yaml for VPC and Transit Gateway setup
- Important: Manually attach a CIDR block to Transit Gateway (here:
10.10.0.0/24
) - Deploy gre_setup.yaml, important parameters are the transport TGW attachment id, route table id and VPC information
- VPC needs to be attached to TGW
- Consumer subnets need a default route (
0.0.0.0/0
) towards TGW - VPC attachment has to be associated with GRE main route table
- Routing from TGW towards consumer VPC has to be in place within GRE main route table
- Dual redundant setup, two SDWAN instances with two GRE tunnels each
- Full appliance instance failover takes ~30s
- Not all regions support TGW Connect (details see AWS documentation: TGW Connect)
- CFN resource type
AWS::EC2::TransitGatewayConnect
is not supported in all regions
- While code samples in this repository has been tested and believe it works well, as always, be sure to test it in your environment before using it in production!
- The sample SDWAN appliances are just break-outs to the public internet in this sample setup
See CONTRIBUTING for more information.
This library is licensed under the MIT-0 License. See the LICENSE file.