When to use Route 53 Aliases

Last Updated : 06-Oct-2020

Amazon Route 53 alias records provide a Route 53–specific extension to DNS functionality. Alias records let you route traffic to selected AWS resources, such as CloudFront distributions and Amazon S3 buckets. They also let you route traffic from one record in a hosted zone to another record.


Note that alias record change are instant as they internal to AWS.

When you use an alias record to route traffic to an AWS resource, Route 53 automatically recognizes changes in the resource. For example, suppose an alias record for example.com points to an ELB load balancer at lb1-1234.us-east-2.elb.amazonaws.com. If the IP address of the load balancer changes, Route 53 automatically starts to respond to DNS queries using the new IP address.

Alias Examples

When Route 53 receives a DNS query for an alias record, Route 53 responds with one or more values for that resource:

  • An Amazon API Gateway custom regional API or edge-optimized API
  • An Amazon VPC interface endpoint
  • A CloudFront distribution
  • An Elastic Beanstalk environment
  • An ELB load balancer
  • An AWS Global Accelerator accelerator
  • An Amazon S3 bucket that is configured as a static website
  • Another Route 53 record in the same hosted zone

Zone Apex Alias

Unlike a CNAME record, you can create an alias record at the top node of a DNS namespace, also known as the zone apex. For example, if you register the DNS name example.com, the zone apex is example.com. You create an alias record for example.com that routes traffic to www.example.com.


Using Template: Template Post
magnifier linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram