EC2/EBS Throttling / Quota Diagnostic Troubleshooter (Part 1)
Use the interactive troubleshooter below to identify your EC2/EBS throttling or quota 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 | throttl — EBS volume I/O or throughput throttled to baseline | "volume I/O (for gp2 volumes) or volume throughput (for st1 and sc1 volumes) is throttled to the baseline. Check the BurstBalance value" | The EBS volume exhausted its burst credit bucket, causing performance to drop to baseline levels. | Use a larger gp2 volume for higher baseline IOPS, or switch to gp3, io1, or io2 provisioned with sufficient IOPS. |
| 2 | limit-exceeded — Spot request failed due to EBS volume limit | limit-exceeded (Spot request status code) - "The limit on the number of EBS volumes or total volume storage was exceeded." | The Spot instance request failed to fulfill because attaching the required EBS volumes would breach the account's total volume count or storage limit. | Request an increase for Amazon EBS Limits in the AWS General Reference / Support Center. |
| 3 | quota — Max spot instance count exceeded | error "Max spot instance count exceeded." | The Spot Instance launch attempt exceeded the maximum number of virtual central processing units (vCPUs) permitted by the account's Spot Instance quota for the Region. | Request a quota increase using the Amazon EC2 Service Quotas console or the get-service-quota AWS CLI command. |