Amazon Route 53
API Reference

Welcome

Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. Route 53 performs four main functions:

  • Domain registration – Route 53 helps lets you register domain names such as example.com.

  • Domain Name System (DNS) service – Route 53 translates friendly domains names like www.example.com into IP addresses like 192.0.2.1. Route 53 responds to DNS queries using a global network of authoritative DNS servers, which reduces latency.

  • Health checking – Route 53 sends automated requests over the internet to your application to verify that it's reachable, available, and functional.

  • Auto naming for service discovery – You define the configuration for DNS records and an optional health check that you want Route 53 to create whenever you register a service instance.

This Amazon Route 53 API Reference explains how to use API actions to create the following resources:

Public Hosted Zones

A public hosted zone is a container that holds information about how you want to route traffic on the internet for a domain, such as example.com, and its subdomains. See Public Hosted Zones.

Private Hosted Zones

A private hosted zone is a container that holds information about how you want to route traffic for a domain and its subdomains within one or more VPCs that you created with the Amazon VPC service. See Private Hosted Zones.

Reusable Delegation Sets

By default, each hosted zone that you create gets a different set of four name servers—a different delegation set. If you create a lot of hosted zones, maintaining different delegation sets can be difficult and time consuming. Route 53 lets you create a delegation set that you can reuse with multiple hosted zones. See Reusable Delegation Sets.

Resource Record Sets

After you create a hosted zone for your domain, such as example.com, you create resource record sets to tell the Domain Name System (DNS) how to route traffic for that domain. See Resource Record Sets.

Traffic Policies and Traffic Policy Instances

You can create complex routing configurations, known as traffic policies, that use weighted, latency, failover, and geolocation resource record sets. You can then associate a traffic policy with a domain name or subdomain name, such as www.example.com, by creating a traffic policy instance. When users submit DNS queries for the domain or subdomain, Route 53 responds based on the traffic policy that you used to create the traffic policy instance. See Traffic Policies and Traffic Policy Instances.

Health Checks

Route 53 health checks monitor the health and performance of your web applications, web servers, and other resources. At regular intervals that you specify, Route 53 submits automated requests over the internet to your application, server, or other resource to verify that it's reachable, available, and functional. See Health Checks.

Domain Registrations

When you want to get a new domain name, such as example.com, you can register it with Route 53. You can also transfer the registration for existing domains from other registrars to Route 53. See Domain Registrations.

Namespaces, Services, and Service Instances

A namespace specifies the domain name that you want to route traffic to.

You create a service in a namespace and specify the configuration for DNS records and an optional health check that you want Route 53 to create when you register a service instance. A service represents an application component, such as a web server, that can run on one or multiple service instances that you want Route 53 to route traffic to.

A service instance contains information about how Route 53 responds to DNS queries for a resource, such as an EC2 instance.

See Service Discovery.

Query Logs

You can configure Route 53 to log information about the queries that Route 53 receives, such as the domain or subdomain that was requested, the date and time of the request, and the DNS record type (such as A or AAAA). See DNS Query Logs.

Tags

A tag is a label that you assign to an AWS resource. Each tag consists of a key and a value, both of which you define. You can use tags for a variety of purposes; one common use is to categorize and track your Route 53 costs. See Tags for Hosted Zones and Health Checks and Tags for Domains.

You can also use the Route 53 API to get the current limit on Route 53 objects that you can create, such as hosted zones and health checks. See Limits for Accounts, Hosted Zones, and Reusable Delegation Sets.

In addition, the Amazon Route 53 API Reference includes the following information:

  • Making API Requests – How to submit HTTP requests to Route 53

  • Traffic Policy Document Format – Syntax and examples for the document that you include when you create a traffic policy programmatically

For information about Route 53 concepts and about how to use the Route 53 console, see the Amazon Route 53 Developer Guide.