Skip to main content
Burstable T instances in Unlimited mode can run above their CPU baseline, but AWS bills the extra as surplus CPU credits. An instance that does this all the time would be cheaper as a general-purpose M instance of the same size, which has no CPU credits. nOps finds these instances and estimates the saving after the higher hourly price of the M instance.

Why it matters

T instances look cheap by the hour, so surplus credit charges are easy to miss. For an instance that is always busy, they can cost more than the instance itself.

How nOps finds it

nOps reads the last 7 days of EC2 billing. An instance is flagged when it was billed surplus CPU credits, the most recent within the last 3 days, and it ran on all 7 days. The target is the cheapest same-size M-family type for the same processor family and operating system (for example t3 to m5, m6i or m7i, t3a to m5a, m6a or m7a, t4g to m6g, m7g or m8g); sizes smaller than large map to large. The saving is the credit charge minus the extra hourly list cost of the M instance for the hours the instance ran, at your rates. Instances mostly covered by Reserved Instances and savings under $5 a month are left out.

Before you start

Permission to stop and modify the instance, and an AMI with ENA and NVMe drivers.

How to implement

  1. Check the instance’s CPU use in CloudWatch to confirm it stays above its baseline most of the time.
  2. Stop the instance, change its instance type to the recommended M type (Actions → Instance settings → Change instance type), and start it.
  3. For instances in an Auto Scaling group, change the launch template instead.
  4. Update Terraform or CloudFormation so the next deployment does not change it back.

Risks and considerations

  • Changing the instance type needs a stop and start. Older AMIs may need ENA and NVMe drivers for newer M generations.
  • For sizes below large, the M instance has more memory than the T instance, and costs more per hour; the estimate already includes that.
  • A Reserved Instance or EC2 Instance Savings Plan that covers the T instance today will not cover the new family.
  • To roll back, stop the instance and change the type back.

FAQs

In Standard mode the instance is throttled to its baseline once credits run out. If it really needs the CPU, a fixed-performance instance is the cheaper way to get it.