Paying for What You Use
With Amazon Route 53, you don’t have to pay any upfront fees or commit to the number of queries the service answers for your domain. Like with other AWS services, you pay as you go and only for what you use:
- Managing hosted zones: You pay a monthly charge for each hosted zone managed with Route 53.
- Serving DNS queries: You incur charges for every DNS query answered by the Amazon Route 53 service, except for queries to Alias A records that are mapped to Elastic Load Balancing instances, CloudFront distributions, AWS Elastic Beanstalk environments, API Gateways, VPC endpoints, or Amazon S3 website buckets, which are provided at no additional charge.
- Managing domain names: You pay an annual charge for each domain name registered via or transferred into Route 53.
Your monthly bill from AWS will list your total usage and dollar amount for the Amazon Route 53 service separately from other AWS services.
Hosted Zones and Records
Queries for qualifying alias records are provided at no additional cost to Route 53 customers. You can create alias records for AWS resources, such as:
- Elastic Load Balancers
- Amazon CloudFront distributions
- AWS Elastic Beanstalk environments
- Amazon S3 buckets that are configured as website endpoints
For a complete list of the AWS resource types that are supported for alias records, see Alias Target in the Amazon Route 53 Developer Guide.
You can create alias records for all of the query types that appear on your Amazon Route 53 usage report—namely:
- Standard queries (records with failover, multivalue answer, and weighted routing policies), listed as “Intra-AWS-DNS-Queries” on the Amazon Route 53 usage report
- Latency-based routing queries (records with latency routing policies), listed as “Intra-AWS-LBR-Queries” on the Amazon Route 53 usage report
- Geo queries (geolocation and geoproximity routing policies), listed as “Intra-AWS-Geo-Queries” on the Amazon Route 53 usage report
- IP-based routing queries (records with IP-based routing policies), listed as “Intra-AWS-Cidr-Queries” on the Amazon Route 53 usage report
DNS queries are free when both of the following are true:
- The domain or subdomain name (example.com or acme.example.com) and the record type (A) in the query match an alias record.
- The alias target is an AWS resource other than another Route 53 record.
We charge the standard rate for DNS queries for which the domain name and type match a record, but the alias target of the record is a non-alias record in the same hosted zone. We do not charge for DNS queries if you create a chain of alias records that reference other alias records, and the last alias record in the chain references an AWS resource such as an ELB load balancer. For example, suppose a.example.com is an alias record that references another alias record, b.example.com. If b.example.com routes traffic to an AWS resource such as an ELB load balancer, DNS queries are free for both a.example.com and b.example.com.
Get Started With DNS Failover At No Additional Cost*
New and existing customers can create up to 50 health checks for AWS endpoints** that are within or linked to the same AWS account.
The monthly health check prices listed above are prorated for partial months.
Need more than 200 health checks? Please contact us.
* New and existing customers are not charged for health checks on up to 50 AWS endpoints (described below) that are within or linked to their AWS account (the “Offer”). The Offer is subject to the AWS Customer Agreement and is a Special Pricing Program under the AWS Service Terms. You will be charged AWS’s standard rates for any use that exceeds the usage amount provided at no additional cost under the Offer. Unused usage amounts remaining at the end of the Offer term do not roll over. When calculating your use of AWS services under the Offer, we will aggregate your use across all AWS regions.
** An "AWS endpoint" is a resource running within AWS (e.g., an Amazon EC2 instance) that is provisioned within the same AWS account as the health check or billed to the same account as the health check. Calculated health checks and metric based health checks are billed as health checks of an AWS endpoint. You are not billed for health checks of Elastic Load Balancing resources or Amazon S3 buckets that are configured as website endpoints. Health checks of Elastic Load Balancing resources and Amazon S3 website bucket endpoints are provisioned automatically by AWS and are available for no additional charge as part of Amazon Route 53.
Route 53 Resolver Endpoints
Route 53 Resolver Query Logs
Amazon Route 53 does not charge for Resolver query logs. However, when you configure DNS query logging, you incur Amazon CloudWatch, Amazon S3 or Amazon Kinesis Data Firehose charges depending upon the destination target you choose for your logs. For information about log charges, see the “Logs” section on the Amazon CloudWatch pricing page.
Route 53 Resolver DNS Firewall
Route 53 Application Recovery Controller
You pay for Route 53 Application Recovery Controller based on two dimensions: readiness checks and clusters. You pay only for what you use and there are no upfront charges to use Route 53 Application Recovery Controller.
Readiness check: Readiness check audits your resources across Availability Zones or Regions to help you ensure that they are prepared for a recovery. You pay $0.045 per hour for every readiness check that you configured. For example, if you have modeled an application using Route 53 Application Recovery Controller and have a readiness check for Auto Scaling Groups and another for DynamoDB tables, you will have two readiness checks configured, each charging $0.045. So, your total readiness check bill will be $0.09 per hour.
Cluster: A cluster is a set of redundant regional endpoints against which you can execute API calls to update or get the state of one or more routing controls. You pay $2.5 per hour for every cluster configured. Each cluster (maximum 2) can host multiple routing controls, which you can use to trigger failovers.
Pricing for domain names varies by TLD. View a full list of current pricing by TLD. Domain names are registered in annual increments. Prices listed are per domain-year unless otherwise noted. We do not currently offer volume discount pricing for domain registrations.
There is a limit of 20 domain name registrations per account. To request a higher limit, please contact us.
Amazon Route 53 does not charge you to enable DNSSEC signing on your public hosted zones or to enable DNSSEC validation for Amazon Route 53 Resolver. However, when you enable DNSSEC signing on your public hosted zones, you incur AWS Key Management Service (KMS) charges for storing the private key and using the instances of the key to sign your zones. For more information about KMS charges, see the AWS KMS pricing page.
Note that you can choose to use a single customer-managed AWS KMS key that is stored in KMS across multiple public hosted zones.
Public DNS Query Logs
Amazon Route 53 does not charge for public DNS query logs. However, when you configure DNS query logging, you incur Amazon CloudWatch charges in the US East (N.Virginia) Region including data ingestion, archival storage, and analysis. For information about CloudWatch charges, see the Amazon CloudWatch pricing page.
The CloudWatch charges depend on the size of entries in your DNS query logs. For more information, see Values that Appear in DNS Query Logs in the Amazon Route 53 Developer Guide.
Taxes and Promotional Credits
The prices above are exclusive of applicable taxes, fees, or similar governmental charges, if any exist, except as otherwise noted. You may not use Promotional Credit for any fees or charges for Amazon Route 53 domain name registration. For more information regarding use of Promotional Credits, please click here.
API Calls Between Amazon Route 53 and Amazon Simple Storage Service (Amazon S3)
Using the Amazon Route 53 console can generate API calls to Amazon Simple Storage Service (Amazon S3). Actions such as identifying Alias record targets sends API calls to S3, such as LIST_ALL_MY_BUCKETS. Depending on how many times you initiate this workflow, the API calls made to S3 may cause charges to appear in your S3 bill as LIST requests. See the S3 Pricing Page for more information.