Posted On: Dec 1, 2021
Starting today, AWS Transit Gateway supports intra-region peering, giving you the ability to establish peering connections between multiple Transit Gateways in the same AWS Region. With this change, different units in your organization can deploy their own Transit Gateways, and easily interconnect them resulting in less administrative overhead and greater autonomy of operation.
Transit Gateway enables you to connect thousands of Amazon Virtual Private Clouds (VPCs) and your on-premises networks using a single gateway. Until now you could only establish peering connections between Transit Gateway in different AWS Regions. With this launch, you can simplify routing and inter-connectivity between networks that are serviced via separate Transit Gateways in the same AWS Region. The ability to natively peer Transit Gateways in the same region eliminates the need to create and manage transit VPCs, simplifies route-tables management, and reduces the probability of configuration errors. Using intra-region peering, you can build flexible network topologies and easily integrate your network with a third-party or partner managed network in the same region.
To get started, create a peering attachment on your transit gateway, and specify a transit gateway you want to peer within the same AWS Region. The peer Transit Gateway can be in your account or a different AWS account. By creating static routes in Transit Gateway route tables, you can route traffic between the VPCs and connections attached to each Transit Gateway. This feature is available through the AWS Management Console, the Amazon Command Line Interface (Amazon CLI), and the Amazon Software Development Kit (Amazon SDK).
Transit Gateway intra-region peering is available in all AWS commercial and AWS GovCloud (US) regions. Pricing for intra-region peering is the same as that for inter-region peering. For additional information, visit the AWS Transit Gateway product page, the documentation, pricing page and the blog post.