The cloudformation in this project are intended to be used in support of the AWS blog article here: creating-a-single-internet-exit-point-from-multiple-vpcs-using-aws-transit-gateway
The files contained here are as follows:
| File | Description |
|---|---|
| transitgateway-egress-solution.yml | Template to create the network infrastructure |
| transitgateway-test-ec2.yml | Template to create the Bastion/Apps tests |
| init-aws-transit-gateway.sh | Script to create AWS services using Cloudformation |
| connect-aws-transit-gateway.sh | Script to connect by Bastion instance to App instances a check internet connection |
| delete-aws-transit-gateway.sh | Script to delete AWS services |
The cloudformation automatically creates the solution highlighted in the blog, and will populate the VPC route tables with the correct routes after creation of the transit gateway attachments. This function has recently been added to cloudformation.
The purpose of the cloudformation is to create this architecture ...
Before, create a key pair with name transit-gateway-key-pair to link EC2 instances and copy into base project path
./init-aws-transit-gateway.sh
./connect-aws-transit-gateway.sh
./delete-aws-transit-gateway.sh
This architecture costs ...
This library is licensed under the MIT-0 License. See the LICENSE file.