• Your VPC needs at least one public and one private subnet.
• In the ELB Subnet drop-down list, specify the public subnet. The Toolkit for Visual Studio deploys the Elastic Load Balancing load balancer for your application to the public subnet. The public subnet is associated with a routing table that has an entry that points to an Internet gateway. You can recognize an Internet gateway because it has an ID that begins with igw- (for example, igw-83cddaex). Public subnets that you create by using the Toolkit for Visual Studio have tag values that identify them as public.
• In the Instances Subnet drop-down list, specify the private subnet. The Toolkit for Visual Studio deploys the Amazon EC2 instances for your application to the private subnet.
• The Amazon EC2 instances for your application communicate from the private subnet to the Internet through an Amazon EC2 instance in the public subnet that performs network address translation (NAT). To enable this communication, you will need a VPC security group that allows traffic to flow from the private subnet to the NAT instance. Specify this VPC security group in the Security Group drop-down list.
For more information about how to deploy an Elastic Beanstalk application to a VPC, go to the AWS Elastic Beanstalk Developer Guide.
1. After you have filled in all of the information on the VPC Options page, choose Next.
• If you selected Enable Rolling Deployments, the Rolling Deployments page will appear.
• If you did not select Enable Rolling Deployments, the Application Options page will appear. Skip ahead to the instructions later in this section that describe how to use the Application Options page.
2. If you selected Enable Rolling Deployments, you specify information on the Rolling Deployments page to configure how new versions of your applications are deployed to the instances in a load-balanced environment. For example, if you have four instances in your environment and you want to change the instance type, you can configure the environment to change two instances at a time. This helps ensure your application is still running while changes are being made.
3. In the Application Versions area, choose an option to control deployments to either a percentage or number of instances at a time. Specify either the desired percentage or number.
4. Optionally, in the Environment Configuration area, select the box if you want to specify the number of instances that remain in service during deployments. If you select this box, specify the maximum number of instances that should be modified at a time, the minimum number of instances that should remain in service at a time, or both.
5. Choose Next.
6. On the Application Options page, you specify information about build, Internet Information Services (IIS), and application settings.
7. In the Build and IIS Deployment Settings area, in the Project build configuration drop-down list, choose the target build configuration. If the wizard can find it, Release appears otherwise, the active configuration is displayed in this box.
8. In the App pool drop-down list, choose the version of the .NET Framework required by your application. The correct .NET Framework version should already be displayed.
9. If your application is 32-bit, select the Enable 32-bit applications box.
10.In the App path box, specify the path IIS will use to deploy the application. By default, Default Web Site/ is specified, which typically translates to the path c:\inetpub\wwwroot. If you specify a path other than Default Web Site/, the wizard will place a redirect in the Default Web Site/ path that points to the path you specified.
11.In the Application Settings area, in the Health check URL box, type a URL for Elastic Beanstalk to check to determine if your web application is still responsive. This URL is relative to the root server URL. The root server URL is specified by default. For example, if the full URL is example.com/site-is-up.html, you would type /site-is-up.html.
12.In the area for Key and Value, you can specify any key and value pairs you want to add to your application's Web.config file.
NoteAlthough not recommended, you can use the area for Key and Value, to specify AWS credentials under which your application should run. The preferred approach is to specify an IAM role in the Identity and Access Management Role drop-down list on the AWS Options page. However, if you must use AWS credentials instead of an IAM role to run your application, in the Key row, choose AWSAccessKey. In the Value row, type the access key.
Repeat these steps for AWSSecretKey.
13.Choose Next.
14.On the Review page, review the options you configured, and select the Open environment status window when wizard closes box.
15.If everything looks correct, choose Deploy.
NoteWhen you deploy the application, the active account will incur charges for the AWS resources used by the application.
Information about the deployment will appear in the Visual Studio status bar and the Output window.
It may take several minutes. When the deployment is complete, a confirmation message will appear in the Output window.
16.To delete the deployment, in AWS Explorer, expand the Elastic Beanstalk node, open the context (right-click) menu for the subnode for the deployment, and then choose Delete. The deletion process might take a few minutes.