instances whe it creates the environment. The EB environment automatically creates the names of the internal EC2, S3. This EB environment name is not the same as the names of any EC2 instance, any RDS instance or anything else within that EB environment. Click next and you are taken to the Application details screen. It is far too easy to attempt to click on 'Next' without doing this step, especially when it appears to be lit. For new deployments, select the "AWS Elastic Beanstalk" item form the list box.In this case, I am using the EU West region which is based in Ireland. When you have completed this box click OK.įig 6 - Creating a new AWS account record (your existing AWS account) In the popup that appears, this is where the Secret Key and and Access Key ID are used from previous stages. Click the 'Add account' icon next to the accounts dropdown, or select an existing account to use for deployment.It is a matter of using the following dialog box. Republishing is the just publishing step without having to enter the publishing settings again.Ĭonfiguring the publishing process from inside VS2010 is actually pretty simple. I've highlighted the differences in the image above. That means you can really only deploy one project at a time from here.
Makes sure your access keys are correctįig 4 - Items added to the project context menu after AWS Toolkit is installedĪfter installing the AWS toolkit, you'll note that unlike VS2010, the context menu elements to deploy a project are only available at the project level, not the solution level.Tests your CI server (or even PC) can connect to the AWS environment.Allows you to create a deployment file which AWSDeploy.exe uses to deploy your application to EB.