Menu
AWS Elastic Beanstalk suggests to use url in the following format: http://{appname}.elasticbeanstalk.com/
But I need to change it to my own url, something like https://tarta.ai
How to do it?
501
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. Choose the URL on the overview page, or choose Go to environment on the navigation pane, to navigate to your application's web page.
In your AWS console, go to Elastic Beanstalk. Click “Create New Application” at the top left corner of the console. Fill in the form and click “Create”. You will get redirected to the new application page.
To deploy configuration files to your environment, add the configuration files to a directory named .ebextensions at the root of your application bundle. Then, deploy the source code that includes these configuration files. 1. Allow incoming traffic on port 443 to the EC2 instance that your Elastic Beanstalk application is running on.
To customize your environment, consider the following: Use the option_settings key to modify the environment configuration. You can choose from general options for all environments and platform-specific options. Note: Recommended values are applied when you create or update an environment on the Elastic Beanstalk API by a client.
A Launch Now URL gives Elastic Beanstalk the minimum information required to create an application: the application name, solution stack, instance type, and environment type. Elastic Beanstalk uses default values for other configuration details that are not explicitly specified in your custom Launch Now URL.
Your Elastic Beanstalk Environment's Domain Name. By default, your environment is available to users at a subdomain of elasticbeanstalk.com. When you create an environment, you can choose a hostname for your application. The subdomain and domain are autopopulated to region.elasticbeanstalk.com.
Note: I use Amazon Route53 for my domain.
I know this is old question but since I just done this process for one of my apps, I decided to share it here which may help others too. Here's the steps I've gone through
References
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html
http://aws.typepad.com/aws/2011/05/moving-ahead-with-amazon-route-53.html
169
Use Amazon Route53. ELBs, including those generated with ElasticBeanstalk, are assigned CNAMEs. You can't just point your top-level domain at a CNAME, as it violates the RFC. You could point a CNAME record like http://www.appname.com at it, but that still won't respond at http://appname.com. It's an irritating problem; for example, consider this 7-page thread on the AWS forum.
The easiest solution is Route53. It uses special apex records to map TLDs to ELBs, thus avoiding the problem entirely. You can also use an EIP'd public instance to forward traffic to the ELB, although this raises scalability concerns.
24
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
