I have deployed an ASP.NET application with AWS Elastic Beanstalk using the following steps:
- Published application to a ZIP file in Visual Studio
- Created Elastic Beanstalk application and environment, using the published ZIP file
All necessary AWS services were provisioned successfully and the application package appears under the Default Website in IIS on the EC2 instance (see screenshot).
However, I get 403 errors when I try to browse both the Default Website and the application directory (using the "browse" link in the IIS manager).
My question is this: Using Elastic Beanstalk, how do I deploy the application package as a "proper" web site that I can configure to respond to my domain?
I know how to set up a web site and import the application package manually, but I would really like to automate the process with Elastic Beanstalk since we will be deploying to both our staging and production environments frequently.