Elastic Beanstalk could not find any platforms

Question

I'm trying to deploy my django app via amazon Elastic BeanStalk(using this tutorial), but getting the following error.

ERROR: Elastic Beanstalk could not find any platforms. Ensure you have the necessary permissions to access Elastic Beanstalk.

How can i fix this issue?

Thanks!

Answer 1

Problem is, as @helloV said, your user does not have access. Now this was a complete surprise to me because I was using the root (which I really shouldn't) and I ASSUMED it would just have access.

So solution is that you HAVE TO ATTACH a policy as shown in the screenshot below since even the root IAM account does not have this policy.

Answer 2

Your IAM account does not have permission to access Elastic Beanstalk. Contact your IAM admin and have the admin grant your account full Elastic Beanstalk permissions.

Answer 3

I had this issue as well. There is a file in /Users/USER_NAME/.aws/ called config.

It looks like below -

[profile eb-cli]
aws_access_key_id = <ACCESS_KEY>
aws_secret_access_key = <SECRET_ACCESS_KEY>

Update this file with your updated aws_access_key_id & aws_secret_access_key

Credit: How to change the AWS account using the Elastic Beanstalk CLI

Answer 4

rm ~/.aws

This fixed the issue for me (updating ~/.aws/config or ~/.aws/credentials in here didn't help)

Answer 5

Not much of an answer, but I'll leave it here for anyone else so they don't frustrate themselves debugging an issue that doesn't require debugging.

IAM permissions don't seem to always provision immediately, & even when they do sometimes the CLI doesn't seem to pick this up right away (would welcome any technical expansion on why this is).

In my case, I ensured that my IAM user had the permission AWSElastikBeanstalkFullAccess. Running eb init was still prompting ERROR: NotFoundError - Elastic Beanstalk could not find any platforms. Ensure you have the necessary permissions to access Elastic Beanstalk.

Fighting with this did nothing, after about 5 minutes I ran again and all was well. Next I run eb create to create an environment. Same issue. I gave it about another 5 minutes, tried again, and all was well.

I can't expand on why this is, but I wanted to make sure my experience was documented here so future readers don't tear their hair out fighting a permissions error when they have proper permissions.