Transit gateway peering attachments

This section provides instructions for creating transit gateway peering attachments.

See Add or edit tags for a transit gateway for instructions on adding and editing tags.

Add tags to transit gateway

Key	Value	Description
TgwPeer	<tgw-id_aws_region>	The default key prefix is TgwPeer. The default delimiter in the tag value to list multiple transit gateway per region is slash(/). You must provide a valid Region name where the remote transit gateway exists. The value must be the remote transit gateway ID that exists in the <aws_region> that you provided in the key. For example, if you create a peering attachment with a transit gateway (tgw-2222) in the U.S. East (Ohio) Region (us-east-2), the tag key would be TgwPeer and the value would be tgw-2222_us-east-2. You can peer with a second transit gateway in the same Region by using the same delimiter to add another suffix the tag key. In this case, the tag key would be TgwPeer and the value must be tgw-2222_us-east-2/tgw-3333_us-east-1. You can change the Transit Gateway Peering Tag add reference to the CFN parameter used in the key in the template during initial configuration, but you must use the same key name when you tag the transit gateway. Note Changing the value doesn’t update the attachment. You must delete the tag and recreate it with a new value, then recreate the peering attachment.

Important

To route traffic between peered transit gateways, you must add a static route to the selected transit gateway route table that points to the transit gateway peering attachment. After you create the route, associate the same transit gateway route table with the transit gateway peering attachment. Refer to Create a static route for more information.