Entry · AWS SERVICE CHEATSHEET

Amazon Route 53 (ROUTE53)

Global authoritative DNS resolution engine providing health-checked Alias routing, multi-region latency optimization, automated disaster failover, and private VPC DNS split-view namespaces.

Open Interactive ROUTE53 Sandbox → Simulate in Architecture Studio

AWS Container Placement

Regional / Global Managed Scope (Outside VPC Subnets)

Summary

Highly available and scalable cloud Domain Name System (DNS) web service designed to route end users to internet applications and AWS infrastructure.

When to Use (SAA-C03)

Use ALIAS records (free queries, works at zone apex) for AWS resources like ALB/CloudFront; use Private Hosted Zones for internal VPC DNS.

Allowed Ingress Connections & Ports

Source ServiceProtocolPortArchitectural Rationale
WEBCLIENTDNS (UDP/TCP)53End-user DNS query resolution requests

Allowed Egress Targets & Ports

Target ServiceProtocolPortData Flow Rationale
CLOUDFRONTALIAS0CloudFront distribution edge DNS ALIAS resolution (d123.cloudfront.net)
ALBALIAS0Application Load Balancer dualstack DNS ALIAS resolution
APIGWCNAME / ALIAS0API Gateway custom domain name mapping
S3ALIAS0S3 static website bucket endpoint resolution

Key Configuration Parameters & AWS Best Practices

ParameterFormat / ExamplePurpose & Rationale
Domain Name (route53Domain) (Required)api.production.example.comThe fully qualified domain name for the DNS resource record set. Why: Identifies the DNS hostname that client resolvers query.
Record Type (route53Type) (Required)AThe DNS protocol record type defining the format of the answer. Why: Determines whether the query returns an IPv4 address (A), IPv6 address (AAAA), or alias redirection.
Routing Policy (route53RoutingPolicy) (Required)latencyThe algorithm Route 53 uses to determine which endpoint to return in response to queries. Why: Allows designing high-availability failover, performance latency steering, or blue/green traffic shifts.
Time to Live (route53Ttl)60The duration in seconds that intermediate DNS resolvers cache the record before re-querying Route 53. Why: Lower TTL (60s) speeds up cutover during migrations; higher TTL (300s-86400s) reduces DNS query costs.
Hosted Zone ID (route53HostedZoneNodeId)Z0123456789ABCDEFThe unique identifier of the Route 53 public or private hosted zone. Why: Scopes the record set to its parent domain container.
Evaluate Target HealthtrueEnables Route 53 to evaluate downstream ALB/CloudFront health check state prior to serving the ALIAS record. Why: Prevents routing traffic to impaired load balancer nodes.

Practice Labs Using Amazon Route 53

SAA-12

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

Expose the private EC2 compute service via an Internet-Facing ALB spanning two public AZs, configure Target Gr…

SAA-16

Enterprise Multi-VPC Peering: Non-Transitive Routing & Route 53 Private Hosted Zone Fallacy

Establish a direct VPC Peering connection between VPC A and VPC C, update route tables with non-overlapping ro…

SAA-C03-MULTIREGION-DR-FAILOVER

Global E-Commerce: Multi-Region Active-Active DR & Automated Route 53 Failover

Configure Route 53 failover routing policy, connect DR ALB, and link DynamoDB Global Table replication.…

SAA-C03-HYBRID-SPLIT-HORIZON-DNS

Hybrid Enterprise Networking: Split-Horizon DNS with Route 53 Resolvers

Deploy Route 53 Inbound and Outbound Resolver Endpoints in VPC subnets, associate the Private Hosted Zone, and…

SAP-07

Disaster Recovery (DR): Aurora Cross-Region Replication Lag

Establish cross-region replication between primary and standby database clusters.…

BUILD-13

Build: Multi-Region CloudFront Edge + WAF + S3 OAC

Design from scratch: Route 53 DNS -> AWS WAF -> CloudFront CDN -> Private S3 Bucket.…

Frequently Asked Questions

Where does Amazon Route 53 live inside an AWS VPC architecture?

Valid container placement: Regional / Global Managed Scope (Outside VPC Subnets). Global authoritative DNS resolution engine providing health-checked Alias routing, multi-region latency optimization, automated disaster failover, and private VPC DNS split-view namespaces.

When should I use Amazon Route 53 on the AWS SAA-C03 exam?

Use ALIAS records (free queries, works at zone apex) for AWS resources like ALB/CloudFront; use Private Hosted Zones for internal VPC DNS.

Can I simulate Amazon Route 53 packet routing without an AWS account?

Yes. CloudTracer simulates Amazon Route 53 along with 53 AWS services directly in your browser and exports production Terraform HCL.