EC2 Burstable Instance Low CPU Credits
The instance is running out of burst credits, so it is throttled to its baseline and the application slows down for a reason the CPU graph does not explain.
Free to start. No card. The playground just needs your work email.
Found, explained, handed over.
What we would change and why, with no savings claim and no policy behind it.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Change burstable EC2 instance type.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- EC2 Instances on AWS
- The fix, by hand
- In CloudWatch, check CPUCreditBalance and CPUSurplusCreditBalance for this instance. Confirm whether credits run out under sustained load or only in occasional spikes.
- Decide: for occasional bursts, enable T-unlimited mode (cheap if rare); for sustained load, move to an m5 or c5 instance of the right size.
- For T-unlimited:
aws ec2 modify-instance-credit-specification --instance-credit-specification InstanceId=‹id›,CpuCredits=unlimited. - For a family change: stop the instance, change its type, then start it.
- Re-check CPUUtilization and application latency in CloudWatch after 7 days.
These are the steps the finding carries in the product.
- Category
- Performance. A measured bottleneck worth clearing: throttled operations, undersized tiers, a workload near its limit.
- Where it appears
- The Advisory tab of Recommendations, with every affected resource listed.
- Rule ID
RC-188- Full reference
Related checks
See the performance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.