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.