Launch an Elastic Beanstalk Environment
You use the Elastic Beanstalk console to launch an Elastic Beanstalk environment. You'll choose the Node.js platform configuration and accept the default settings and sample code. After you configure the environment's permissions, you deploy the sample application that you downloaded from GitHub.
To launch an environment (console)
Open the Elastic Beanstalk console using this preconfigured link:console.aws.amazon.com/elasticbeanstalk/home#/newApplication?applicationName=tutorials&environmentType=LoadBalanced
For Platform, choose the platform that matches the language used by your application.
For Application code, choose Sample application.
Choose Review and launch.
Review all options. When you're satisfied with them, choose Create app.
Elastic Beanstalk takes about five minutes to create the environment with the following resources:
EC2 instance– An Amazon Elastic Compute Cloud (Amazon EC2) virtual machine configured to run web apps on the platform that you choose.
Each platform runs a different set of software, configuration files, and scripts to support a specific language version, framework, web container, or combination thereof. Most platforms use either Apache or nginx as a reverse proxy that sits in front of your web app, forwards requests to it, serves static assets, and generates access and error logs.
Instance security group– An Amazon EC2 security group configured to allow ingress on port 80. This resource lets HTTP traffic from the load balancer reach the EC2 instance running your web app. By default, traffic is not allowed on other ports.
Load balancer– An Elastic Load Balancing load balancer configured to distribute requests to the instances running your application. A load balancer also eliminates the need to expose your instances directly to the Internet.
Load balancer security group– An Amazon EC2 security group configured to allow ingress on port 80. This resource lets HTTP traffic from the Internet reach the load balancer. By default, traffic is not allowed on other ports.
Auto Scaling group– An Auto Scaling group configured to replace an instance if it is terminated or becomes unavailable.
Amazon S3 bucket– A storage location for your source code, logs, and other artifacts that are created when you use Elastic Beanstalk.
Amazon CloudWatch alarms– Two CloudWatch alarms that monitor the load on the instances in your environment and are triggered if the load is too high or too low. When an alarm is triggered, your Auto Scaling group scales up or down in response.
AWS CloudFormation stack– Elastic Beanstalk uses AWS CloudFormation to launch the resources in your environment and propagate configuration changes. The resources are defined in a template that you can view in the AWS CloudFormation console.
Domain name– A domain name that routes to your web app in the form
subdomain.region.elasticbeanstalk.com.
Elastic Beanstalk manages all of these resources. When you terminate your environment, Elastic Beanstalk terminates all of the resources that it contains.
Note
The S3 bucket that Elastic Beanstalk creates is shared between environments and is not deleted during environment termination. For more information, see Using Elastic Beanstalk with Amazon Simple Storage Service.