Networking is a big challenge with growing demands on diversified environments and creating datacenter across the world. Limit is just imagination. Enterprises works around different sites, different geography but common vein that join those environments are Network. With growing demands, it’s getting complicated to manage routes between sites. AWS Transit Gateway(TGW) is born to make Network Engineers life easy. TGW helps with following features –
- Connect multiple VPC network environment together for given account
- Connect multiple VPC network across multiple AWS account
- Inter region connectivity across multiple VPC
- Connect on-premise datacenter with VPC network via VPN or
- Connect multiple cloud environment via VPN using BGP.
Benefits of Transit Gateway
Easy Connectivity : AWS Transit Gateway is cloud router and help easy deployment of network. Routes can\will be easily propagated into environment after adding new network to TGW.
Better visibility and control : AWS Transit Gateway Network Manager used to monitor Amazon VPC’s and edge locations from central location. This will helps to identify and react on network issue quickly.
Flexible multicast : TGW supports multicast. Multicast helps sending same content to multiple destinations.
Better Security: Amazon VPC and TGW traffic always remain on Amazon private environment. Data is encrypted. Data is also protected for common network exploits.
Inter-region peering : AWS Transit Gateway inter-region peering allows customers to route traffic across AWS Regions using the AWS global network. Inter-region peering provides a simple and cost-effective way to share resources between AWS Regions or replicate data for geographic redundancy.
Transit Gateway Components
There are 4 major components in transit gateway –
Attachments : Attach network component to gateway. Attachments will be added to single route table. Following are network devices can be connected to TGW –
- Amazon VPC
- An AWS Direct Connect gateway
- Peering connection with another transit gateway
- VPN connection to on-prem or multi-cloud network
Transit gateway route table : Default route table will be created. TGW can have multiple route table. Route table defines boundary for connection. Attachments will be added to route table. Given route table can have multiple attachment where as attachment can only be added to single route table.
Route table includes dynamic and static routes. It determine next stop by given destination ip.
Association : To attach your attachment to route table we use association. Each attachment is associated with single route table but route table can have multiple attachments.
Route Propagation : All VPC and VPN associated to route table can dynamically propagate routes to route table. If VPN configured with BGP protocol then routes from VPN network can automatically propagated to transit gateway. For VPC one must create static routes to send traffic to transit gateway. Peering attachments does not dynamically added routes to route table so we need to add static routes.
We are going to test following TGW scenarios. In this architecture design I am creating “management VPC” that will be shared for entire organization. This VPC can be used for Active Directory, DNS, DHCP or NTP like common services for organization.
Project_VPC1 and Project_VPC2 will be able communicate with each other and managent_vpc. Private_VPC is isolated network(private project) and will not be able to communicate with project VPC’s, but should be able to communicate with management_vpc.
Following is architecture for this design –
- Region name
- Ami ID – “ami id” depend upon region
- Instance Role. We dont need this one explicitly, as we are not accessing any services or environment from instances.
- Instance key pair : Create instance key pair. Add key pair name in parameterstore. Parameter name should be – “ec2-keypair”. Value should be name of your keypair name.
This implementation has cost associated with it. With attached configuration testing is done within 1 hr then it will not take more than 50 cents.
For latest charges, look for AWS price calculator
First time to Terraform check this blog to get started –
Run following command to start terraform –
- ./terraform init
- ./terraform plan
- ./terraform apply –auto-approve
I am using terraform for implementation. Following is output for terraform –
Total 47(not 45) devices are configured.
4 VPC created
4 subnet created if you observe available ips are 1 less because one of the ip in a subnet will be used by transit gateway for data transfer and routing.
4 Route table created. Each route table will use transit gateway as target for other VPC network.
Security group – These are most important configuration configuration in real world. For DNS you will allow port 53 or AD server open appropriate ports. In my case, I am using ping for checking communication.
Private VPC will only able to communicate with management network.
Project VPC will able to communicate with other VPC where as not able to communicate with Private VPC.
Note : We don’t have to explicitly, block network in project VPC this should be blocked by transit gateway as we are not going to add propagation.
Transit Gateway created. Remember if 64512 ASN is used by existing VPN then this can be added as parameter to change it.
DNS support enables help to reach out cloud with dns names rather than ip address ,certainly a useful feature.
Transit gateway can be shared with other transit gateway for inter regional data transfer for VPC’s over Amazon private network. Its advisable to “disable” auto accept shared for security reason.
Default route table is created and all VPC not explicitly attached will be attached to default route table.
Each VPN needed to add to transit gateway as attachment.
Each route table is created. Route table can be created as per segregation one needed into environment. In my case I am creating 3 route table for 4 VPC’s. Generally in Enterprise environment, we do create 5 route table. Separate route table to backup and security environment.
Since project VPC1 and project VPC2 should have same network requirement so I added them to same route table.
Management Route table
Management route table has management VPC attachment. Propagation added from all network which needed to communicate with management VPC. In this case, management VPC should be able to communicate with all other network so added propagation from all networks. This will add all routes propagated automatically.
Private Network Route table
Private VPC attached to private network route table. Private network should be able to communicated with management VPC so added propagation for management VPC. Also route for management VPC is added automatically after propagation.
Project Route table
Project route table do have attachment from both project VPC. Propagation added for other project VPC network and management network. Respective routes are added.
Management server is able to ping both private and project environment instance.
Project VPC can talk to management VPC and other project VPC’s but not with private VPC
Private VPC able to talk to management vpc but not able to communicated with any project VPC’s. That makes private VPC private within organization.
Delete terraform configuration
To delete terrform configuration. Ensure all resources are destroyed
./terraform destroy –auto-approve
Transit gateway is tool to connect multiple VPC, VPN and direct connect network to make communication over private network. Transit gateway can be used to isolate network traffic. This makes routing comparatively easy.
SD-WAN partner solution can be used to automate adding new remote site into AWS network.
One reply on “AWS Transit Gateway”
I have gone through this article and find out good information, lets discuss with http://www.vitelglobal.in technical team.