Document history - Amazon Route 53 (original) (raw)

The following entries describe important changes in each release of the Route 53 documentation. For notification about updates to this documentation, you can subscribe to an RSS feed.

Topics

• 2025 releases
• 2024 releases
• 2023 releases
• 2022 releases
• 2021 releases
• 2020 releases
• 2018 releases
• 2017 releases
• 2016 releases
• 2015 releases
• 2014 releases
• 2013 releases
• 2012 release
• 2011 releases
• 2010 release

2025 releases

June 01, 2025

Added permissions for cloudwatch:GetMetricData ,tag:GetResources, es:ListDomainNames, es:DescribeDomains, cloudfront:GetDistributionTenantByDomain, cloudfront:GetConnectionGroup and lightsail:GetContainerServices. These permissions enable you to fetch up to 500 CloudWatch health check metrics, up to 100 names of health checks, get the domain configuration for the specified Amazon OpenSearch Service domains, and list the names of all Amazon OpenSearch Service domains owned by the current user in the active Region, fetch the CloudFront multi-tenant distributions and get the Lightsail container services. For more information, see AWS managed policy: AmazonRoute53FullAccess.

April 28, 2025

You can now associate interface VPC endpoints to Route 53 Profiles. For more information, see Associate interface VPC endpoints to a Route 53 Profile.

April 28, 2025

You can now add an alias record to a CloudFront distribution tenant. For more information, see Routing traffic to an Amazon CloudFront distribution by using your domain name.

February 27, 2025

Updated the Route 53 guide with the new console experience for Traffic Flow. For more information, see Creating and managing traffic policies and Creating and managing policy records.

January 14, 2025

Amazon Route 53 now supports alias records for OpenSearch Service custom domain endpoints. For more information, see Routing traffic to Amazon OpenSearch Service domain endpoint.

January 13, 2025

Added Route 53 Resolver DNS Firewall findings to the Security Hub. For more information, see Sending findings from Route 53 Resolver DNS Firewall to Security Hub.

2024 releases

November 15, 2024

Added Route 53 Resolver DNS Firewall Advanced, a new set of features on Route 53 Resolver DNS Firewall that allows you to identify and block DNS traffic associated with advanced DNS threats, such as DNS tunneling and Domain Generation Algorithm (DGA) based threats. For more information, see Route 53 Resolver DNS Firewall Advanced.

October 29, 2024

Added support for HTTPS, SSHFP, SVCB, and TLSA DNS record types. For more information, see Supported DNS record types.

October 3, 2024

Added support for Service Name Indication (SNI) for DoH outbound Resolver endpoints. For more information, see Values that you specify when you create or edit rules.

September 3, 2024

You can now use route53:VPCs policy condition to grant fine-grained access to managing hosted zone associations to VPCs. For more information, see Using IAM policy conditions for fine-grained access control.

August 27, 2024

AmazonRoute53ProfilesFullAccess added permissions forGetProfilePolicy and PutProfilePolicy. These are permission-only IAM actions. If an IAM principal doesn't have these permissions granted, an error will occur when attempting to share the Profile using the AWS RAM service. For more information, see AWS managed policy: AmazonRoute53ProfilesFullAccess.

August 27, 2024

AmazonRoute53ProfilesReadOnlyAccess added permission forGetProfilePolicy. This is a permission-only IAM action. If an IAM principal doesn't have this permission granted, an error will occur when attempting to access the Profile's policy using the AWS RAM service. For more information, see AWS managed policy: AmazonRoute53ProfilesReadOnlyAccess.

August 5, 2024

Added a statement id (Sid) to uniquely identity the managed policy AmazonRoute53ResolverFullAccess. For more information, see AWS managed policy: AmazonRoute53ResolverFullAccess.

August 5, 2024

Added a statement id (Sid) to uniquely identity the managed policy AmazonRoute53ResolverReadOnlyAccess. For more information, see AWS managed policy: AmazonRoute53ResolverReadOnlyAccess.

July 18, 2024

Updated the entire Route 53 guide with the new console experience for health checks. For more information, see Creating, updating, and deleting health checks.

April 30, 2024

You can now decide if a DNS Firewall rule will either inspect (default), or trust the DNS redirection chain. For more information, seeRoute 53 Resolver DNS Firewall components and settings and Rule settings in DNS Firewall.

April 22, 2024

You can now use Route 53 Profiles to share DNS-specific configurations with many VPCs and with AWS acounts. For more information, seeWhat are Amazon Route 53 Profiles?.

April 22, 2024

Added the managed policies AmazonRoute53ProfilesReadOnlyAccess andAmazonRoute53ProfilesFullAccess to grant read-only and full access to Amazon Route 53 Profiles. For more information, see AWS managed policies for Amazon Route 53.

February 5, 2024

You can now use Amazon EventBridge for real time alerts with DNS Firewall. For more information, seeManaging Route 53 Resolver DNS Firewall events using Amazon EventBridge.

January 9, 2024

You can now use the DNS query type as an optional value for DNS Firewall rule to differentiate the rule's response for a specific DNS query type. For more information, seeRoute 53 Resolver DNS Firewall components and settings and Rule settings in DNS Firewall.

January 9, 2024

You can now use the Quick create record or the Create record wizard to create geoproximity routing records. For more information, seeGeoproximity routing, Values specific for geoproximity records, and Values specific for geoproximity alias records.

2023 releases

December 20, 2023

You can now use DNS over HTTPS with Route 53 Resolver endpoints. For more information, see Choosing protocols for the endpoints.

July 20, 2023

Amazon Route 53 on Outposts is now available on AWS Outposts racks. It includes a Resolver that caches all DNS queries that originate from the AWS Outposts. You can also set up hybrid connectivity between an Outpost and an on-premises DNS resolver when you deploy inbound and outbound endpoints. For more information, see What is Amazon Route 53 on Outposts?.

July 19, 2023

You can now use Local Zones with geoproximity routing (traffic flow only) after you enable them. For more information, see Geoproximity routing and Traffic Policy Document Format.

March 22, 2023

Updated the entire Route 53 guide with the new console experience for domains. You can also use the new console experience to transfer a domain from one AWS account to another AWS account. For more information, see Registering a new domain and Transferring domains.

March 10, 2023

You can now connect to your resources by using IPv4, IPv6, or dual-stack endpoints with Amazon Route 53 Resolver. For more information, see Values that you specify when you create or edit inbound endpoints and Values that you specify when you create or edit outbound endpoints.

2022 releases

September 21, 2022

You can now use policy conditions for giving users fine-grained access to updating resource record sets in Amazon Route 53. For more information, see Using IAM policy conditions for fine-grained access control.

August 30, 2022

Amazon Route 53 now supports alias records for AWS App Runner services that are created after August 1, 2022. For more information, see Routing traffic to an AWS App Runner service.

June 1, 2022

IP-based routing option is now available in Amazon Route 53. For more information, see IP-based routing.

March 16, 2022

Geolocation and latency-based routing options are now supported for private hosted zones in Amazon Route 53. For more information, see Considerations when working with a private hosted zone.

January 25, 2022

The process for changing ownership for .com.au and .net.au TLDs has been simplified to include responding to two emails (by both old and new registrants) and doesn't include filling in forms. For more information, see .com.au (Australia) and .net.au (Australia).

2021 releases

2020 releases

2018 releases

December 20, 2018

You can create Route 53 alias records that route traffic to API Gateway APIs or to Amazon VPC interface endpoints. For more information, see Value/route traffic to.

November 28, 2018

Route 53 Auto Naming (also known as Service Discovery) is now a separate service, AWS Cloud Map. For more information, see the AWS Cloud Map Developer Guide.

November 19, 2018

You can use Route 53 Resolver to configure DNS resolution between your VPC and your network over a Direct Connect or VPN connection. (Resolver is the new name for the recursive DNS service that is provided to all customers by default in Amazon Virtual Private Cloud (Amazon VPC).) This lets you forward DNS queries from resolvers on your network to Route 53 Resolver. Resolver also lets you forward queries for selected domain names (example.com) and subdomain names (api.example.com) from a VPC to resolvers on your network. For more information, see What is Amazon Route 53 Resolver?.

November 7, 2018

When you're using Route 53 traffic flow and geoproximity routing, you can use an interactive map to visualize how your end users will be routed to your endpoints around the world. For more information, see Viewing a map that shows the effect of geoproximity settings.

October 18, 2018

You can use the Route 53 console and API to temporarily disable a Route 53 health check. This gives you an easy way to pause monitoring of an endpoint, such a web server, so that you can perform maintenance on it without triggering alarms or generating unnecessary logs or status messages. For more information, see "Disabled" in Values that you specify when you create or update health checks. The feature is available for all three types of Route 53 health checks: health checks that monitor an endpoint, health checks that monitor other health checks, and health checks that monitor a CloudWatch alarm.

March 13, 2018

If you're using auto naming, you can now use a third-party health checker to evaluate the health of your resources. This is useful when a resource isn't available over the internet, for example, because the instance is in an Amazon VPC. For more information, see HealthCheckCustomConfig in the Amazon Route 53 API Reference.

March 9, 2018

IAM now includes managed policies for auto naming. For more information, see AWS managed policies for Amazon Route 53.

February 6, 2018

You can now configure auto naming to create alias records that route traffic to ELB load balancers or to create CNAME records. For more information, see Attributes in the documentation for the RegisterInstance API in the Amazon Route 53 API Reference.

2017 releases

December 5, 2017

You can now use the Route 53 autonaming API to provision instances for microservices. Autonaming lets you automatically create DNS records and, optionally, health checks based on a template that you define. For more information, see What is AWS Cloud Map? in the AWS Cloud Map Developer Guide.

November 16, 2017

You can now programmatically get both the current quotas on Route 53 resources such as hosted zones and health checks, and the number of each resource that you're currently using. For more information, see GetAccountLimit, GetHostedZoneLimit, and GetReusableDelegationSetLimit in the Amazon Route 53 API Reference.

October 3, 2017

Route 53 is now a HIPAA eligible service. For more information, see Compliance validation for Amazon Route 53.

September 29, 2017

You can now programmatically check whether a domain can be transferred to Route 53. For more information, see CheckDomainTransferability in the Amazon Route 53 API Reference.

September 11, 2017

You can now create Route 53 alias records that route internet traffic to Elastic Load Balancing Network Load Balancers. For more information about alias records, see Choosing between alias and non-alias records.

September 7, 2017

If you're using Route 53 as your public, authoritative DNS service, you can now log DNS queries that Route 53 receives. For more information, see Public DNS query logging.

September 1, 2017

If you're using Route 53 traffic flow, you can now use geoproximity routing, which lets you route traffic based on the physical distance between your users and your resources. You can also route more or less traffic to each resource by specifying a positive or negative bias. For more information, see Geoproximity routing.

August 21, 2017

You can now use Route 53 to create Certification Authority Authorization (CAA) records, which let you specify the certificate authorities that can issue certificates for your domains and subdomains. For more information, see CAA record type.

August 18, 2017

You can now transfer large numbers of domains to Route 53 using the Route 53 console. For more information, see Transferring registration for a domain to Amazon Route 53.

August 4, 2017

When you register a domain, the registries for some top-level domains (TLDs) require you to verify that you specified a valid email address for the registrant contact. You can now send the verification email and get confirmation that you successfully verified the email address during the domain registration process. For more information, see Registering a new domain.

June 21, 2017

If you want to route traffic approximately randomly to multiple resources, such as web servers, you can now create one multivalue answer record for each resource and, optionally, associate a Route 53 health check with each record. Route 53 responds to DNS queries with up to eight healthy records in response to each DNS query, and gives different answers to different DNS resolvers. For more information, see Multivalue answer routing.

April 10, 2017

When you use the Route 53 console to transfer a domain registration to Route 53, you can now choose one of the following options for associating the name servers for the DNS service for the domain with the transferred domain registration:

• Use the name servers for a Route 53 hosted zone that you choose
• Use the name servers for the current DNS service for the domain
• Use name servers that you specify

Route 53 automatically associates these name servers with the transferred domain registration.

2016 releases

November 21, 2016

You can now create health checks that use IPv6 addresses to check the health of endpoints. For more information, see Creating and updating health checks.

November 15, 2016

You can now use a Route 53 API action to associate an Amazon VPC that you created with one account with a private hosted zone that you created with another account. For more information, see Associating an Amazon VPC and a private hosted zone that you created with different AWS accounts.

August 30, 2016

With this release, Route 53 adds the following new features:

• Name Authority Pointer (NAPTR) records – You can now create NAPTR records, which are used by Dynamic Delegation Discovery System (DDDS) applications to convert one value to another or to replace one value with another. For example, one common use is to convert phone numbers into SIP URIs. For more information, see NAPTR record type.
• DNS query test tool – You can now simulate DNS queries for a record and see the value that Route 53 returns. For geolocation and latency records, you can also simulate requests from a particular DNS resolver and/or client IP address to find out what response Route 53 would return to a client with that resolver and/or IP address. For more information, see Checking DNS responses from Route 53.

August 11, 2016

With this release, you can create alias records that route traffic to ELB Application Load Balancers. The process is the same as for Classic Load Balancers. For more information, see Value/route traffic to.

August 9, 2016

With this release, Route 53 adds support for DNSSEC for domain registration. DNSSEC lets you protect your domain from DNS spoofing attacks, which are also known as man-in-the-middle attacks. For more information, see Configuring DNSSEC for a domain.

July 7, 2016

You can now manually extend the registration for a domain and register a domain with an initial registration period longer than the minimum registration period specified by the registry. For more information, see Extending the registration period for a domain.

July 6, 2016

If you're an AISPL customer with a contact address in India, you can now use Route 53 to register domains. For more information, see Managing an Account in India.

May 26, 2016

With this release, Route 53 adds the following new features:

• Domain billing report – You can now download a report that lists all domain registration charges, by domain, for a specified time period. The report includes all domain registration operations for which there is a fee, including registering domains, transferring domains to Route 53, renewing domain registration, and (for some TLDs), changing the owner of a domain. For more information, see the following documentation:
  • Route 53 console – See Downloading a domain billing report
  • Route 53 API – See ViewBilling in the Amazon Route 53 API Reference.
• New TLDs – You can now register domains that have the following TLDs: .college, .consulting, .host, .name, .online, .republican, .rocks, .sucks, .trade, .website, and .uk. For more information, see Domains that you can register with Amazon Route 53.
• New APIs for domain registration – For operations that require confirmation that the email address for the registrant contact is valid, such as registering a new domain, you can now programmatically determine whether the registrant contact has clicked the link in the confirmation email and, if not, whether the link is still valid. You can also programmatically request that we send another confirmation email. For more information, see the following documentation in the Amazon Route 53 API Reference:
  • GetContactReachabilityStatus
  • ResendContactReachabilityEmail

April 5, 2016

With this release, Route 53 adds the following new features:

• Health checks based on CloudWatch metrics – You can now create health checks that are based on the alarm state of any CloudWatch metric. This is useful for checking the health of endpoints that can't be reached by a standard Route 53 health check, such as instances within an Amazon Virtual Private Cloud (VPC) that have only private IP addresses. For more information, see the following documentation:
  • Route 53 console – See Monitoring a CloudWatch alarm in the "Values that You Specify When You Create or Update Health Checks" topic.
  • Route 53 API – See CreateHealthCheck and UpdateHealthCheck in the Amazon Route 53 API Reference.
• Configurable health check locations – You can now choose the Route 53 health checking regions that check the health of your resources, which reduces the load on the endpoint from health checks. This is useful if your customers are concentrated in one or a few geographic regions. For more information, see the following documentation:
  • Route 53 console – See Advanced configuration ("Monitor an Endpoint" only) in the "Values that You Specify When You Create or Update Health Checks" topic.
  • Route 53 API – See the Regions element for CreateHealthCheck and UpdateHealthCheck in the Amazon Route 53 API Reference.
• Failover in private hosted zones – You can now create failover and failover alias records in a private hosted zone. When you combine this feature with metric-based health checks, you can configure DNS failover even for endpoints that have only private IP addresses and can't be reached by using standard Route 53 health checks. For more information, see the following documentation:
  • Route 53 console – See Configuring failover in a private hosted zone.
  • Route 53 API – See ChangeResourceRecordSets in the Amazon Route 53 API Reference.
• Alias records in private hosted zones – In the past, you could create alias records that route DNS queries only to other Route 53 records in the same hosted zone. With this release, you can also create alias records that route DNS queries to Elastic Beanstalk environments that have regionalized subdomains, Elastic Load Balancing load balancers, and Amazon S3 buckets. (You still can't create alias records that route DNS queries to a CloudFront distribution.) For more information, see the following documentation:
  • Route 53 console – See Choosing between alias and non-alias records.
  • Route 53 API – See ChangeResourceRecordSets in the Amazon Route 53 API Reference.

February 23, 2016

When you create or update HTTPS health checks, you can now configure Route 53 to send the host name to the endpoint during TLS negotiation. This allows the endpoint to respond to the HTTPS request with the applicable SSL/TLS certificate. For more information, see the description for the SNI in Advanced configuration ("Monitor an Endpoint" only) field in the "Values that You Specify When You Create or Update Health Checks" topic. For information about how to enable SNI when you use the API to create or update a health check, see CreateHealthCheck and UpdateHealthCheck in the Amazon Route 53 API Reference.

January 27, 2016

You can now register domains for over 100 additional top-level domains (TLDs) such as .accountants, .band, and .city. For a complete list of supported TLDs, see Domains that you can register with Amazon Route 53.

January 19, 2016

You can now create alias records that route traffic to Elastic Beanstalk environments. For information about creating records by using the Route 53 console, see Creating records by using the Amazon Route 53 console. For information about using the API to create records, see ChangeResourceRecordSets in the Amazon Route 53 API Reference.

2015 releases

December 3, 2015

The Route 53 console now includes a visual editor that lets you quickly create complex routing configurations that use a combination of Route 53 weighted, latency, failover, and geolocation routing policies. You can then associate the configuration with one or more domain names (such as example.com) or subdomain names (such as www.example.com), in the same hosted zone or in multiple hosted zones. In addition, you can roll back the updates if the new configuration isn't performing as you expected it to. The same functionality is available by using the Route 53 API, AWS SDKs, the AWS CLI, and AWS Tools for Windows PowerShell. For information about using the visual editor, see Using Traffic Flow to route DNS traffic. For information about using the API to create traffic flow configurations, see the Amazon Route 53 API Reference.

October 19, 2015

With this release, Route 53 adds the following new features:

• Domain registration for .com and .net domains by Amazon Registrar, Inc. – Amazon is now an ICANN-accredited registrar for the .com and .net top-level domains (TLDs) through Amazon Registrar, Inc. When you use Route 53 to register a .com or .net domain, Amazon Registrar will be the registrar of record and will be listed as the "Sponsoring Registrar" in your Whois query results. For information about using Route 53 to register domains, see Registering and managing domains using Amazon Route 53.
• Privacy protection for .com and .net domains – When you register a .com or .net domain with Route 53, all of your personal information, including first and last name, is now hidden. First and last name are not hidden for other domains that you register with Route 53. For more information about privacy protection, see Enabling or disabling privacy protection for contact information for a domain.

September 15, 2015

With this release, Route 53 adds the following new features:

• Calculated health checks – You can now create health checks whose status is determined by the health status of other health checks. For more information, see Creating and updating health checks. In addition, see CreateHealthCheck in the Amazon Route 53 API Reference.
• Latency measurements for health checks – You can now configure Route 53 to measure the latency between health checkers and your endpoint. Latency data appears in Amazon CloudWatch graphs in the Route 53 console. To enable latency measurements for new health checks, see the Latency measurements setting under Advanced configuration ("Monitor an Endpoint" only) in the topic Values that you specify when you create or update health checks. (You can't enable latency measurements for existing health checks.) In addition, see MeasureLatency in the topic CreateHealthCheck in the Amazon Route 53 API Reference.
• Updates to the health checks dashboard in the Route 53 console – The dashboard for monitoring health checks has been improved in a variety of ways, including CloudWatch graphs for monitoring latency between Route 53 health checkers and your endpoints. For more information, see Monitoring health check status and getting notifications.

March 3, 2015

The Amazon Route 53 Developer Guide now explains how to configure white-label name servers for Route 53 hosted zones. For more information, see Configuring white-label name servers.

February 26, 2015

You can now use the Route 53 API to list the hosted zones that are associated with an AWS account in alphabetical order by name. You can also get a count of the hosted zones that are associated with an account. For more information, see ListHostedZonesByName andGetHostedZoneCount in the Amazon Route 53 API Reference.

February 11, 2015

With this release, Route 53 adds the following new features:

• Health Check Status – The health checks page in the Route 53 console now includes a Status column that lets you view the overall status of all of your health checks. For more information, see Viewing health check status and the reason for health check failures.
• Integration with AWS CloudTrail – Route 53 now works with CloudTrail to capture information about every request that your AWS account sends to the Route 53 API. Integrating Route 53 and CloudTrail lets you determine which requests were made to the Route 53 API, the source IP address from which each request was made, who made the request, when it was made, and more. For more information, see Logging Amazon Route 53 API calls with AWS CloudTrail.
• Quick Alarms for Health Checks – When you create a health check by using the Route 53 console, you can now simultaneously create an Amazon CloudWatch alarm for the health check and specify who to notify when Route 53 considers the endpoint unhealthy for one minute. For more information, see Creating and updating health checks.
• Tagging for Hosted Zones and Domains – You can now assign tags, which are commonly used for cost allocation, to Route 53 hosted zones and domains. For more information, see Tagging Amazon Route 53 resources.

February 5, 2015

You can now use the Route 53 console to update contact information for a domain. For more information, see Values that you specify when you register or transfer a domain.

January 22, 2015

You can now specify internationalized domain names when you're registering a new domain name with Route 53. (Route 53 already supported internationalized domain names for hosted zones and records.) For more information, see DNS domain name format.

2014 releases

November 25, 2014

With this release, you can now edit the comment that you specified for a hosted zone when you created it. In the console, you just click the pencil icon next to the Comment field and enter a new value. For more information about changing the comment by using the Route 53 API, see UpdateHostedZoneComment in the Amazon Route 53 API Reference.

November 5, 2014

With this release, Route 53 adds the following new features:

• Private DNS for VPCs created using the Amazon Virtual Private Cloud service – You can now use Route 53 to manage your internal domain names for VPCs without exposing DNS data to the public internet. For more information, see Working with private hosted zones.
• Health check failure reasons – You can now see the current status of a selected health check, as well as details on why the health check last failed, as reported by each of the Route 53 health checkers. The status includes the HTTP status code, and failure reasons include information about numerous types of failures, such as string matching failures and response timeouts. For more information, see Viewing health check status and the reason for health check failures.
• Reusable delegation sets – You can now apply the same set of four authoritative name servers, known collectively as a delegation set, to multiple hosted zones that correspond with different domain names. This greatly simplifies the process of migrating DNS service to Route 53 and managing large numbers of hosted zones. Using reusable delegation sets currently requires that you use the Route 53 API or an AWS SDK. For more information, see the Amazon Route 53 API Reference.
• Improved geolocation routing – We further improved the accuracy of geolocation routing by adding support for the edns-client-subnet extension of EDNS0. For more information, see Geolocation routing.
• Support for Signature v4 – You can now sign all Route 53 API requests using Signature version 4. For more information, see Signing Route 53 API Requests in the Amazon Route 53 API Reference.

July 31, 2014

With this release, you can now do the following:

• Register domain names using Route 53. For more information, see Registering and managing domains using Amazon Route 53.
• Configure Route 53 to respond to DNS queries based on the geographic location that the queries originate from. For more information, see Geolocation routing.

July 2, 2014

With this release, you can now do the following:

• Edit most values in health checks. For more information, see Creating, updating, and deleting health checks.
• Use the Route 53 API to get a list of the IP ranges that Route 53 health checkers use to check the health of your resources. You can use these IP addresses to configure your router and firewall rules to allow health checkers to check the health of your resources. For more information, see GetCheckerIpRanges in the Amazon Route 53 API Reference.
• Assign cost allocation tags to health checks, which also lets you assign a name to health checks. For more information, see Naming and tagging health checks.
• Use the Route 53 API to get the number of health checks that are associated with your AWS account. For more information, see GetHealthCheckCount in the Amazon Route 53 API Reference.

April 30, 2014

With this release, you can now create health checks and use a domain name instead of an IP address to specify the endpoint. This is helpful when an endpoint's IP address either is not fixed or is served by multiple IPs, such as Amazon EC2 or Amazon RDS instances. For more information, see Creating and updating health checks.

In addition, some information about using the Route 53 API that formerly appeared in the Amazon Route 53 Developer Guide has been moved. Now all API documentation appears in the Amazon Route 53 API Reference.

April 18, 2014

With this release, Route 53 passes a different value in the Host header when the health check Port value is 443 and the Protocol value is HTTPS. During a health check, Route 53 now passes to the endpoint a Host header that contains the value of the Host Name field. If you created the health check by using the CreateHealthCheck API action, this is the value of the FullyQualifiedDomainName element.

For more information, see Creating, updating, and deleting health checks.

April 9, 2014

With this release, you can now view what percentage of Route 53 health checkers are currently reporting that an endpoint is healthy.

In addition, behavior of the Health Check Status metric in Amazon CloudWatch now shows only zero (if your endpoint was unhealthy during a given time period) or one (if the endpoint was healthy for that time period). The metric no longer shows values between 0 and 1 reflecting the portion of Route 53 health checks that are reporting the endpoint as healthy.

For more information, see Monitoring health checks using CloudWatch.

February 18, 2014

With this release, Route 53 adds the following features:

• Health check failover threshold: You can now specify how many consecutive health checks an endpoint must fail before Route 53 considers the endpoint unhealthy, between 1 and 10 consecutive checks. An unhealthy endpoint must pass the same number of checks to be considered healthy. For more information, see How Amazon Route 53 determines whether a health check is healthy.
• Health check request interval: You can now specify how frequently Route 53 sends requests to an endpoint to determine whether the endpoint is healthy. Valid settings are 10 seconds and 30 seconds. For more information, see How Amazon Route 53 determines whether a health check is healthy.

January 30, 2014

With this release, Route 53 adds the following features:

• HTTP and HTTPS string-match health checks: Route 53 now supports health checks that determine the health of an endpoint based on the appearance of a specified string in the response body. For more information, see How Amazon Route 53 determines whether a health check is healthy.
• HTTPS health checks: Route 53 now supports health checks for secure, SSL-only websites. For more information, see How Amazon Route 53 determines whether a health check is healthy.
• UPSERT for the ChangeResourceRecordSets API Action: When creating or changing records using the ChangeResourceRecordSets API action, you can now use the UPSERT action either to create a new record if none exists with a given name and type, or to update an existing record. For more information, see ChangeResourceRecordSets in the Amazon Route 53 API Reference.

January 7, 2014

With this release, Route 53 adds support for health checks that determine the health of an endpoint based on whether a specified string appears in the response body. For more information, see How Amazon Route 53 determines whether a health check is healthy.

2013 releases

August 14, 2013

With this release, Route 53 adds support for creating records by importing a BIND-formatted zone file. For more information, see Creating records by importing a zone file.

In addition, CloudWatch metrics for Route 53 health checks have been integrated into the Route 53 console and streamlined. For more information, see Monitoring health checks using CloudWatch.

June 26, 2013

With this release, Route 53 adds support for integrating health checks with CloudWatch metrics so you can do the following:

• Verify that a health check is properly configured.
• Review the health of a health check endpoint over a specified period of time.
• Configure CloudWatch to send an Amazon Simple Notification Service (Amazon SNS) alert when all Route 53 health checkers consider your specified endpoint to be unhealthy.

For more information, see Monitoring health checks using CloudWatch.

June 11, 2013

With this release, Route 53 adds support for creating alias records that route DNS queries to alternate domain names for Amazon CloudFront distributions. You can use this feature both for alternate domain names at the zone apex (example.com) and alternate domain names for subdomains (www.example.com). For more information, see Routing traffic to an Amazon CloudFront distribution by using your domain name.

May 30, 2013

With this release, Route 53 adds support for evaluating the health of ELB load balancers and the associated Amazon EC2 instances. For more information, see Creating Amazon Route 53 health checks .

March 28, 2013

The documentation about health checks and failover was rewritten to enhance usability. For more information, see Creating Amazon Route 53 health checks .

February 11, 2013

With this release, Route 53 adds support for failover and health checks. For more information, see Creating Amazon Route 53 health checks .

2012 release

March 21, 2012

With this release, Route 53 lets you create latency records. For more information, see Latency-based routing.

2011 releases

December 21, 2011

With this release, the Route 53 console in the AWS Management Console lets you create an alias record by choosing an Elastic Load Balancer from a list instead of manually entering the hosted zone ID and the DNS name of the load balancer. New functionality is documented in the Amazon Route 53 Developer Guide.

November 16, 2011

With this release, you can use the Route 53 console in the AWS Management Console to create and delete hosted zones, and to create, change, and delete records. New functionality is documented throughout the Amazon Route 53 Developer Guide, as applicable.

October 18, 2011

The Amazon Route 53 Getting Started Guide was merged into the Amazon Route 53 Developer Guide, and the Developer Guide was reorganized to enhance usability.

May 24, 2011

This release of Amazon Route 53 introduces alias records, which allow you to create zone apex aliases; weighted records; a new API (2011-05-05); and a service-level agreement. In addition, after six months in beta, Route 53 is now generally available. For more information, see the Amazon Route 53 product page and Choosing between alias and non-alias records in the Amazon Route 53 Developer Guide.

2010 release

December 5, 2010

This is the first release of Amazon Route 53 Developer Guide.