AWS Route53 — Cheat Sheet(In 2 Minutes)

Gaurav Gupta
2 min readMay 6, 2020

Route53- Managed DNS(Domain Name System) in AWS.

DNS: Collection of rules & records.

AWS Route53

Route53 uses:

  • Public Domain (You own)
  • Private Domain ( Inside your VPC for your instances)

Route53 Features:

  • Health Checks
  • Load Balancing through DNS
  • Provides different kinds of Routing Policy.

Pricing: $0.50 per month per hosted zone

Types of Records:

  • A Record -Hostname to IPv4
  • AAAA -Hostname to IPv6
  • CNAME- Hostname to Hostname
  • Alias- Hostname to AWS Resources

TTL (Time to live):

DNS cache for TTL duration. It’s mandatory for all kind of records.

Max TTL: 24hrs

Min TTL: 60 seconds

Health check:

Monitor the health and performance of your application’s servers, or endpoints, from a network of health checkers in locations around the world. You can specify either a domain name or an IP address and a port to create HTTP, HTTPS, and TCP health checks that check the health of the endpoint.

Health check failed: Unhealthy if 3 health checks get fail.

Health check passed: Healthy if 3 health checks get pass.

Alias VS CNAME:

Alias: Hostname to AWS Resource, works for root domain & non-root domain both.

CNAME(Zone Apex): hostname to hostname, only work for non-root domain (it means, CNAME’s record name can’t be same as hosted zone name).

Routing Policies:

Simple Routing: redirect to single resource, can’t attach health check, If multiple records are attached, random one will be selected.

Weighted Routing: “N” % requests will go to specific Endpoint, It’s helpful to test 5–10% traffic on new application version, can attach health check.

Latency Routing: redirect to the server that has the least latency close to us, latency is calculated in terms to AWS Region, health check attached.

Failover Routing: If primary resource is not working, traffic is redirect to secondary instance/resource. Health check is mandatory.

Geo-location Routing: routing is based on user location. Specify that, traffic from XYZ location should go always to particular instance/resource, if it doesn’t match, should go to default policy(We define this also).

Multi-Value: Use when, traffic needs to go to multiple resources, health check mandatory. It’s not substitute for having an ELB.

DOMAIN REGISTRAR is not equal to DNS.

If you have bought domain from 3rd party (eg: Go Daddy), you can use it in AWS Route53 by creating a hosted zone in Route53 & update NS records on 3rd party website to use Route53 name servers.

if you want to read in depth, check below blog:

--

--