EC2/EBS Quota & Limit Diagnostic Troubleshooter (Part 3)
Use the interactive troubleshooter below to identify your EC2/EBS quota or limit symptom, review the raw evidence, understand the root cause, and apply the recommended fix.
🚨 Step 1: What specific error symptom are you experiencing?
Please click the most accurate description:
Quick Reference Table
| # | Scenario | Key Error Signal | Root Cause | The Fix |
|---|---|---|---|---|
| 1 | EBS Volume Limit Exceeded (Immediate Termination) | "StateReason": { "Message": "Client.VolumeLimitExceeded: Volume limit exceeded", "Code": "Server.InternalError" } | The AWS account exceeded its permitted number of EBS volumes or total volume storage quota upon instance launch. | Delete unused volumes. You can submit a request to increase your volume limit. |
| 2 | Regional On-Demand Instance Quota Exhaustion | InstanceLimitExceeded error when you try to launch a new instance or restart a stopped instance | The account reached the default limit on the number of On-Demand instances that can be launched in a specific Region. | You can request an instance limit increase on a per-region basis. |
| 3 | Spot Instance vCPU Limit Exceeded | spotInstanceCountLimitExceeded You've reached the limit on the number of Spot Instances that you can launch. (Also: Max spot instance count exceeded) | The total number of vCPUs for running or requested Spot Instances exceeded the Region's Spot capacity quota. | Request a quota increase using the Service Quotas console. |
| 4 | EBS Volume I/O or Throughput Throttling | BurstBalance displays the burst bucket balance for gp2, st1, and sc1 volumes... volume I/O (for gp2 volumes) or volume throughput (for st1 and sc1 volumes) is throttled to the baseline. | The burst bucket balance was depleted due to sustained heavy I/O, dropping performance to baseline limits. | Consider using a larger gp2 volume that provides enough baseline IOPS performance, or a gp3, io1, or io2 volume. |