Stay up to date with the latest from the Knowledge Center. See all new and updated Knowledge Center articles published in the last month and re:Post’s top contributors.
AWS Elastic Beanstalk - issue launching environment
Hi! I am learning AWS, and in the process of playing around with AWS Elastic Beanstalk, I noticed that my environment will not launch and stays stuck in the pending state after this warning below, and the delete application as well as the terminate environment buttons are disabled. I am using the free tier resources so I would not like to upgrade as of yet. But is there a way to re-configure to avoid this warning?
- Newest
- Most votes
- Most comments
Hello.
Looking at the logs, it seems that EC2 could not start due to EC2's vCPU limit.
Therefore, please increase the vCPU service quota limit by following the steps in the document below.
There is no charge if you simply increase the service quota limit.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html
Please change to the region you are using when upgrading.
Also, be sure to select quotas for the instance type you are using.
https://docs.aws.amazon.com/ec2/latest/instancetypes/ec2-instance-quotas.html
Relevant content
- asked 2 years ago
AWS OFFICIALUpdated 4 months ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
Thank you! This helps, I've requested a quota increase on the standard instances.