This is the base image you’ll customize later. For example, for the Sydney region, for the 64bit Windows Server 2016 v1.2.0 running IIS 10.0 platform, the AMI ID is ami-e04aa682. This is determined by the selected platform and the region. Under Instances, you’ll find the default AMI that Elastic Beanstalk will use.NET (Windows/IIS) as the preconfigured platform. On the Create new environment page, choose.Open the Elastic Beanstalk console and create a new application by choosing Create New Application.

How to identify which Elastic Beanstalk image to customize Finally, we attach the Visual Studio debugger to the remote process running inside the EC2 instance started by Elastic Beanstalk. To allow communication with the Visual Studio remote debugger, we set up proper security groups. Then, we start an Elastic Beanstalk environment with this custom image. Next, we install Visual Studio remote debugger as a service and create a custom image from it. You can use this approach in your development environments.įirst, we create an Amazon EC2 instance from a base Elastic Beanstalk image. NET application running on Elastic Beanstalk? This article describes a one-time setup of Elastic Beanstalk that enables you to remote debug in real time. You simply upload your application, and Elastic Beanstalk automatically handles the details of capacity provisioning, load balancing, scaling, and application health monitoring. Elastic Beanstalk reduces management complexity without restricting choice or control. With Elastic Beanstalk, you can quickly deploy and manage applications in the AWS Cloud without worrying about the infrastructure that runs those applications. We love to run IIS websites on AWS Elastic Beanstalk. In this guest post by AWS Partner Solution Architect Sriwantha Attanayake, we take a look at how you can set up remote debugging for ASP.NET applications deployed to AWS Elastic Beanstalk.

What is visual studio remote debugging