I\'m trying to deploy a test site to AWS via the toolkit for visual studio, and I\'m gettin
I was having the same issue. It turned out that what was happening was that my Secret Access Key
on my profile was missing a character. Fixing this made everything else run smoothly.
AWS.
First, go to AWS, click on Services -> IAM, at the top left. Follow the instructions at http://docs.aws.amazon.com/IAM/latest/UserGuide/Using_SettingUpUser.html to create an IAM user. This will create an alias, essentially, for your account. You will need the access key and secret key, so download the file when prompted.
Second, while in the IAM management portal, click on Policies, on the left. You can check up to two options, and use them to create a Policy. Choose EC2 and Elastic Beanstalk, full access for each. You should do this with the IAM user you created, though I believe that you can use your main account.
Finally, you'll need to assign that profile to your web project. In the AWS Explorer, click on the New Account Profile at the top. You'll be prompted to enter some information; here is where you will need those keys. Once that is all done, try the Publish to AWS wizard, again.
Have you given your profile permission to Create an EC2 and Elastic Beanstalk instance?
So, for me I tried everything mentioned here and it still wasn't working. After stepping away for 2 hours I tried it again... and it worked!!
Looks like there was a sync delay of some sort in my case.
For me, it was a connection problem. Before publishing check if the aws explorer in VS is showing the resources. If it doesn't then the connectivity needs to be checked.
Services -> IAM -> Users -> Click on your user -> Permissions section -> Attach Policy -> Add AWSElasticBeanstalkFullAccess policy.