Inter-VPC Traffic Isolation: Peering vs Transit Gateway Asymmetric Routing Trap
Client Profile: A multinational investment bank operates a multi-VPC architecture consisting of Production VPC (10.10.0.0/16), Shared Services VPC (10.20.0.0/16), and an isolated Compliance Audit VPC (10.30.0.0/16). Problem: The enterprise migrated to an AWS Transit Gateway hub for Prod and Shared, but left an unisolated legacy VPC Peering connection targeting the Audit VPC. A junior network engineer misconfigured the Shared Services route table: outbound traffic to Prod (10.10.0.0/16) was pointed to the Peering connection instead of the Transit Gateway. Traffic from Prod to Shared reaches the destination via TGW, but the return packets enter the peering trap and are dropped, causing total transaction timeouts and violating compliance isolation policies.
Lab Objective
Resolve the asymmetric routing trap: update the Shared Services VPC route table so that 10.10.0.0/16 targets the Transit Gateway (tgw-hub), ensure the VPC Peering connection is isolated exclusively to the Audit VPC (10.30.0.0/16), and restore symmetric bidirectional routing.
Exam Track & Type
Solutions Architect Professional (SAP) (SAP-C02) · Live Outage Troubleshooting Drill
FinOps & Cost Impact
Enforcing clean Transit Gateway route table association and removing redundant peering routes prevents unexpected cross-peering inter-AZ data transfer fees and eliminates asymmetric routing outages.
AWS Services Involved
Verification Success Criteria
- Shared Services VPC route table sends 10.10.0.0/16 targeting the Transit Gateway (tgw-hub).
- Production VPC route table sends 10.20.0.0/16 targeting the Transit Gateway (tgw-hub).
- VPC Peering connection is strictly isolated to the Compliance Audit VPC (10.30.0.0/16).
- Production VPC does not have unapproved routes into the Compliance Audit VPC.
Diagnostic Starting Point (Spoiler-Free Hint)
Real Solutions Architect Interview Question
Frequently Asked Questions
How do I troubleshoot "Inter-VPC Traffic Isolation: Peering vs Transit Gateway Asymmetric Routing Trap" in AWS?
Why does asymmetric routing—where outbound traffic enters a VPC via Transit Gateway but return traffic routes out via VPC Peering—cause stateful TCP drops at the endpoint?
Which AWS certification exam covers this architecture scenario?
This interactive lab maps directly to SAP-C02 (Solutions Architect Professional (SAP)) under Domain 1: Design Resilient Architectures.
Do I need an AWS account or credit card to practice this lab?
No. CloudTracer runs a stateful VPC packet engine locally in your browser so you can debug Route Tables, Security Groups, NACLs, and target groups with $0 AWS cloud spend.
Related SAP-C02 Troubleshooting Labs
Missing Internet Gateway Route
Attach or route default outbound traffic 0.0.0.0/0 to the Internet Gateway in the public route table.…
CLF-04Single Point of Failure (Single-AZ)
Add a secondary subnet in us-east-1b and front instances with an Application Load Balancer across both Availability…
CLF-06Tight Coupling in Transaction Processing
Decouple the architecture by placing an Amazon SQS queue between the producer and consumer.…
SAA-02HealthTech EMR Backend: Asymmetric Outbound NAT Routing
Re-point the private route table default route pointing to NAT (0.0.0.0/0 -> nat-xxx) in the public subnet.…
SAA-08Multi-Tier Highly Available Web Architecture: Dual-AZ ALB, ASG Fleet & Multi-AZ RDS
Re-architect for multi-AZ high availability: map the public ALB across dual AZs (us-east-1a and us-east-1b), distri…
SAA-14E-Commerce Flash Sale: EventBridge Dead-Letter Queue (DLQ) Delivery Blackhole
Configure the EventBridge rule to route failed execution events to sqs-order-dlq.…