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

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?

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)

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?

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.