Example: Launching a Load-Balancing, Autoscaling Environment with Public Instances in a VPC
You can deploy an Elastic Beanstalk application in a load balancing, autoscaling environment in a single public subnet. Use this configuration if you have a single public subnet without any private resources associated with your Amazon EC2 instances. In this configuration, Elastic Beanstalk assigns public IP addresses to the Amazon EC2 instances so that each can directly access the Internet through the VPC Internet gateway. You do not need to create a network address translation (NAT) configuration in your VPC.
To deploy an Elastic Beanstalk application in a load balancing, autoscaling environment in a single public subnet, you need to complete the following:
Create a VPC with a Public Subnet
To create a VPC
Sign in to the AWS Management Console and open the Amazon VPC console at https://console.amazonaws.cn/vpc/.
In the navigation pane, choose VPC Dashboard and then choose Start VPC Wizard.
Select VPC with a Single Public Subnet and then choose Select.
A confirmation page shows the CIDR blocks used for the VPC and subnet. The page also shows the subnet and the associated Availability Zone.
Choose Create VPC.
AWS creates your VPC, subnet, Internet gateway, and route table. Choose OK to exit the wizard.
After AWS successfully creates the VPC, it assigns the VPC a VPC ID. You will need this for this for the next step. To view your VPC ID, choose Your VPCs in the left pane of the Amazon VPC console.
Deploy to Elastic Beanstalk
After you set up your VPC, you can create your environment inside your VPC and deploy your
application to Elastic Beanstalk. You can do this using the Elastic Beanstalk console, or you can use the AWS
toolkits, AWS CLI, EB CLI, or Elastic Beanstalk API. If you use the Elastic Beanstalk console, you just need to upload
.zip file and select the VPC settings
inside the wizard. Elastic Beanstalk then creates your environment inside your VPC and deploys your
application. Alternatively, you can use the AWS toolkits, AWS CLI, EB CLI, or Elastic Beanstalk API to
deploy your application. To do this, you need to define your VPC option settings in a
configuration file and deploy this file with your source bundle. This topic provides
instructions for both methods.
Deploying with the Elastic Beanstalk Console
When you create an Elastic Beanstalk application or launch an environment, the Elastic Beanstalk console walks you through creating your environment inside a VPC. For more information, see Managing and Configuring AWS Elastic Beanstalk Applications.
You'll need to select the VPC ID and subnet ID for your instance. By default, VPC creates a public subnet using 10.0.0.0/24. You can view your subnet ID by clicking Subnets in the Amazon VPC console.
Deploying with the AWS Toolkits, AWS CLI, EB CLI, or Elastic Beanstalk API
When deploying your application to Elastic Beanstalk using the AWS toolkits, the EB CLI, the AWS CLI, or
API, you can specify your VPC option settings in a file and deploy
it with your source bundle. See Advanced Environment Customization with Configuration Files
When you create your configuration file with your option settings, you need to specify the following configuration options:
The identifier of your VPC.
The identifier(s) of the subnet(s) to launch the instances in.
You can specify multiple identifiers by separating them with a comma.
Specifies whether to launch instances in your VPC with public IP addresses. Instances with public IP addresses do not require a NAT device to communicate with the Internet. You must set the value to
trueif you want to include your load balancer and instances in a single public subnet.
The following is an example of the option settings you could set when deploying your Elastic Beanstalk application inside a VPC.
option_settings: aws:ec2:vpc: VPCId: "
vpd_id" Subnets: "
instance_subnet, etc" AssociatePublicIpAddress: "true"