SAA-C03 · Domain 3: Design Secure Architectures

Publish Private Compute: Secure Route 53 CNAME & Dual-AZ ALB Reverse Proxy

Client Profile: Fintech startup PayVault runs an internal ledger API on EC2 instances inside an isolated private subnet (10.0.10.0/24) with no public IP. The security compliance team strictly forbids attaching an Internet Gateway directly to compute or assigning public IPv4 addresses. However, external client applications must reach the payment API at api.payvault.io via a resilient Dual-AZ Application Load Balancer.

Launch Interactive Lab in Browser → Browse All 56 AWS Labs

Lab Objective

Expose the private EC2 compute service via an Internet-Facing ALB spanning two public AZs, configure Target Group forwarding, chain security groups, and point a Route 53 CNAME/ALIAS to the ALB.

Exam Track & Type

Solutions Architect Associate (SAA) (SAA-C03) · Architecture Build Lab

FinOps & Cost Impact

Security Group rule chaining provides zero-trust perimeter microsegmentation at $0 additional cost. Multi-AZ ALB eliminates downtime and prevents single-datacenter failure.

AWS Services Involved

VPC Cheatsheet → SUBNET Cheatsheet → IGW Cheatsheet → RTB Cheatsheet → ALB Cheatsheet → TG EC2 Cheatsheet → SG Cheatsheet → ROUTE53 Cheatsheet →

Verification Success Criteria

Diagnostic Starting Point (Spoiler-Free Hint)

How can internet clients reach a web service running inside an isolated private subnet without assigning public IPs to compute or placing servers in an exposed public subnet? What managed reverse-proxy accepts public traffic across multiple AZs and securely forwards to private compute?

Real Solutions Architect Interview Question

Explain why AWS RFC rules prevent a CNAME at the zone apex, why ALBs require at least two public AZs, and how Security Group chaining protects backend EC2 instances from direct internet attacks.

Frequently Asked Questions

How do I troubleshoot "Publish Private Compute: Secure Route 53 CNAME & Dual-AZ ALB Reverse Proxy" in AWS?

How can internet clients reach a web service running inside an isolated private subnet without assigning public IPs to compute or placing servers in an exposed public subnet? What managed reverse-proxy accepts public traffic across multiple AZs and securely forwards to private compute?

Which AWS certification exam covers this architecture scenario?

This interactive lab maps directly to SAA-C03 (Solutions Architect Associate (SAA)) under Domain 3: Design Secure 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

CLF-02

Locked-Out Security Group Ingress

Add an inbound rule allowing TCP port 80 from 0.0.0.0/0 to the web instance Security Group.…

CLF-03

Public Database Exposure Vulnerability

Move or configure RDS to be in a private subnet, disable public accessibility, and restrict ingress exclusively to …

CLF-05

S3 Public Access Block Disabled

Enable S3 Block Public Access and enable AES-256 or KMS encryption on the S3 bucket.…

SAA-01

FinTech 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-02

HealthTech 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-03

Retail 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.…