How do I troubleshoot InsufficientInstanceCapacity errors when I start or launch an EC2 instance?

2 minute read
3

When I try to start or launch my Amazon Elastic Compute Cloud (Amazon EC2) instance, I receive an insufficient capacity error.

Resolution

If AWS doesn't have enough available On-Demand capacity to complete your request, then you receive the following error:

"An error occurred (InsufficientInstanceCapacity) when calling the RunInstances operation (reached max retries: 4). We currently do not have sufficient capacity in the Availability Zone you requested."

Troubleshoot the error

To troubleshoot the InsufficientInstanceCapacity error, use the following options:

  • Wait a few minutes, and then submit your request again.
  • Submit a new request with fewer instances.
  • If you're launching an instance, then submit a new request, but don't specify an Availability Zone.
    Note: If you launch the instance in a non-default VPC, then select a subnet in a different Availability Zone.
  • If you're launching an instance, then submit a new request for a different instance type.
    Note: You can resize the instance after launch.

You might receive an insufficient capacity error if you launch the instance into a cluster placement group. For more information, see Placement groups for your Amazon EC2 instances.

Move the instance

If you continue to receive the error, then move the instance to another Availability Zone.

Avoid insufficient capacity errors on critical machines

To reserve capacity for critical machines, it's a best practice to create On-Demand Capacity Reservations in advance. Complete the following steps:

  1. Create the Capacity Reservation in an Availability Zone.
  2. Launch critical instances into your Capacity Reservation. You can view real-time Capacity Reservation usage, and launch instances into it as needed.

Note: If there isn't enough capacity, or you exceed your On-Demand Instance quota, then you can't create a Capacity Reservation. For more information, see Limitations.

Related information

Why can't I start or launch my EC2 instance?

AWS OFFICIALUpdated a month ago
8 Comments

I'm curious how I can ask to launch EC2 instance in any AZ, using AWS CLI? Currently, I'm using "aws ec2 run-instances .... --subnet-id subnet-xxxx", where subnet-xxxx is one of subnets for my custom VPC, located in specific AZ.

Thanks, Vitaly

replied 2 years ago

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

AWS
EXPERT
replied 2 years ago

Why would I get this error on a dedicated host? Thats what I'm getting for a dedicated mac host - m2.metal. "Failed to start the instance i-092ca07b85cd0a87c Dedicated host h-0c86b2bf6ea52b192 has insufficient capacity to launch the instances in this request."...

replied a year ago

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

AWS
EXPERT
replied a year ago

Is this related to a lack of capacity for AWS EC2 instances overall, or a lack of capacity for AWS EC2 instances at the user's specific organization?

replied 6 months ago

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

AWS
MODERATOR
replied 6 months ago

It is worth noting that this option: "If you're launching an instance, then submit a new request, but don't specify an Availability Zone." is only applicable for the default VPC. This option is not available for non-default VPCs

AWS
replied a month ago

Thank you for your comment. We'll review and update the Knowledge Center article as needed.

AWS
replied a month ago