EC2/EBS Quota & Limit Diagnostic Troubleshooter (Part 6)
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 | Elastic IP Address Quota Exhaustion During Transfer | AddressLimitExceeded | The transfer account exceeded the Elastic IP address quota (default 5 per Region) when attempting to accept an Elastic IP transfer. | Request a quota increase directly from the Service Quotas console. |
| 6 | EC2 Fleet Spot Instance Limit Exceeded | "detail-type": "EC2 Fleet Error", "sub-type": "spotInstanceCountLimitExceeded" | You've reached the limit on the number of Spot Instances that you can launch during fleet fulfillment. | N/A |
| 7 | EC2 Fleet Instant Deletion Hard Limit | "Code": "ExceededInstantFleetNumForDeletion", "Message": "Can't delete more than 25 instant fleets in a single request." | A request attempted to delete more than 25 instant fleets at the same time, which violates the maximum allowed deletion threshold for a single request. | N/A |
| 8 | EC2 Instance Connection Tracking Allowance Exceeded | conntrack_allowance_exceeded / conntrack_allowance_available (via ethtool -S eth0) | Packets were dropped because connection tracking exceeded the maximum limit for the instance type and new connections could not be established. | Scale either the number of instances registered with the load balancer or the size of the instances registered with the load balancer. |