EC2/EBS Throttling / Quota Diagnostic Troubleshooter (Part 5)
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 |
|---|---|---|---|---|
| 5 | quota — On-Demand Instance vCPU quota exceeded | On-Demand Instance quotas are managed in terms of the number of virtual central processing units (vCPUs) that your running On-Demand Instances are using, regardless of the instance type. | The requested instance launch would exceed the maximum number of vCPUs allowed by the On-Demand Instance quota for the account in that Region. | Request a quota increase using the Service Quotas console. |
| 6 | quota — EC2 Fleet / Spot Fleet target capacity quota exceeded | If you need more than the default quota for target capacity, you can request a quota increase. ... For Limit, choose Target Fleet Capacity per Fleet (in units) or Target Fleet Capacity per Region (in units) | The EC2 Fleet or Spot Fleet target capacity request exceeded the default quota limit (10,000 per fleet or 100,000 per Region). | Open the AWS Support Center Create case form and submit a "Service limit increase" for "EC2 Fleet". |
| 7 | quota — Archived snapshots per volume / concurrent archive quota | Archived snapshots per volume: 25 / Concurrent in-progress snapshot archives per account: 25 | N/A | N/A |