HealthTech EMR Backend: Asymmetric Outbound NAT Routing
Client Profile: HealthCare Systems operates an electronic medical records (EMR) application. Compute nodes in private subnets must query external drug interaction registries over the internet. Problem: A junior engineer modified the private route table and set 0.0.0.0/0 directly to the Internet Gateway. External API calls fail with timeouts.
Lab Objective
Re-point the private route table default route pointing to NAT (0.0.0.0/0 -> nat-xxx) in the public subnet.
Exam Track & Type
Solutions Architect Associate (SAA) (SAA-C03) · Live Outage Troubleshooting Drill
FinOps & Cost Impact
Directing private egress through a shared NAT Gateway avoids allocating costly individual Elastic IPs to dozens of backend instances and enforces centralized outbound filtering.
AWS Services Involved
Verification Success Criteria
- Private subnet route table default route points to the NAT Gateway (0.0.0.0/0 -> nat-xxx).
- NAT Gateway resides in the public subnet with an Internet Gateway route.
- Public subnet route table maintains default route 0.0.0.0/0 pointing to the Internet Gateway.
- Compute instance in private subnet retains private IP without public IP exposure.
Diagnostic Starting Point (Spoiler-Free Hint)
Real Solutions Architect Interview Question
Frequently Asked Questions
How do I troubleshoot "HealthTech EMR Backend: Asymmetric Outbound NAT Routing" in AWS?
Why does directing outbound traffic from a private subnet without public IPs directly to an Internet Gateway fail? What managed gateway in a public subnet translates private IP traffic?
Which AWS certification exam covers this architecture scenario?
This interactive lab maps directly to SAA-C03 (Solutions Architect Associate (SAA)) 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 SAA-C03 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-01FinTech Payment Ledger: $6,750 NAT Gateway S3 Cost Surge
Add an S3 prefix-list destination route in the private route table targeting the S3 Gateway Endpoint.…
SAA-03Retail Banking PCI Audit: Stateless NACL Ephemeral Drop
Add an outbound NACL rule permitting return ephemeral traffic (TCP 1024-65535) to 0.0.0.0/0.…
SAA-04E-Commerce Flash Sale: ALB 502 Bad Gateway Port Mismatch
Reconcile Target Group port to match the backend EC2 application port (80) to restore healthy status.…