- Newest
- Most votes
- Most comments
This error indicates that AWS currently doesn't have enough available On-Demand capacity in your requested Availability Zone to fulfill your instance start request. This is a temporary capacity constraint that can affect instances that stop and start regularly.
Here are several approaches to resolve this:
-
Wait and retry: Capacity constraints are often temporary. Wait a few minutes and try starting your instance again, as AWS continuously works on provisioning additional capacity.
-
Try a different instance type: If your workload allows, you can modify your instance to use a different instance type that has available capacity. Stop the instance, change the instance type through the console or CLI, and attempt to start it again.
-
Launch without specifying an Availability Zone: If you're launching a new instance, you can let AWS automatically select an Availability Zone with available capacity rather than specifying one.
-
Use a different Availability Zone: If possible, launch your instance in a different Availability Zone within your region that currently has capacity for your instance type.
-
Consider instance type flexibility: For workloads that can tolerate variations in instance types, you might implement automated solutions that can switch to compatible alternative instance types when capacity constraints occur.
-
Plan ahead with capacity reservations: For critical workloads that require guaranteed capacity, consider using On-Demand Capacity Reservations to reserve capacity in advance.
The key is that this is a temporary availability issue rather than a problem with your instance itself, and AWS is continuously working to add capacity.
Sources
Handling EC2 Capacity Constraints with Automated Instance Type Flexibility | AWS re:Post
Troubleshoot Amazon EC2 instance launch issues - Amazon Elastic Compute Cloud
Troubleshoot Amazon EC2 Auto Scaling: EC2 instance launch failures - Amazon EC2 Auto Scaling
