InsufficientInstanceCapacity: We currently do not have sufficient capacity in the Availability Zone you requested
AWS has no free capacity for that instance type in that Availability Zone right now.
Exact message you may see
We currently do not have sufficient capacity in the Availability Zone you requestedInsufficient capacity
Seen on:
AWS
Meaning
Popular or large types (GPU, new generations) can run out in a specific AZ. It’s temporary and not related to your account limits. Retrying later, another AZ, or another type usually works.
Common causes
- Instance type in short supply in that AZ
- Placement group/tenancy constraints
- Large simultaneous launch
⚡ Quick fix
- Launch in another AZ (subnet)
- Try a similar instance type
- Use capacity reservations for critical workloads
Detailed fix by platform
AWS CLI
aws ec2 describe-instance-type-offerings --location-type availability-zone --filters Name=instance-type,Values=g5.xlarge --region us-east-1
How to diagnose
- AZ — Which zone?
- Type — Alternatives available?
- Placement — Cluster placement group?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in AWS
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 14 Oct 2026