Your Elastic Beanstalk environment's Domain name - Amazon Elastic Beanstalk
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Your Elastic Beanstalk environment's Domain name

By default, your environment is available to users at a subdomain of When you create an environment, you can choose a hostname for your application. The subdomain and domain are autopopulated to

To route users to your environment, Elastic Beanstalk registers a CNAME record that points to your environment's load balancer. You can see URL of your environment's application with the current value of the CNAME in the environment overview page of the Elastic Beanstalk console.

Environment URL with CNAME showing on the environment overview page in the Elastic Beanstalk console

Choose the URL on the overview page, or choose Go to environment on the navigation pane, to navigate to your application's web page.

You can change the CNAME on your environment by swapping it with the CNAME of another environment. For instructions, see Blue/Green deployments with Elastic Beanstalk.

If you own a domain name, you can use Amazon Route 53 to resolve it to your environment. You can purchase a domain name with Amazon Route 53, or use one that you purchase from another provider.

To purchase a domain name with Route 53, see Registering a New Domain in the Amazon Route 53 Developer Guide.

To learn more about using a custom domain, see Routing Traffic to an Amazon Elastic Beanstalk Environment in the Amazon Route 53 Developer Guide.


If you terminate an environment, you must also delete any CNAME mappings that you created, as other customers can reuse an available hostname. Be sure to delete DNS records that point to your terminated environment to prevent a dangling DNS entry. A dangling DNS entry can expose internet traffic destined for your domain to security vulnerabilities. It can also present other risks.

For more information, see Protection from dangling delegation records in Route 53 in the Amazon Route 53 Developer Guide. You can also learn more about dangling DNS entries in Enhanced Domain Protections for Amazon CloudFront Requests in the Amazon Security Blog.