Q: Your company has two VPCs in different AWS regions. You set up VPC Peering between them. From VPC A (10.0.0.0/16), you can reach a server in VPC B (10.1.0.0/16). However, the server in VPC A cannot access the internet *through* VPC B's NAT Gateway. Why?
AWS VPC Peering does not support Transitive Edge Routing.
Want to master this scenario in a live sandbox? KodeKloud's Istio Service Mesh & Advanced Kubernetes Networking Course covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "Isolating network failures requires proving whether packets are dropped by route tables, security groups, or stateless NACLs. The interviewer is testing: VPC Peering limitations, transitive routing.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
AWS VPC Peering does not support Transitive Edge Routing.
- Provide VPC A with its own NAT Gateway and Internet Route.
- Use AWS Transit Gateway, which supports advanced routing topologies including routing edge internet traffic through a centralized egress VPC.
- Setup proxy software (e.g. Squid) on an instance in VPC B, and have VPC A explicitly use that proxy.
Remediation & Permanent Safeguards
This means traffic from VPC A cannot traverse VPC B to hit an edge device configured in VPC B (like an Internet Gateway, NAT Gateway, Direct Connect, or VPN). VPC Peering only allows communication strictly terminating at the instances within the peered VPCs. To solve this, you would need to either:
- Provide VPC A with its own NAT Gateway and Internet Route.
- Use AWS Transit Gateway, which supports advanced routing topologies including routing edge intern...
- Setup proxy software (e.g. Squid) on an instance in VPC B, and have VPC A explicitly use that proxy.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Treating stateless Network ACLs as stateful firewalls without specifying outbound ephemeral return ports when configuring Networking company VPCs Security Groups track connection state automatically, whereas stateless Network ACLs require explicit ephemeral port rules (1024-65535) for return traffic.
- Opening short-lived non-pooled TCP client connections, exhausting ephemeral ports in TIME_WAIT state when configuring Networking company VPCs Rapidly opening and closing short-lived TCP sockets without connection pooling exhausts ephemeral ports, causing connection refusal errors.
- Directing load balancer health checks to heavy computational endpoints rather than dedicated health routes when configuring Networking company VPCs Deep health check paths amplify database load during traffic spikes and risk cascading eviction of healthy application nodes.
- Triggering BGP route dampening by rapidly announcing and withdrawing multihomed network prefixes when configuring Networking company VPCs Rapidly flapping BGP route announcements triggers upstream ISP route dampening, effectively blackholing network traffic for hours.