Transit Gateway Peering #

🔄 Transit Gateway Peering Setup Between Workspaces and DB VPCs #

🧭 Objective #

Establish successful bi-directional connectivity between the Workspaces VPC and multiple DB VPCs across AWS accounts using Transit Gateway (TGW) peering.

🛠️ Steps Taken #

1. Source TGW Route Table Update (Workspaces VPC)

   • Identified that the TGW route table [tgw-rtb-0ce6425b61b4b023a] lacked a route to the DB VPC CIDR (10.80.96.0/19).
   • ✅ Route added pointing to the peering attachment.

2. Peering TGW Route Table Propagation

   • The TGW route table [tgw-rtb-022e56c20124fc292] associated with the peering had no DB VPC routes.
   • ✅ Propagation of DB VPCs into the peering route table was configured.

3. Return Path Setup in DB TGW Route Tables

   • Verified and added return routes to the Workspaces VPC CIDR in each DB VPC’s TGW route table:
     • tgw-rtb-06397d477fd853f3b
     • tgw-rtb-08d79219f77eead64
     • tgw-rtb-0b26d6befa805b82c4

4. Validation

   • All Transit Gateway route configurations were reviewed and confirmed from AWS’s side.
   • Next step: Customer team to test connectivity between Workspaces and DB VPCs.

🔁 Traffic Flow Path #

Forward Path: Workspaces VPC → TGW Attachment (Virginia) → TGW Peering Attachment (Ohio) → DB VPC

Return Path: DB VPC → TGW Attachment (Ohio) → TGW Peering Attachment (Virginia) → Workspaces VPC