Durch die Nutzung von AWS re:Post stimmt du den AWS re:Post Nutzungsbedingungen
AWS re:Postre:Post

Inquiry about Sharing Transit Gateway (TGW) with Different AWS Account in us-east-1 Region"

0

The customer has established a Direct Connect connection in the us-east1 AWS region. This connection is linked to a Direct Connect (DX) Gateway utilizing a transit Virtual Interface (VIF). Additionally, a Transit Gateway (TGW) has been set up in the us-east 2 AWS region.

Now, the customer intends to share the same Transit Gateway (TGW) with a different AWS account that exists in the us-east 1 region.

The question is: Is it possible to share the same TGW with a different AWS account in the us-east 1 region?

In summary, the customer has set up a network infrastructure connecting two AWS regions (us-east1 and us-east 2) using Direct Connect and Transit Gateway, and they are considering sharing the TGW with another AWS account in the us-east 1 region.

Themen
Vernetzung & Bereitstellung von Inhalten
Tags
AWS Direct ConnectAWS Transit Gateway
Sprache
English
Ali Md
gefragt vor 10 Monaten503 Aufrufe
1 Antwort
1
Akzeptierte Antwort

Transit Gateway is a regional construct. You can not share a TGW in us-east-2 with an account in us-east-1. You'll need to setup a separate TGW in us-east-1, you can then potentially peer the 2 TGWs for inter-region connectivity.

Take a look at this example: https://docs.aws.amazon.com/whitepapers/latest/hybrid-connectivity/aws-dx-dxgw-with-aws-transit-gateway-multi-regions-and-aws-public-peering.html

profile pictureAWS
EXPERTE
Tushar_J
beantwortet vor 10 Monaten
profile picture
EXPERTE
Sedat Salman
überprüft vor 10 Monaten
profile picture
EXPERTE
Gary Mclean
überprüft vor 10 Monaten
  • Ali Md
    vor 10 Monaten

    Thank you for your input, Tushar. I have a couple of questions: Is it necessary to associate two Transit Gateways (TGWs) with the Direct Connect Gateway if we do not intend to establish inter-region peering between the two TGWs? In the scenario where inter-region peering is configured on the Transit Gateway, is it sufficient to associate just one TGW, or is it still required to associate both TGWs?

  • Tushar_J EXPERTE
    vor 10 Monaten

    If you dont need inter-region connectivity then TGW peering is not required. Direct Connect Gateway provides north-south connectivity (on-premises to AWS) and TGW peering provides east-west/inter-region connectivity (AWS region A to AWS region B)

  • Ali Md
    vor 10 Monaten

    Thanks again, Tushar! Please correct me if my understanding is accurate:

    1. To establish connectivity with the principal account in the us-east-1 region, I must create a Transit Gateway (TGW) in the same us-east-1 region.
    2. Similarly, to connect to the principal accounts in the us-east-2 region, I need to create a separate Transit Gateway in the us-east-2 region.
    3. Once the TGWs are created in both us-east-1 and us-east-2 regions, can I associate both of them with the Direct Connect (DX) Gateway to achieve the desired connectivity?
  • Tushar_J EXPERTE
    vor 10 Monaten

    Answer to your first 2 questions is yes. for question # 3 - yes, you can associate the 2 TGWs with the same DXGW for the on-premises connectivity.

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen

Relevanter Inhalt