# Routing internet traffic to your AWS resources


You can use Amazon Route 53 to route traffic to a variety of AWS resources. 
+ [Routing traffic to an Amazon API Gateway API by using your domain name](routing-to-api-gateway.md)
+ [Routing traffic to an Amazon CloudFront distribution by using your domain name](routing-to-cloudfront-distribution.md)
+ [Routing traffic to an Amazon EC2 instance](routing-to-ec2-instance.md)
+ [Routing traffic to an AWS App Runner service](routing-to-app-runner.md)
+ [Routing traffic to an AWS Global Accelerator](routing-to-global-accelerator.md)
+ [Routing traffic to an AWS Elastic Beanstalk environment](routing-to-beanstalk-environment.md)
+ [Routing traffic to an ELB load balancer](routing-to-elb-load-balancer.md)
+ [Routing traffic to a website that is hosted in an Amazon S3 bucket](RoutingToS3Bucket.md)
+ [Routing traffic to an Amazon Virtual Private Cloud interface endpoint by using your domain name](routing-to-vpc-interface-endpoint.md)
+ [Routing traffic to Amazon WorkMail](routing-to-workmail.md)
+ [Routing traffic to Amazon OpenSearch Service domain endpoint](routing-to-open-search-service.md)
+ [Routing traffic to Amazon VPC Lattice service domain endpoint](routing-to-vpc-lattice-service.md)
+ [Routing traffic to other AWS resources](routing-to-additional-aws-resources.md)
+ [Creating Amazon Route 53 and Route 53 VPC Resolver resources with AWS CloudFormation](creating-resources-with-cloudformation.md)

# Routing traffic to an Amazon API Gateway API by using your domain name
Amazon API Gateway API

You can use Amazon API Gateway to create, publish, maintain, monitor, and secure APIs. You can create APIs that access AWS services or other web services in addition to data stored in the AWS Cloud.

The method that you use to route domain traffic to an API Gateway API is the same regardless of whether you created a regional API Gateway endpoint or an edge-optimized API Gateway endpoint. If you create a private API Gateway endpoint, the process is slightly different.
+ **Regional API endpoint**: You create a Route 53 alias record that routes traffic to the regional API endpoint.
+ **Edge-optimized API endpoint**: You create a Route 53 alias record that routes traffic to the edge-optimized API. This causes traffic to be routed to the CloudFront distribution that's associated with the edge-optimized API.
+ **Private API endpoint**: You create a Route 53 alias record that routes traffic to your private API endpoint using an interface VPC endpoint for API Gateway in a private hosted zone.

An alias record is a Route 53 extension to DNS that's similar to a CNAME record. For a comparison of alias and CNAME records, see [Choosing between alias and non-alias records](resource-record-sets-choosing-alias-non-alias.md).

**Note**  
Route 53 doesn't charge for alias queries to API Gateway APIs or other AWS resources.

**Topics**
+ [

## Prerequisites
](#routing-to-api-gateway-prereqs)
+ [

## Configuring Route 53 to route traffic to an API Gateway endpoint
](#routing-to-api-gateway-config)

## Prerequisites


To get started, you need the following:
+ An API Gateway API that has a custom domain name, such as api.example.com that matches the name of the Route 53 record that you want to create.

  For more information, see the following topics:
  + [Setting up custom domain names for HTTP APIs](https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-custom-domain-names.html) in the *Amazon API Gateway Developer Guide*.
  + [Setting up custom domain names for REST APIs](https://docs.aws.amazon.com/apigateway/latest/developerguide/how-to-custom-domains.html) in the *Amazon API Gateway Developer Guide*.
  + [Setting up custom domain names for WebSocket APIs](https://docs.aws.amazon.com/apigateway/latest/developerguide/websocket-api-custom-domain-names.html) in the *Amazon API Gateway Developer Guide*.
  + [Custom domain names for private APIs in API Gateway](https://docs.aws.amazon.com//apigateway/latest/developerguide/apigateway-private-custom-domains.html) in the *Amazon API Gateway Developer Guide*.
+ A registered domain name. You can use Amazon Route 53 as your domain registrar or you can use a different registrar.
+ Route 53 as the DNS service for the domain. If you register your domain name by using Route 53, we automatically configure Route 53 as the DNS service for the domain. 

  For information about using Route 53 as the DNS service provider for your domain, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md).

## Configuring Route 53 to route traffic to an API Gateway endpoint


To configure Route 53 to route traffic to an API Gateway endpoint, perform the following procedure.

------
#### [ Custom domain names for public APIs ]

The following procedure describes how to route traffic to an API Gateway endpoint for a custom domain name for public APIs.<a name="routing-to-api-gateway-config-procedure"></a>

**To route traffic to an API Gateway endpoint**

1. If you created the Route 53 hosted zone and the endpoint using the same account, skip to step 2.

   If you created the hosted zone and the endpoint using different accounts, get the target domain name for the custom domain name that you want to use:

   1. Sign in to the AWS Management Console and open the API Gateway console at [https://console.aws.amazon.com/apigateway/](https://console.aws.amazon.com/apigateway/). 

   1. In the navigation pane, choose **Custom domain names**.

   1. Select the custom domain name that you want to use and get the value of ** API Gateway domain name**.

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the name of the hosted zone that has the domain name that you want to use to route traffic to your API.

1. Choose **Create record**.

1. Specify the following values:
**Important**  
We recommend that you turn on Alias. For domain names that don't use a Route 53 Alias record, you might encounter issues if you use a VPC with private DNS enabled to invoke a private API. Private DNS overrides the default DNS resolution behavior within the VPC, which might cause conflicts with external DNS records.  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).  
**Record name**  
Enter the domain name that you want to use to route traffic to your API.   
The API that you want to route traffic to must include a custom domain name, such as api.example.com that matches the name of the Route 53 record.  
**Alias**  
If you are using the **Quick create** record creation method, turn on **Alias**.  
**Value/Route traffic to**  
Choose **Alias to API Gateway API**, then choose the Region that the endpoint is from.   
How you specify the value for **Endpoint** depends on whether you created the hosted zone and the API using the same AWS account or different accounts:  
   + **Same account** – The list of target domain names includes only APIs that have a custom domain name that matches the value that you specified for **Record name**. Choose the applicable value.
   + **Different accounts** – Enter the value that you got in step 1 of this procedure.  
**Record type**  
Choose **A – IPv4 address**.  
**Evaluate target health**  
For control over DNS failover, configure custom health checks. For an example, see [Configure custom health checks for DNS failover](https://docs.aws.amazon.com/apigateway/latest/developerguide/dns-failover.html) in the *API Gateway user guide*.

1. Choose **Create records**.

   Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you'll be able to route traffic to your API by using the name of the alias record that you created in this procedure.

------
#### [ Custom domain names for private APIs ]

The following procedure describes how to route traffic to an API Gateway endpoint for a custom domain name for private APIs.<a name="routing-to-api-gateway-config-procedure"></a>

**To route traffic to an API Gateway endpoint**

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the name of the private hosted zone that has the domain name that you want to use to route traffic to your API.

1. Choose **Create record**.

1. Specify the following values:  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).  
**Record name**  
Enter the domain name that you want to use to route traffic to your API.   
The API that you want to route traffic to must include a custom domain name, such as api.example.com that matches the name of the Route 53 record.  
**Alias**  
Turn on **Alias**.  
**Value/Route traffic to**  
Choose **Alias to VPC Endpoint**. Choose the Region that the endpoint is from, and then select your VPC endpoint.  
**Record type**  
If you are using IPv6 for your VPC endpoint, create an AAAA record type. If you are using dualstack for your VPC endpoint, create both an AAAA and an A record type.  
**Evaluate target health**  
For control over DNS failover, configure custom health checks. For an example, see [Configure custom health checks for DNS failover](https://docs.aws.amazon.com/apigateway/latest/developerguide/dns-failover.html) in the *API Gateway user guide*.

1. Choose **Create records**.

   Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you'll be able to route traffic to your API by using the name of the alias record that you created in this procedure.

------

# Routing traffic to an Amazon CloudFront distribution by using your domain name
Amazon CloudFront distribution

This topic provides comprehensive procedures for routing DNS traffic to any Amazon CloudFront distribution. If you're setting up a static website with Amazon CloudFront and Amazon Simple Storage Service, see [Use an Amazon CloudFront distribution to serve a static website](getting-started-cloudfront-overview.md) for a complete tutorial.

You can use Amazon CloudFront, the AWS content delivery network (CDN), as one way to speed up delivery of your web content. CloudFront can deliver your entire website—including dynamic, static, streaming, and interactive content—by using a global network of edge locations. Users who request your content are automatically routed to the edge location that gives them the lowest latency. 

**Note**  
You can route traffic to a CloudFront distribution only for public hosted zones.

To use CloudFront to distribute your website content, create a distribution and specify settings for it. For example, specify the Amazon S3 bucket or HTTP server that you want CloudFront to get your content from, whether you want only selected users to have access to your content, and whether you want users to use HTTPS.

When you create a distribution, CloudFront assigns a domain name to the distribution, such as d111111abcdef8.cloudfront.net. You can use this domain name in the URLs for your content, for example:

`http://d111111abcdef8.cloudfront.net/logo.jpg`

Alternatively, you can use your own domain name in URLs, for example:

`http://example.com/logo.jpg`

Follow the steps in the Amazon CloudFront Developer Guide to use your own domain name in your files' URLs in a CloudFront distribution, instead of the domain name that CloudFront assigns to your distribution. For more information, about using your own domain name with a CloudFront distribution, see [Using custom URLs by adding alternate domain names (CNAMEs)](/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html).

When you use a Route 53 domain name with a CloudFront distribution, use Amazon Route 53 to create an [alias record](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html) that points to your CloudFront distribution. An alias record is a Route 53 extension to DNS. It's similar to a CNAME record, but you can create an alias record both for the root domain, such as example.com, and for subdomains, such as www.example.com. (You can create CNAME records only for subdomains.) When Route 53 receives a DNS query that matches the name and type of an alias record, Route 53 responds with the domain name that is associated with your distribution. 

**Note**  
Route 53 doesn't charge for alias queries to CloudFront distributions or other AWS resources.

## Prerequisites


To get started, you need the following:

1. A registered domain name. You can use Amazon Route 53 as your domain registrar or you can use a different registrar.

1. Route 53 as the DNS service for the domain. If you register your domain name by using Route 53, we automatically configure Route 53 as the DNS service for the domain. 

   For information about using Route 53 as the DNS service provider for your domain, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md).

1. A CloudFront distribution or a CloudFront distribution tenant. The distribution must include an alternate domain name that matches the domain name that you want to use for your URLs instead of the domain name that CloudFront assigned to your distribution. For a CloudFront distribution tenant, it must contain the domain name that you want to use for your URLs.

   For example, if you want the URLs for your content to contain the domain name **example.com**, the **Alternate Domain Name** field for the distribution must include **example.com**.

   For more information, see the following documentation in the *Amazon CloudFront Developer Guide*:
   + [Task list for creating a distribution](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/distribution-web-creating.html)
   + [Creating or updating a distribution using the CloudFront console](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/distribution-web-creating-console.html)
**Note**  
If you're creating a static website, see [Get started with a secure static website](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/getting-started-secure-static-website-cloudformation-template.html) in the *Amazon CloudFront Developer Guide* for complete setup instructions.

1. (Optional) Request a public certificate so that Amazon CloudFront distributions require HTTPS. For more information, see [DNS validation in the AWS Certificate Manager](https://docs.aws.amazon.com/acm/latest/userguide/dns-validation.html) in the *AWS Certificate Manager User Guide.*

## Configuring Amazon Route 53 to route traffic to a CloudFront distribution


To configure Amazon Route 53 to route traffic to a CloudFront distribution, follow these steps. For more information about using your own domain name with a CloudFront distribution, see [Using custom URLs by adding alternate domain names (CNAMEs)](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/CNAMEs.html) in the Amazon CloudFront Developer Guide.

**Note**  
Changes generally propagate to all Route 53 servers within 60 seconds. When the changes propagate, you'll be able to route traffic to your CloudFront distribution by using the name of the alias record that you create in this procedure. <a name="routing-to-cloudfront-distribution-procedure"></a>

**To route traffic to a CloudFront distribution**

1. Get the domain name that CloudFront assigned to your distribution and determine whether IPv6 is enabled:

   1. Sign in to the AWS Management Console and open the CloudFront console at [https://console.aws.amazon.com/cloudfront/v4/home](https://console.aws.amazon.com/cloudfront/v4/home).

   1. in the **ID** column, select the linked name of the distribution that you want to route traffic to (not the check box).

   1. On the **General** tab, get the value of the **Distribution domain name** field.

   1. On the **General** tab, in the **Settings** section, choose edit and scroll to check the **IPv6** field to see whether IPv6 is enabled for the distribution. If IPv6 is enabled, you'll need to create two alias records for the distribution, one to route IPv4 traffic to the distribution, and one to route IPv6 traffic. Choose **Cancel**.

      For more information, see [Enable IPv6](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/distribution-web-values-specify.html#DownloadDistValuesEnableIPv6) in the topic [Values that you specify when you create or update a distribution](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/distribution-web-values-specify.html) in the *Amazon CloudFront Developer Guide*.

1. For a CloudFront distribution tenant,

   1. Choose **SaaS** in the left nav, then **Distribution tenants**, and choose the distribution tenant with the domain name that you want to route traffic to

   1. in the **General details** section, copy the value of the **Endpoint**.

1. Sign in to the AWS Management Console and open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the linked name of the hosted zone for the domain that you want to use to route traffic to your CloudFront distribution.

1. Choose **Create record**.

1. Specify the following values:  
**Record name**  
Enter the domain name that you want to use to route traffic to your CloudFront distribution. The default value is the name of the hosted zone.  
For example, if the name of the hosted zone is example.com and you want to use **acme.example.com** to route traffic to your distribution, enter **acme**.  
**Record type**  
Choose **A – IPv4 address**.  
If IPv6 is enabled for the distribution and you're creating a second record, choose **AAAA – IPv6 address**.   
**Alias**  
Turn on **Alias**.  
You must create an Alias record for the CloudFront distribution to work.  
**Route traffic to**  
Choose **Alias to CloudFront distribution**. Choose the domain name that CloudFront assigned to the distribution when you created it. This is the value that you got in step 1.  
For a CloudFront distribution tenant, choose the endpoint from step 2.  
**Evaluate target health**  
Accept the default value of **No**.  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).

1. Choose **Create records**.

1. If IPv6 is enabled for the distribution, repeat steps 5 through 7. Specify the same settings except for the **Record type** field, as explained in step 6.

# Routing traffic to an Amazon EC2 instance
Amazon EC2 instance

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.

You can route traffic for your domain, such as example.com, to your server by using Amazon Route 53, if you're hosting a website or running a web application on an EC2 instance. 

## Prerequisites


To get started, you need the following:
+ An Amazon EC2 instance. For information about launching an EC2 instance, see the following documentation:
  + **Linux** – See [Getting started with Amazon EC2 Linux instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html) in the *Amazon EC2 User Guide*
  + **Microsoft Windows** – See [Getting started with Amazon EC2 Windows instances](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/EC2_GetStarted.html) in the *Amazon EC2 User Guide*
**Important**  
We recommend that you also create an [Elastic IP address](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/elastic-ip-addresses-eip.html) and associate it with your EC2 instance. An Elastic IP address ensures that the IP address of your Amazon EC2 instance will never change. For information related to pricing, see [Pricing for Elastic IP addresses](https://aws.amazon.com/ec2/pricing/on-demand/#Elastic_IP_Addresses).
+ A registered domain name. You can use Amazon Route 53 as your domain registrar or you can use a different registrar.
+ Route 53 as the DNS service for the domain. If you register your domain name by using Route 53, we automatically configure Route 53 as the DNS service for the domain. 

  For information about using Route 53 as the DNS service provider for your domain, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md).

## Configuring Amazon Route 53 to route traffic to an Amazon EC2 instance


To configure Amazon Route 53 to route traffic to an EC2 instance, perform the following procedure.<a name="routing-to-ec2-instance-procedure"></a>

**To route traffic to an Amazon EC2 instance**

1. Get the IP address for the Amazon EC2 instance:

   1. Sign in to the AWS Management Console and open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/).

   1. In the Regions list in the upper right corner of the console, choose the Region that you launched the instance in.

   1. In the navigation pane, choose **Instances**.

   1. In the table, choose the instance that you want to route traffic to.

   1. In the bottom pane, on the **Description** tab, get the value of **Elastic IPs**. 

      If you didn't associate an Elastic IP with the instance, get the value of **IPv4 Public IP**.

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the name of the hosted zone that matches the name of the domain that you want to route traffic for.

1. Choose **Create record**.

1. Specify the following values:  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).  
**Record name**  
Enter the domain name that you want to use to route traffic to your EC2 instance. The default value is the name of the hosted zone.  
For example, if the name of the hosted zone is example.com and you want to use acme.example.com to route traffic to your EC2 instance, enter **acme**.  
**Value/Route traffic to**  
Choose **IP address or another value depending on the record type**. Enter the IP address that you got in step 1.  
**Record type**  
Choose **A – IPv4 address**.  
**TTL (seconds)**  
Accept the default value of **300**.

1. Choose **Create records**.

   Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you'll be able to route traffic to your EC2 instance by using the name of the record that you created in this procedure. 

**Important**  
If you release the elastic IP, make sure you also delete the DNS record pointing to it. If you don't, you will have a dangling DNS record that can be taken over by an unauthorized user.

# Routing traffic to an AWS App Runner service
App Runner service

AWS App Runner is a fully managed service that makes it easy for developers to deploy containerized web applications and APIs at scale and with no prior infrastructure experience required. Start with your source code or a container image. App Runner builds and deploys the web application automatically, load balances traffic with encryption, scales to meet your traffic needs, and makes it easy for your services to communicate with other AWS services and applications that run in a private Amazon VPC. With App Runner, rather than thinking about servers or scaling, you have more time to focus on your applications. For more information, see [What is AWS App Runner](https://docs.aws.amazon.com/apprunner/latest/dg/what-is-apprunner.html) in the *AWS App Runner Developer Guide.*

**Important**  
Amazon Route 53 currently supports alias records for AWS App Runner services that are created after August 1, 2022.

To route domain traffic to an App Runner Service, use Amazon Route 53 to create an [alias record](resource-record-sets-choosing-alias-non-alias.md) that points to your App Runner service. An alias record is a Route 53 extension to DNS. It's similar to a CNAME record, except you can create an alias record both for the root domain, such as example.com, and for subdomains, such as www.example.com (http://www.example.com/). You can create only CNAME records for subdomains. 

**Note**  
Route 53 doesn't charge for alias queries to App Runner service or other AWS resources.

## Prerequisites


To get started, you need the following:
+ An App Runner service. For information about creating an App Runner service, see [Getting started with App Runner](https://docs.aws.amazon.com/apprunner/latest/dg/getting-started.html).
+ A registered domain name. You can use Amazon Route 53 as your domain registrar, or you can use a different registrar.
+ Route 53 as the DNS service for the domain. If you register your domain name by using Route 53, we automatically configure Route 53 as the DNS service for the domain. 

  For information about using Route 53 as the DNS service provider for your domain, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md).
+ Associated the custom domain to your App Runner service. For more information, see [Managing custom domain names for App Runner](https://docs.aws.amazon.com/apprunner/latest/dg/manage-custom-domains.html).
+ Configure the certificate validation record returned by App Runner to you Route 53 hosted zone to start the domain validation process. For more information, see [DNS validation in the AWS Certificate Manager](https://docs.aws.amazon.com/acm/latest/userguide/dns-validation.html) in the *AWS Certificate Manager User Guide.*

## Configuring Amazon Route 53 to route traffic to an App Runner service


To configure Amazon Route 53 to route traffic to an App Runner service, perform the following procedure.<a name="routing-to-app-runner-procedure"></a>

**To route traffic to an App Runner service**

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the name of the hosted zone that matches the name of the domain that you want to route traffic for.

1. Choose **Create record**.

1. Specify the following values:  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).  
**Record name**  
Enter the domain name that you want to use to route traffic to your App Runner service. The default value is the name of the hosted zone.  
For example, if the name of the hosted zone is example.com and you want to use acme.example.com to route traffic to your App Runner service, enter **acme**.  
**Value/Route traffic to**  
Choose **Alias to App Runner Service**, then choose the AWS Region. Choose the domain name of the environment that you want to route traffic to.  
**Record type**  
Accept the default value, **A – IPv4 address**.  
**Evaluate target health**  
Choose **No**. For information about evaluating target health, see [Evaluate target health](resource-record-sets-values-alias.md#rrsets-values-alias-evaluate-target-health).

1. Choose **Create records**.

   Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you'll be able to route traffic to your App Runner service by using the name of the alias record that you created in this procedure. 

# Routing traffic to an AWS Global Accelerator
Global Accelerator

AWS Global Accelerator is a service in which you create accelerators to improve the performance of your applications for local and global users. The service reacts instantly to changes in health or configuration to ensure that internet traffic from clients is always directed to healthy endpoints. Global Accelerator includes a fault tolerant architecture, and incorporates AWS Shield Standard, for automated in-line mitigation from DDoS attacks. For more information, see [What is Global Accelerator](https://docs.aws.amazon.com/global-accelerator/latest/dg/what-is-global-accelerator.html) in the AWS Global Accelerator Developer Guide.

By default, Global Accelerator provides you with static IP addresses that you associate with your accelerator. The static IP addresses are anycast from the AWS edge network. Accelerators include a deafult DNS name, but in most scenarios, you can configure DNS to use your custom domain name (such as www.example.com) with your accelerator, instead of using the assigned static IP addresses or the default DNS name. 

**Note**  
Route 53 doesn't charge for alias queries to Global Accelerator or other AWS resources.

## Prerequisites


To get started, you need the following:
+ An accelerator. You can create either a standard accelerator, or a custom routing accelerator. For more information, see [Create a standard accelerator](https://docs.aws.amazon.com/global-accelerator/latest/dg/about-accelerators.creating-editing.html) and [Create a custom routing accelerator](https://docs.aws.amazon.com/global-accelerator/latest/dg/about-custom-routing-accelerators.creating-editing.html).
+ A registered domain name. You can use Amazon Route 53 as your domain registrar, or you can use a different registrar.
+ Route 53 as the DNS service for the domain. If you register your domain name by using Route 53, we automatically configure Route 53 as the DNS service for the domain. 

  For information about using Route 53 as the DNS service provider for your domain, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md).

## Configuring Amazon Route 53 to route traffic to an accelerator


To configure Amazon Route 53 to route traffic to an accelerator, perform the following procedure.<a name="routing-to-global-accelerator-procedure"></a>

**To route traffic to an accelerator**

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the name of the hosted zone that matches the name of the domain that you want to route traffic for.

1. Choose **Create record**.

1. Specify the following values:  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).  
**Record name**  
Enter the domain name that you want to use to route traffic to your accelerator. The default value is the name of the hosted zone.  
For example, if the name of the hosted zone is example.com and you want to use acme.example.com to route traffic to your Global Accelerator, enter **acme**.  
**Value/Route traffic to**  
Choose **Alias to Global Accelerator**, then choose the AWS Region. Choose the DNS name for the accelerator.  
You can enter the DNS name of an accelerator that you created using the current AWS account or using a different AWS account.  
**Record type**  
Accept the default value, **A – IPv4 address**.  
**Evaluate target health**  
Accept the default value of **Yes**.

1. Choose **Create records**.

   Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you'll be able to route traffic to your accelerator by using the name of the alias record that you created in this procedure. 

# Routing traffic to an AWS Elastic Beanstalk environment
AWS Elastic Beanstalk environment

If you're using 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 a new or an existing Elastic Beanstalk environment.

To route DNS traffic to an Elastic Beanstalk environment, see the procedures in the following topics.

**Note**  
These procedures assume that you're already using Route 53 as the DNS service for your domain. If you're using another DNS service, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md) for information about using Route 53 as the DNS service provider for your domain. 

**Topics**
+ [

## Deploying an application into an Elastic Beanstalk environment
](#routing-to-beanstalk-environment-deploy)
+ [

## Getting the domain name for your Elastic Beanstalk environment
](#routing-to-beanstalk-environment-get-domain-name)
+ [

## Creating an Amazon Route 53 record that routes traffic to your Elastic Beanstalk environment
](#routing-to-beanstalk-environment-create-resource-record-set)

## Deploying an application into an Elastic Beanstalk environment


If you already have an Elastic Beanstalk environment that you want to route traffic to, skip to [Getting the domain name for your Elastic Beanstalk environment](#routing-to-beanstalk-environment-get-domain-name).

**To create an application and deploy it into an Elastic Beanstalk environment**
+ For information about creating an application and deploying it to an Elastic Beanstalk environment, see [Getting started using Elastic Beanstalk](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/GettingStarted.html) in the *AWS Elastic Beanstalk Developer Guide*.

## Getting the domain name for your Elastic Beanstalk environment


If you already know the domain name for your Elastic Beanstalk environment, skip to [Creating an Amazon Route 53 record that routes traffic to your Elastic Beanstalk environment](#routing-to-beanstalk-environment-create-resource-record-set).<a name="routing-to-beanstalk-environment-get-domain-name-procedure"></a>

**To get the domain name for your Elastic Beanstalk environment**

1. Sign in to the AWS Management Console and open the Elastic Beanstalk console at [https://console.aws.amazon.com/elasticbeanstalk/](https://console.aws.amazon.com/elasticbeanstalk/).

1. In the list of applications, find the application that you want to route traffic to, and get the value of **URL**. If you don't see the list of applications, choose **Applications** in the navigation pane.

   For more information about the URL, see [Elastic Beanstalk environment's domain name](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html) in the *Elastic Beanstalk Developer Guide*. 

## Creating an Amazon Route 53 record that routes traffic to your Elastic Beanstalk environment
Creating a Route 53 record

An Amazon Route 53 record contains the settings that control how traffic is routed to your Elastic Beanstalk environment. You create either a *CNAME record* or an *alias record*, depending on whether the domain name for the environment includes the Region, such as **us-east-2**, in which you deployed the environment. New environments include the Region in the domain name; environments that were created before early 2016 do not. For a comparison of CNAME and alias records, see [Choosing between alias and non-alias records](resource-record-sets-choosing-alias-non-alias.md).

**If the domain name does not include the Region**  
You must create a *CNAME record*. However, because of limitations imposed by DNS, you can create CNAME records only for subdomains, not for the root domain name. For example, if your domain name is example.com, you can create a record that routes traffic for acme.example.com to your Elastic Beanstalk environment, but you can't create a record that routes traffic for example.com to your Elastic Beanstalk environment.  
See the procedure [To create a CNAME record to route traffic to an Elastic Beanstalk environment](#routing-to-beanstalk-environment-create-cname-procedure).

**If the domain name includes the Region**  
You can create an alias record. An alias record is specific to Route 53 and has two significant advantages over CNAME records:  
+ You can create alias records for the root domain name or for subdomains. For example, if your domain name is example.com, you can create a record that routes requests for example.com or for acme.example.com to your Elastic Beanstalk environment.
+ Route 53 doesn't charge for requests that use an alias record to route traffic.
See the procedure [To create an Amazon Route 53 alias record to route traffic to an Elastic Beanstalk environment](#routing-to-beanstalk-environment-create-alias-procedure).<a name="routing-to-beanstalk-environment-create-cname-procedure"></a>

**To create a CNAME record to route traffic to an Elastic Beanstalk environment**

1. Sign in to the AWS Management Console and open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the name of the hosted zone that you want to use to route traffic to your Elastic Beanstalk environment.

1. Choose **Create record**.

1. Choose **Switch to quick create**

1. Specify the following values:  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).  
**Record name**  
Enter the domain name that you want to use to route traffic to your Elastic Beanstalk environment. The default value is the name of the hosted zone.  
For example, if the name of the hosted zone is example.com and you want to use acme.example.com to route traffic to your environment, enter **acme**.  
You can't create a CNAME record that has the same name as the hosted zone.  
**Alias**  
If you are using the **Quick create** record creation method, turn on **Alias**.  
**Value/Route traffic to**  
Choose **IP address or another value depending on the record type** and enter the value that you get when you perform the procedure in the topic [Getting the domain name for your Elastic Beanstalk environment](#routing-to-beanstalk-environment-get-domain-name). If you used different accounts to create your Route 53 hosted zone and your Elastic Beanstalk environment, enter the CNAME attributes for the Elastic Beanstalk environment.  
**Record type**  
Choose **CNAME**.  
**TTL (seconds)**  
Accept the default value of **300**.

1. Choose **Create records**.

   Changes generally propagate to all Route 53 servers within 60 seconds. <a name="routing-to-beanstalk-environment-create-alias-procedure"></a>

**To create an Amazon Route 53 alias record to route traffic to an Elastic Beanstalk environment**

1. Sign in to the AWS Management Console and open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the name of the hosted zone that you want to use to route traffic to your Elastic Beanstalk environment.

1. Choose **Create record**.

1. Specify the following values:  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).  
**Record name**  
Enter the domain name that you want to use to route traffic to your Elastic Beanstalk environment. The default value is the name of the hosted zone.  
For example, if the name of the hosted zone is example.com and you want to use acme.example.com to route traffic to your environment, enter **acme**.  
**Value/Route traffic to**  
Choose **Alias to Elastic Beanstalk environment**, then choose the Region that the endpoint is from. Choose the domain name of the environment that you want to route traffic to. This is the value that you get when you perform the procedure in the topic [Getting the domain name for your Elastic Beanstalk environment](#routing-to-beanstalk-environment-get-domain-name).  
If you used different accounts to create your Route 53 hosted zone and your Elastic Beanstalk environment, enter the CNAME attribute for the Elastic Beanstalk environment.   
**Record type**  
Accept the default, **A – IPv4 address**.  
**Evaluate target health**  
Accept the default value of **Yes**.

1. Choose **Create records**.

   Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you'll be able to route traffic to your Elastic Beanstalk environment by using the name of the alias record that you create in this procedure. 

# Routing traffic to an ELB load balancer
ELB load balancer

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. 

To route domain traffic to an ELB load balancer, use Amazon Route 53 to create an [alias record](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html) that points to your load balancer. An alias record is a Route 53 extension to DNS. It's similar to a CNAME record, but you can create an alias record both for the root domain, such as example.com, and for subdomains, such as www.example.com. (You can create CNAME records only for subdomains.) 

**Note**  
Route 53 doesn't charge for alias queries to ELB load balancers or other AWS resources.

## Prerequisites


To get started, you need the following:
+ An ELB load balancer. You can use an ELB Classic, Application, or Network Load Balancer. For information about creating a load balancer, see [Getting started with Elastic Load Balancing](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/load-balancer-getting-started.html) in the *Elastic Load Balancing User Guide*.

  Give the load balancer a name that will help you remember what it's for later. The name that you specify when you create a load balancer is the name that you'll choose when you create an alias record in the Route 53 console.
+ A registered domain name. You can use Route 53 as your domain registrar, or you can use a different registrar.
+ Route 53 as the DNS service for the domain. If you register your domain name by using Route 53, we automatically configure Route 53 as the DNS service for the domain. 

  For information about using Route 53 as the DNS service provider for your domain, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md).

## Configuring Amazon Route 53 to route traffic to an ELB load balancer


To configure Amazon Route 53 to route traffic to an ELB load balancer, perform the following procedure.<a name="routing-to-elb-load-balancer-procedure"></a>

**To route traffic to an ELB load balancer**

1. If you created the Route 53 hosted zone and ELB load balancer using the same account, skip to step 2.

   If you created the hosted zone and the ELB load balancer using different accounts, perform the procedure [Getting the DNS name for an Elastic Load Balancing load balancer](resource-record-sets-creating.md#resource-record-sets-elb-dns-name-procedure) to get the DNS name for the load balancer. 

1. Sign in to the AWS Management Console and open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the name of the hosted zone that has the domain name that you want to use to route traffic to your load balancer.

1. Choose **Create record**.

1. Specify the following values:  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).  
**Record name**  
Enter the domain or subdomain name that you want to use to route traffic to your ELB load balancer. The default value is the name of the hosted zone.  
For example, if the name of the hosted zone is example.com and you want to use acme.example.com to route traffic to your load balancer, enter **acme**.  
**Alias**  
If you are using the **Quick create** record creation method, turn on **Alias**.  
**Value/Route traffic to**  
Choose **Alias to Application and Classic Load Balancer **or **Alias to Network Load Balancer**, then choose the Region that the endpoint is from.   
If you created the hosted zone and the ELB load balancer using the same AWS account, choose the DNS name that you assigned to the load balancer when you created it.  
If you created the hosted zone and the ELB load balancer using different accounts, enter the value that you got in step 1 of this procedure.  
The console prepends **dualstack.** to the DNS name of the application and Classic Load Balancer from the same AWS account only. When a client, such as a web browser, requests the IP address for your domain name (example.com) or subdomain name (www.example.com), the client can request an IPv4 address (an A record), an IPv6 address (an AAAA record), or both IPv4 and IPv6 addresses (in separate requests with IPv4 first). The **dualstack.** designation allows Route 53 to respond with the appropriate IP address for your load balancer based on which IP address format the client requested. You will need to prepend **dualstack.** for Application and Classic Load Balancer from the different account.  
**Record type**  
Choose **A – IPv4 address**.  
**Evaluate target health**  
If you want Route 53 to route traffic based on the health of your resources, choose **Yes**. For more information about checking the health of your resources, see [Creating Amazon Route 53 health checks](dns-failover.md).

1. Choose **Create records**.

   Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you'll be able to route traffic to your load balancer by using the name of the alias record that you created in this procedure. 

# Routing traffic to a website that is hosted in an Amazon S3 bucket
Amazon S3 bucket

This topic provides comprehensive procedures for routing DNS traffic to any Amazon Simple Storage Service bucket configured for static website hosting. If you're setting up a static website with Amazon Simple Storage Service, see [Use your domain for a static website in an Amazon S3 bucket](getting-started-s3.md) for a complete tutorial.

Amazon Simple Storage Service (Amazon S3) provides secure, durable, highly scalable [cloud storage](https://aws.amazon.com/what-is-cloud-storage/). You can configure an S3 bucket to host a static website that can include webpages and client-side scripts. (S3 doesn't support server-side scripting.)

To route domain traffic to an S3 bucket, use Amazon Route 53 to create an [alias record](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-choosing-alias-non-alias.html) that points to your bucket. An alias record is a Route 53 extension to DNS. It's similar to a CNAME record, except you can create an alias record both for the root domain, such as example.com, and for subdomains, such as www.example.com. You can create CNAME records only for subdomains. 

**Note**  
Route 53 doesn't charge for alias queries to S3 buckets or other AWS resources.

## Prerequisites


To get started, you need the following:
+ An S3 bucket that's configured to host a static website.

   For more information, see [Tutorial: Configuring a static website using a custom domain registered with Route 53](https://docs.aws.amazon.com/AmazonS3/latest/userguide/website-hosting-custom-domain-walkthrough.html) in the *Amazon Simple Storage Service User Guide*.
**Important**  
The bucket must have the same name as your domain or subdomain. For example, if you want to use the subdomain acme.example.com, the name of the bucket must be acme.example.com.

  You can route traffic for a domain and its subdomains, such as example.com and www.example.com, to a single bucket. Create a bucket for the domain and each subdomain, and configure all but one of the buckets to redirect traffic to the remaining bucket.
**Note**  
An S3 bucket that's configured as a website endpoint doesn't support SSL/TLS, so you need to route traffic to the CloudFront distribution and use the S3 bucket as the origin for the distribution.  
For instructions on how to create a CloudFront distribution, see [Routing traffic to an Amazon CloudFront distribution by using your domain name](routing-to-cloudfront-distribution.md).
+ A registered domain name. You can use Route 53 as your domain registrar, or you can use a different registrar.
+ Route 53 as the DNS service for the domain. If you register your domain name by using Route 53, we automatically configure Route 53 as the DNS service for the domain. 

  For information about using Route 53 as the DNS service provider for your domain, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md).

## Configuring Amazon Route 53 to route traffic to an S3 Bucket


To configure Amazon Route 53 to route traffic to an S3 bucket that is configured to host a static website, perform the following procedure.<a name="routing-to-s3-bucket-procedure"></a>

**To route traffic to an S3 bucket**

1. Sign in to the AWS Management Console and open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the name of the hosted zone that has the domain name that you want to use to route traffic to your S3 bucket.

1. Choose **Create record**.

1. Specify the following values:  
**Record name**  
Enter the domain name that you want to use to route traffic to your S3 bucket. The default value is the name of the hosted zone.  
For example, if the name of the hosted zone is example.com and you want to use acme.example.com to route traffic to your bucket, enter **acme**.  
**Record type**  
Choose **A – IPv4 address**.  
**Alias**  
Turn on **Alias**.  
**Route traffic to**  
Choose **Alias to S3 website endpoint**, then choose the Region that the endpoint is from.   
Choose the bucket that has the same name that you specified for **Record name**.  
The list includes a bucket only if the bucket meets the following requirements:  
   + The name of the bucket is the same as the name of the record that you're creating.
   + The bucket is configured as a website endpoint.
   + The bucket was created by the current AWS account.

     If you created the bucket using a different AWS account, enter the name of the Region that you created your S3 bucket in. For the correct format for the Region name, see the **Website endpoint** column in the table [Amazon S3 website endpoints](https://docs.aws.amazon.com/general/latest/gr/s3.html#s3_website_region_endpoints) in the *Amazon Web Services General Reference*.  
**Evaluate target health**  
Choose **No**. For information about evaluating target health, see [Evaluate target health](resource-record-sets-values-alias.md#rrsets-values-alias-evaluate-target-health).  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).

1. Choose **Create records**.

   Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you'll be able to route traffic to your S3 bucket by using the name of the alias record that you created in this procedure. 

# Routing traffic to an Amazon Virtual Private Cloud interface endpoint by using your domain name
Amazon Virtual Private Cloud interface endpoint

You can use AWS PrivateLink to access selected services with an Amazon Virtual Private Cloud (Amazon VPC) interface endpoint. These services include some AWS services, services that are hosted by other AWS customers and partners in their own VPCs, and supported AWS Marketplace partner services.

To route domain traffic to an interface endpoint, use Amazon Route 53 to create an alias record. An alias record is a Route 53 extension to DNS. It's similar to a CNAME record, but you can create an alias record both for the root domain, such as example.com, and for subdomains, such as www.example.com. You can create CNAME records only for subdomains.

**Note**  
Route 53 doesn't charge for alias queries to interface endpoints or other AWS resources.

**Topics**
+ [

## Prerequisites
](#routing-to-vpc-interface-endpoint-prereqs)
+ [

## Configuring Amazon Route 53 to route traffic to an Amazon VPC interface endpoint
](#routing-to-vpc-interface-endpoint-config)

## Prerequisites


To get started, you need the following:
+ An Amazon VPC interface endpoint. For more information, see [Interface VPC endpoints (AWS PrivateLink)](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html) in the *Amazon VPC User Guide*.
+ A registered domain name. You can use Amazon Route 53 as your domain registrar, or you can use a different registrar.
+ Route 53 as the DNS service for the domain. If you register your domain name by using Route 53, we automatically configure Route 53 as the DNS service for the domain. 

  For information about using Route 53 as the DNS service provider for your domain, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md).

## Configuring Amazon Route 53 to route traffic to an Amazon VPC interface endpoint
Amazon VPC interface endpoint

To configure Amazon Route 53 to route traffic to an Amazon VPC interface endpoint, perform the following procedure.<a name="routing-to-vpc-interface-endpoint-config-procedure"></a>

**To route traffic to an Amazon VPC interface endpoint**

1. If you created the Route 53 hosted zone and the Amazon VPC interface endpoint using the same account, skip to step 2.

   If you created the hosted zone and the interface endpoint using different accounts, get the service name for the interface endpoint:

   1. Sign in to the AWS Management Console and open the Amazon VPC console at [https://console.aws.amazon.com/vpc/](https://console.aws.amazon.com/vpc/).

   1. In the navigation pane, choose **Endpoints**.

   1. In the right pane, choose the endpoint that you want to route internet traffic to.

   1. In the bottom pane, get the value of DNS name, for example, **vpce-0fd00dd593example-dexample.cloudtrail.us-west-2.vpce.amazonaws.com**.

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the name of the hosted zone that has the domain name that you want to use to route traffic to your interface endpoint.

1. Choose **Create record**.

1. Specify the following values:  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).  
**Record name**  
Enter the domain name that you want to use to route traffic to your Amazon VPC interface endpoint.   
**Alias**  
If you are using the **Quick create** record creation method, turn on **Alias**.  
**Value/Route traffic to**  
Choose **Alias to VPC endpoint**, then choose the Region that the endpoint is from.   
How you specify the value for **Endpoints** depends on whether you created the hosted zone and the interface endpoint using the same AWS account or different accounts:  
   + **Same account** – Choose the list, and find the category **Amazon VPC endpoints**. Then choose the DNS name of the interface endpoint that you want to route internet traffic to.
   + **Different accounts** – Enter the value that you got in step 1 of this procedure.  
**Record type**  
Choose **A – IPv4 address**.  
**Evaluate target health**  
Choose **No**. For information about evaluating target health, see [Evaluate target health](resource-record-sets-values-alias.md#rrsets-values-alias-evaluate-target-health).

1. Choose **Create records**.

   Changes generally propagate to all Route 53 servers within 60 seconds. When propagation is done, you'll be able to route traffic to your interface endpoint by using the name of the alias record that you created in this procedure.

# Routing traffic to Amazon WorkMail
Amazon WorkMail

You can use Route 53 to route traffic to your Amazon WorkMail email domain. The name of your Route 53 hosted zone (such as example.com) must match the name of an Amazon WorkMail domain.

**Note**  
You can route traffic to an Amazon WorkMail domain only for public hosted zones.

To route traffic to Amazon WorkMail, perform the following four procedures.<a name="routing-to-workmail-dns-procedure"></a>

**To configure Amazon Route 53 as your DNS service and add an Amazon WorkMail organization and email domain**

1. If you haven't registered the domain name that you want to use in your email addresses (such as john@example.com), register the domain now so you know that the domain is available. For more information, see [Registering a new domain](domain-register.md). 

   If Amazon Route 53 is not the DNS service for the email domain that you added to Amazon WorkMail, migrate DNS service for the domain to Route 53. For more information, see [Making Amazon Route 53 the DNS service for an existing domainMaking Route 53 the DNS service for an existing domain](MigratingDNS.md).

1. Add an Amazon WorkMail organization and email domain. For more information, see [Getting started for new users](https://docs.aws.amazon.com/workmail/latest/adminguide/getting_started_new_user.html) in the *Amazon WorkMail Administrator Guide*.<a name="routing-to-workmail-txt-procedure"></a>

**To create a Route 53 TXT record for Amazon WorkMail**

1. In the navigation pane of the Amazon WorkMail console, choose **Domains**.

1. Choose the name of the email domain, such as example.com that you want to use to route traffic to Amazon WorkMail.

1. Open another browser tab, and open the [Route 53 console](https://console.aws.amazon.com/route53/home).

1. In the Route 53 console, do the following:

   1. In the navigation pane, choose **Hosted zones**.

   1. Choose the name of the hosted zone that you want to use for your Amazon WorkMail email domain.

1. In the Amazon WorkMail console, in the section **Step 1: Verify domain ownership**, go to the **Hostname** column, and copy the part of the value that precedes your email domain name. 

   For example, if your Amazon WorkMail email domain is **example.com** and the value of **Hostname** is **\$1amazonses.example.com**, copy **\$1amazonses**.

1. In the Route 53 console, do the following:

   1. Choose **Create record**, and choose **Simple routing**.

   1. For **Record name**, paste the value that you copied in step 5.

   1. For **Record type**, choose **TXT – Text**.

1. In the Amazon WorkMail console, for the TXT record, copy the value of the **Value** column, including the quotation marks.

1. In the Route 53 console, do the following:

   1. For **Value/Route traffic to**, choose **IP address or another value depending on the record type**, and paste the value that you copied in step 7.

      Don't change any other settings.

   1. Choose **Create**.<a name="routing-to-workmail-mx-procedure"></a>

**To create a Route 53 MX record for Amazon WorkMail**

1. In the Amazon WorkMail console, in the section **Step 2: Finalize domain setup**, go to the row that has a **Record type** of **MX**, and copy the value of the **Value** column.

1. In the Route 53 console, do the following:

   1. Choose **Create record**.

   1. For **Value/Route traffic to**, choose **IP address or another value depending on the record type**, and paste the value that you copied in step 1.

   1. For **Record type**, choose **MX – Mail Exchange**.

      Don't change any other settings.

   1. Choose **Create records**.<a name="routing-to-workmail-cname-procedure"></a>

**To create four Route 53 CNAME records for Amazon WorkMail**

1. In the Amazon WorkMail console, in the section **Step 2: Finalize domain setup**, go to the first row that has a **Record type** of **CNAME**. In the **Hostname** column, copy the part of the value that precedes your email domain name.

   For example, if your Amazon WorkMail email domain is **example.com** and the value of **Hostname** is **autodiscover.example.com**, copy **autodiscover**.

1. In the Route 53 console, do the following:

   1. Choose **Create record**.

   1. For **Record name**, paste the value that you copied in step 1.

   1. For **Record type**, choose **CNAME – Canonical Name**.

1. In the Amazon WorkMail console, in the first row that has a **Record type** of **CNAME**, copy the value of the **Value** column.

1. In the Route 53 console, do the following:

   1. For **Value/Route traffic to**, choose **IP address or another value depending on the record type**, and paste the value that you copied in step 3.

      Don't change any other settings.

   1. Choose **Create records**.

1. Repeat steps 1 through 4 for the remaining CNAME records that are listed in the Amazon WorkMail console.

# Routing traffic to Amazon OpenSearch Service domain endpoint
Amazon OpenSearch Service

Amazon OpenSearch Service is is a managed service that makes it easy to deploy, operate, and scale OpenSearch clusters in the AWS Cloud. An OpenSearch Service Service domain is synonymous with an OpenSearch Service cluster. Domains are clusters with the settings, instance types, instance counts, and storage resources that you specify. For more information, see [What is Amazon OpenSearch Service](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/what-is.html) in the *Amazon OpenSearch Service Developer Guide.*

## Prerequisites


To get started, you need the following:

An OpenSearch Service domain that has a custom domain name, such as example.com that matches the name of the Route 53 record that you want to create.

For more information, see the following topics:
+ [Getting started](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/gsg.html) in the *Amazon OpenSearch Service Developer Guide*.
+ [Creating a custom endpoint](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/customendpoint.html) in the *Amazon OpenSearch Service Developer Guide*.

## Configuring Amazon Route 53 to route traffic to an Amazon OpenSearch Service domain endpoint


To use Route 53 to route traffic to OpenSearch Service you first get the domain endpoint provided by OpenSearch Service. This dual stack endpoint is provided only if custom endpoint is enabled on an OpenSearch Service domain with dual-stack network mode. For more information, see [Create a custom endpoint](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/customendpoint.html) in the *Amazon OpenSearch Service Developer Guide*.<a name="routing-to-open-search-procedure"></a>

**To route traffic to an OpenSearch Service endpoint**

1. Go to [https://aws.amazon.com](https://aws.amazon.com) and choose **Sign In to the Console**.

1. Under **Analytics**, choose **Amazon OpenSearch Service**.

1. Under **Managed clusters** choose **Domains**.

1. On the **Domains** page choose the name of the domain that you want to route traffic to.

1. On the domain detail page copy the value for the **Domain endpoint v2 (dual stack)**.

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the linked name of the hosted zone for the domain that you want to use to route traffic to your OpenSearch Service endpoint. The domain name must match the custom endpoint defined in OpenSearch Service.

1. Choose **Create record**.

   You can use the wizard to create the records or choose **Switch to quick create**.

1. Specify the following values:  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).  
**Record name**  
Enter the domain name that you want to use to route traffic to your OpenSearch Service domain endpoint. The default value is the name of the hosted zone.  
For example, if the name of the hosted zone is example.com and you want to use **acme.example.com** to route traffic to your distribution, enter **acme**.  
**Alias**  
If you are using the **Quick create** record creation method, turn on **Alias**.  
**Value/Route traffic to**  
Choose **Alias to OpenSearch Service domain endpoint**. Choose the Region that the OpenSearch Service domain was created in, and choose the value that you got in step 5.  
**Record type**  
Choose **A – IPv4 address**, **AAAA – IPv6 address** or both for dual-stack.  
**Evaluate target health**  
Choose **No**. For information about evaluating target health, see [Evaluate target health](resource-record-sets-values-alias.md#rrsets-values-alias-evaluate-target-health).

1. Choose **Create records**.

# Routing traffic to Amazon VPC Lattice service domain endpoint
VPC Lattice

Amazon VPC Lattice is a fully managed application networking service that you use to connect, secure, and monitor the services and resources for your application. You can use VPC Lattice with a single virtual private cloud (VPC) or across multiple VPCs from one or more accounts. For more information, see [What is Amazon VPC Lattice](https://docs.aws.amazon.com/vpc-lattice/latest/ug/what-is-vpc-lattice.html) in the *Amazon VPC Lattice User Guide*.

## Prerequisites


To get started, you need the following:

A VPC Lattice service domain that has a custom domain name, such as example.com that matches the name of the Route 53 record that you want to create.

For more information, see [Associate a custom domain name with your service](https://docs.aws.amazon.com/vpc-lattice/latest/ug/service-custom-domain-name.html) in the *Amazon VPC Lattice User Guide*.

## Configuring Amazon Route 53 to route traffic to a VPC Lattice service domain endpoint


To use Route 53 to route traffic to Amazon VPC Lattice service domain, you first get the domain service endpoint provided by VPC Lattice. For more information, see [Associate a custom domain name with your service](https://docs.aws.amazon.com/vpc-lattice/latest/ug/service-custom-domain-name.html) in the *Amazon VPC Lattice User Guide*.<a name="routing-to-vpc-lattice-procedure"></a>

**To route traffic to VPC Lattice service domain endpoint**

1. Go to [https://aws.amazon.com](https://aws.amazon.com) and choose **Sign In to the Console**.

1. Under **Networking & Content Delivery**, choose **VPC**.

1. Under **PrivateLink and Lattice** choose **Lattice Services**.

1. Create a VPC Lattice service or select an existing VPC Lattice service.
**Note**  
 When creating a VPC Lattice service, you must specify a custom domain configuration and supply a custom domain name. If you choose an existing service, it must also have a custom domain.

1. Under **Domain configuration**, copy the value for the custom domain name.

1. Open the Route 53 console at [https://console.aws.amazon.com/route53/](https://console.aws.amazon.com/route53/).

1. In the navigation pane, choose **Hosted zones**.

1. Choose the linked name of the hosted zone for the domain that you want to use to route traffic to your VPC Lattice service domain endpoint. The domain name must match the custom domain endpoint defined in VPC Lattice.

1. Choose **Create record**.

   You can use the wizard to create the records or choose **Switch to quick create**.

1. Specify the following values:  
**Routing policy**  
Choose the applicable routing policy. For more information, see [Choosing a routing policy](routing-policy.md).  
**Record name**  
Enter the domain name that you want to use to route traffic to your VPC Lattice service domain endpoint. The default value is the name of the hosted zone.  
For example, if the name of the hosted zone is example.com and you want to use **acme.example.com** to route traffic to your distribution, enter **acme**.  
**Alias**  
If you are using the **Quick create** record creation method, turn on **Alias**.  
**Value/Route traffic to**  
Choose **Alias to VPC Lattice service**. Choose the Region that the VPC Lattice service domain was created in, and choose the value that you got in step 5.  
**Record type**  
Choose **A – IPv4 address**, **AAAA – IPv6 address**, or both for dual-stack.  
**Evaluate target health**  
Choose **No**. For information about evaluating target health, see [Evaluate target health](resource-record-sets-values-alias.md#rrsets-values-alias-evaluate-target-health).

1. Choose **Create records**.

# Routing traffic to other AWS resources
Other AWS resources

The following is the list of topics in other guides on how to use Route 53 to route traffic to those services.
+ [Using AWS Cloud Map](https://docs.aws.amazon.com/cloud-map/latest/dg/using-cloud-map.html) in the *AWS Cloud Map User Guide*.
+ [Manage custom domains](https://docs.aws.amazon.com/apprunner/latest/dg/manage-custom-domains.html) in the * AWS App Runner Developer Guide*.
+ [Using Route 53 as a DNS provider](https://docs.aws.amazon.com/transfer/latest/userguide/requirements-dns.html#requirements-use-r53) in the *AWS Transfer Family User Guide*.
+ [Using Route 53 to point a domain to an Amazon Lightsail instance](https://lightsail.aws.amazon.com/ls/docs/en_us/articles/amazon-lightsail-using-route-53-to-point-a-domain-to-an-instance).