Transit Gateway Peering - Cross Accounts Not Sharing Payer ID
Is same Payer ID required for cross-account TGW peering? A customer is wanting to peer with multiple 3rd parties using DGW. I understand that cross-region and cross-account TGW peering is supported. However, it's not clear if cross-account peering requires the accounts to have the same Payer ID, similar to how associations between TGW and DXG in separate accounts do.
By reading the documentation, and also doing a test between two personal accounts - I can confirm that it is possible to peer Transit Gateways between accounts even when they do not have the same payer account.
You do need the following details from the account that you are peering with:
- Account Name
- Region
- Transit Gateway ID
The instructions can be found below:
Source: https://docs.aws.amazon.com/vpc/latest/tgw/tgw-peering.html
Relevant questions
Transit Gateway shared with AWS Resource Access Manager (AWS RAM) identify all accounts as external
Accepted Answerasked 3 years agoAWS Transit Gateway attachment pricing
Accepted Answerasked 2 years agoTransit Gateway to Direct Connect Gateway to Transit Gateway
Accepted Answerasked 2 years agoAWS Transit Gateway peering encryption
Accepted Answerasked 2 years agoData transfer cost on VPC peering with different AWS accounts
Accepted Answerasked 2 years agoTransit Gateway Inter-region Peering Pricing
Accepted AnswerAccessing S3 Gateway VPC Endpoint from another VPC (VPC Peering established between both source and destination VPCs)
Accepted Answerasked 2 years agoTransit Gateway Peering - Cross Accounts Not Sharing Payer ID
Accepted Answerasked 2 years agoCross Region private link
Accepted Answerasked 3 months agoUsing VPC Peering in addition to Transit Gateway for cost optimization
Accepted Answerasked a year ago