EC2/EBS Quota & Limit Diagnostic Troubleshooter (Part 2)
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 |
|---|---|---|---|---|
| 5 | Nitro Architecture Device Attachment Hard Limit | "Instances built on the Nitro System instances support a maximum of 28 attachments, including network interfaces, EBS volumes, and NVMe instance store volumes." | A single Nitro-based EC2 instance attempted to mount too many ENIs and EBS volumes, hitting the absolute hardware limit of 28 total attachments. | N/A |
| 6 | Cross-Region AMI Copy Concurrency Cliff | "Destination Regions are limited to 100 concurrent AMI copies." | A CI/CD deployment pipeline attempted to distribute an AMI to a single target Region across more than 100 parallel copy operations. | N/A |
| 7 | Spot Fleet EBS Volume Quota Exhaustion | "With EC2 Fleet and Spot Fleet, if you have many stopped instances, you can exceed the limit on the number of EBS volumes for your account." | Spot instances configured with a "stop" interruption behavior accumulated dormant EBS volumes over time, silently maxing out the account-level EBS volume count quota. | N/A |
| 8 | Public AMI & AMI Sharing Quotas | "Public AMIs: 5" / "AMI sharing: 1,000 (The maximum number of entities... an AMI can be shared with in a Region)." | An account attempted to make a 6th AMI public, or an automated process tried to share a private AMI with more than 1,000 separate AWS accounts. | Consider making one or more public AMIs private, share your AMIs with an organization or OU instead of separate accounts, or Request a quota increase for AMIs. |