Why can't I select my preferred alias target when creating a Route 53 alias resource record set?

2 minute read
1

I'm creating an Amazon Route 53 alias resource record set in the Route 53 console, but I can't select my preferred resource from the Alias Target list.

Short description

If no resources are available when creating an alias record using the Route 53 console, then the Alias Target list shows the message No Targets Available. Verify the following:

  • Route 53 supports your resource as an alias target.
  • The resource is on the same AWS account as your Route 53 hosted zone.
  • If you're routing to an Amazon CloudFront distribution, the resource record name matches a CNAME in the CloudFront distribution.
  • If you're routing to an Amazon Simple Storage Service (Amazon S3) bucket, the resource record name matches the Amazon S3 bucket name.

Resolution

Verify that Route 53 supports your resource

To verify that Route 53 supports your resource and that you've configured your resource correctly, see Value/route traffic to.

Verify that you're routing to resources on the same account

To route to resources on a different AWS account, enter a value that identifies the resource.

For example, to use an Amazon CloudFront distribution as an alias target, enter the CloudFront domain name.

Check CloudFront distribution names

Before routing to CloudFront distributions, be sure that the name of the resource record that you create matches a CNAME in the CloudFront distribution.

For example, if the record name is example.com, then your CloudFront distribution must use example.com as one of its alternate domain names.

Check S3 website endpoint names

Make sure that the name of the resource record for your Amazon S3 website endpoint matches the name of your Amazon S3 bucket. Also, configure your bucket for website hosting.

For example, if your bucket's name is AWSDOC-EXAMPLE-BUCKET, the record name must also be AWSDOC-EXAMPLE-BUCKET.


Related information

Values specific for simple alias records

AWS OFFICIAL
AWS OFFICIALUpdated a year ago