Why am I receiving a "no Spot capacity available" error when trying to launch an Amazon EC2 Spot Instance?
Last updated: 2021-09-23
I get an error message stating "There is no Spot capacity available that matches your request." when trying to launch an Amazon Elastic Compute Cloud (Amazon EC2) Spot Instance. How do I troubleshoot this error?
This error occurs when Amazon EC2 doesn't have enough Spot Capacity to fulfill your Spot Instance or Spot Fleet request. Spot capacity is the amount of spare, unused EC2 compute capacity that's made available for customers to use at a price lower than On-Demand Instances.
To troubleshoot this error, do one of the following:
- Leave the request as is. The Spot request continues to automatically make the launch request until capacity becomes available. When capacity becomes available, Amazon EC2 fulfills the Spot request. If you encounter the "no Spot Capacity available" error frequently, consider using the next workaround around.
- Be flexible about which instance types you request and which Availability Zones you deploy your workload in. For example, instead of requesting an m5.large in us-east-1a, request an m4.large, c5.large, r5.large, t3.xlarge, and so on, in multiple Availability Zones. This type of request increases the chances of AWS finding and allocating your required amount of compute capacity.
- Use the capacity-optimized allocation strategy within your Auto Scaling group. The capacity-optimized strategy analyses real-time capacity data to launch your Spot Instances into pools with the most available capacity. This strategy reduces the chances of receiving "no Spot Capacity available" errors. For more information about allocation strategies, see Spot Instances in the Amazon EC2 Auto Scaling User Guide.
For a complete list of best practices for utilizing Spot Instances successfully, see Spot Instance Best Practices.