Integration with Other Services
You can integrate Amazon Route 53 with other AWS services to log requests that are sent to the Amazon Route 53 API, monitor the status of your resources, and assign tags to your resources. In addition, you can use Amazon Route 53 to route Internet traffic to your AWS resources.
Logging, Monitoring, and Tagging
- AWS CloudTrail
Amazon Route 53 is integrated with AWS CloudTrail, a service that captures information about every request that is sent to the Amazon Route 53 API by your AWS account. You can use information in the CloudTrail log files to determine which requests were made to Amazon Route 53, the source IP address from which each request was made, who made the request, when it was made, and so on.
For more information, see Using AWS CloudTrail to Capture Requests Sent to the Amazon Route 53 API.
- Amazon CloudWatch
You can use Amazon CloudWatch to monitor the status—healthy or unhealthy—of your Amazon Route 53 health checks. Health checks monitor the health and performance of your web applications, web servers, and other resources. At regular intervals that you specify, Amazon Route 53 submits automated requests over the Internet to your application, server, or other resource to verify that it's reachable, available, and functional.
For more information, see Monitoring Health Checks Using CloudWatch.
- Tag Editor
A tag is a label that you assign to an AWS resource, including Amazon Route 53 domains, hosted zones, and health checks. Each tag consists of a key and a value, both of which you define. For example, you might assign a tag to a domain registration that has the key "Customer" and the value "Example Corp." You can use tags for a variety of purposes; one common use is to categorize and track your AWS costs.
For more information, see Tagging Amazon Route 53 Resources.
Routing Traffic to Other AWS Resources
You can use Amazon Route 53 to route traffic to a variety of AWS resources.
- Amazon CloudFront
To speed up delivery of your web content, you can use Amazon CloudFront, the AWS content delivery network (CDN). CloudFront can deliver your entire website—including dynamic, static, streaming, and interactive content—by using a global network of edge locations. CloudFront routes requests for your content to the edge location that gives your users the lowest latency. You can use Amazon Route 53 to route traffic for your domain to your CloudFront distribution. For more information, see Routing Traffic to an Amazon CloudFront Web Distribution by Using Your Domain Name.
- Amazon EC2
Amazon EC2 provides scalable computing capacity in the AWS Cloud. You can launch an EC2 virtual computing environment (an instance) using a preconfigured template (an Amazon Machine Image, or AMI). When you launch an EC2 instance, EC2 automatically installs the operating system (Linux or Microsoft Windows) and additional software included in the AMI, such as web server or database software.
If you host a website or run a web application on an EC2 instance, you can route traffic for your domain, such as example.com, to your server by using Amazon Route 53. For more information, see Routing Traffic to an Amazon EC2 Instance.
- AWS Elastic Beanstalk
If you use AWS Elastic Beanstalk to deploy and manage applications in the AWS Cloud, you can use Amazon Route 53 to route DNS traffic for your domain, such as example.com, to an Elastic Beanstalk environment. For more information, see Routing Traffic to an AWS Elastic Beanstalk Environment.
- Elastic Load Balancing
If you host a website on multiple Amazon EC2 instances, you can distribute traffic to your website across the instances by using an Elastic Load Balancing (ELB) load balancer. The ELB service automatically scales the load balancer as traffic to your website changes over time. The load balancer also can monitor the health of its registered instances and route domain traffic only to healthy instances.
You can use Amazon Route 53 to route traffic for your domain to your Classic Load Balancer or Application Load Balancer. For more information, see Routing Traffic to an ELB Load Balancer.
- Amazon RDS
If you use an Amazon RDS database instance for data storage for your web application, the domain name that is assigned to your DB instance is a long, partially random, alphanumeric string, such as
myexampledb.a1b2c3d4wxyz.us-west-2.rds.amazonaws.com. If you want to use a domain name that's easier to remember, you can use Amazon Route 53 to associate your domain name, such as
productdata.example.com, with the domain name of your DB instance. For more information, see Opening Connections to an Amazon RDS Database Instance Using Your Domain Name.
- Amazon S3
Amazon Simple Storage Service (Amazon S3) provides secure, durable, highly scalable cloud storage. You can configure an S3 bucket to host a static website that can include web pages and client-side scripts. (S3 doesn't support server-side scripting.) You can use Amazon Route 53 to route traffic to an Amazon S3 bucket. For more information, see the following topics:
For information about routing traffic to a bucket, see Routing Traffic to a Website that Is Hosted in an Amazon S3 Bucket.
For a more detailed explanation of how to host a static website in an S3 bucket, see Getting Started with Amazon Route 53.
- Amazon WorkMail
If you're using Amazon WorkMail for your business email and you're using Amazon Route 53 as your DNS service, you can use Amazon Route 53 to route traffic to your Amazon WorkMail email domain. For more information, see Routing Traffic to Amazon WorkMail.