DNS is the internet’s phone book: it helps a browser find the server associated with a human-readable domain name. A registrar’s DNS dashboard controls how that domain behaves. section 12.4.1
Use DNS to connect a purchased domain to a deployed application:
- Register a domain through a provider such as Cloudflare or Route 53, then open its DNS management dashboard. section 12.4.1
- Add a CNAME record with the host name www and the deployed application’s Elastic Beanstalk address as its target. section 12.4.1
- Disable proxying or forwarding initially when the provider offers that option, avoiding an extra complication during setup. section 12.4.1
Pointing a custom domain to an app
For a deployed application at fact-frenzy.us-east-2.elasticbeanstalk.com, configure the www host to use a CNAME targeting that address. Visitors can then reach the application through www.factfrenzyapp.com. section 12.4.1
Elastic Beanstalk can also provide a public URL directly. The DNS prefix selected during environment creation becomes the application’s subdomain, making it useful for testing and demos before attaching a custom domain. section 12.3.6
www.factfrenzyapp.com -> fact-frenzy.us-east-2.elasticbeanstalk.com
Follow the concrete mapping from a custom www address to its Elastic Beanstalk endpoint. section 12.4.1






