1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
1
I seem to be having the same problem as here.
The error occurs when "aws-elasticbeanstalk-ec2-role" is missing.
As described here, if you get this error, you can solve it by creating your own IAM role..
https://repost.aws/questions/QUx_V0HSWxRJSRndVaSlsvOQ/elastic-bean-stalk-environment-is-not-getting-created#ANwB9EGj4QTHycEXVvji4eEg
Also, I believe Elastic Beanstalk environments are automatically deleted if they fail to be created.
