Enterprise Multi-VPC Transit Hub: Asymmetric Return Blackhole
Client Profile: Enterprise migrating from on-premises deployed an AWS Transit Gateway connecting Spoke VPC A (App tier 10.10.0.0/16) and Spoke VPC B (Shared database tier 10.20.0.0/16). Problem: TCP handshakes from EC2-A to EC2-B time out after initial SYN packets cross the TGW. VPC Flow Logs indicate asymmetric routing failure.
Lab Objective
Add the missing return route in Spoke VPC B route table for 10.10.0.0/16 targeting the Transit Gateway.
Exam Track & Type
Solutions Architect Professional (SAP) (SAP-C02) · Live Outage Troubleshooting Drill
FinOps & Cost Impact
Consolidating multi-VPC routing into a centralized Transit Gateway eliminates N*(N-1)/2 complex VPC peering management costs and allows unified bandwidth management.
AWS Services Involved
Verification Success Criteria
- Spoke VPC B route table has route for 10.10.0.0/16 targeting tgw-hub.
- Transit Gateway attachments exist for both VPCs.
Diagnostic Starting Point (Spoiler-Free Hint)
Real Solutions Architect Interview Question
Frequently Asked Questions
How do I troubleshoot "Enterprise Multi-VPC Transit Hub: Asymmetric Return Blackhole" in AWS?
In an AWS Transit Gateway hub-and-spoke topology, bidirectional communication requires symmetric route entries. If Spoke A forwards packets to Spoke B via TGW, what route table entry must exist in Spoke B for return traffic?
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.…