News

Transit Gateway Case Study

Challenges and threats

The customer has many AWS accounts and owns many VPCs in them. All the VPCs must be interconnected with a specific VPC of an account. Virtual SD-WAN appliance is placed in that VPC and connected with the on-premises SD-WAN appliance. Currently, the networking between VPCs is done with a lot of VPC peering connections. Peering connections between VPCs are complex and routes are becoming hard to modified and maintained.

NEX4 Cloud Team is asked to simplify the networking connections and give out the most suitable solution not to lose the transit access between VPCs across accounts.

Solution

Transit networking should be implemented between VPCs so that AWS transit gateway is used to ensure this. The complex VPC peering connections can be replaced by transit gateway attachment. And it also ensures transit connection between VPCs. Both virtual or on-premises SD-WAN appliances can be integrated with transit gateway and connection routes can be separated with transit gateway route tables for each VPC.

The general overall architecture diagram can be seen here.

Solution outcomes and benefits

• Transit Gateway can be used to interconnect resources across on-premises and cloud.
• Routes can be scalable and modifed in seperated transit gateway route tables.
• Upcoming VPCs can be easily integrated with the created Transit Gateway as needed.
• Transit Gateway Attachment Cost will be paid by VPC owner account.
• Single Management Portal for all connected on-premises and cloud services.