What is Amazon Route 53? A plain-English explainer

What DNS is, briefly

DNS is the system that maps human-friendly domain names to the numerical addresses computers use to actually locate and connect to resources on a network. Our what-is-dns explainer covers this in more depth; the short version is that DNS is essentially the internet’s phone book, and without it people would have to remember and type raw numerical addresses instead of names.

Route 53 is AWS’s implementation of that lookup system, run as a fully managed service — AWS operates the infrastructure, and you configure what each domain name should resolve to.

What Route 53 does

At its core, Route 53 translates domain names into the resources they should point to — an AWS service, a server, or another address entirely. Beyond that basic lookup, it can also register new domain names directly, so a domain can be bought and managed in the same place it is configured.

Route 53 also supports routing policies that go beyond a single fixed answer: it can route traffic based on latency to send users to the fastest available location, fail over automatically to a backup resource if the primary one becomes unhealthy, or split traffic across multiple destinations by weight. Health checks underpin the failover behaviour — Route 53 can actively monitor whether a resource is responding and stop directing traffic to it if it is not.

Common uses

Route 53 is used to point a domain name at a website or application, to register and manage domain names, to route users to the nearest or fastest healthy resource across multiple regions, and to automatically fail over to backup infrastructure if a primary resource goes down. It is often one of the first services configured when a domain goes live on AWS, and one of the ones quietly relied on afterwards for resilience.

• Resolving a domain name to an application or resource
• Registering and managing domain names
• Latency-based or geographic routing across regions
• Automatic failover using health checks

A globally scoped service

Unlike many AWS services that are configured per region, Route 53 is a global service — a hosted zone and its records are not tied to a single AWS region, because DNS itself is inherently a global system. This is a distinctive property worth remembering: you do not choose a region when working with Route 53 the way you would for, say, EC2.

Cross-cloud equivalents

Every major cloud provider offers a managed DNS service in the same spirit as Route 53: Microsoft Azure offers Azure DNS, and Google Cloud offers Google Cloud DNS. All three do the same fundamental job of translating domain names to resources, and the choice generally follows whichever cloud is hosting the resources being pointed to.

Route 53 and pricing

Route 53 pricing is pay-for-use, billed based on things like the number of hosted zones, DNS queries answered and health checks running, plus domain registration where applicable, rather than a flat subscription. Exact rates change over time, so check the AWS pricing page for current figures rather than relying on a fixed number here.

Where Route 53 appears in certification study

Route 53 appears across AWS certifications as a foundational networking service: the Cloud Practitioner exam expects a basic understanding of what it does, while the Solutions Architect Associate and CloudOps Engineer Associate exams go further into routing policies, health checks and how Route 53 supports high availability across regions.

This article deliberately stays at that introductory level. How routing policies and health checks are actually configured is exam-depth material, and that is what our /revision study library is built to cover.