Steady production EC2 instances with no Compute Savings Plan coverage

What a Compute Savings Plan trades for its discount

A Savings Plan is a commitment to spend a fixed amount per hour on compute for one or three years. Compute Savings Plans are the most flexible type, with prices up to 66% off On-Demand. They apply to EC2 usage whatever the instance family, size, Region, operating system or tenancy, and also to Fargate and Lambda.

That flexibility is why Compute Savings Plans suit fleets that change shape. The discount is smaller than a Standard Reserved Instance, so ZopNight prices this rule with the Savings Plan rate, not the RI rate.

Checking coverage and AWS’s own recommendation

aws ce get-savings-plans-coverage \
  --time-period Start=2026-08-01,End=2026-09-01

aws ce get-savings-plans-purchase-recommendation \
  --savings-plans-type COMPUTE_SP --term-in-years ONE_YEAR \
  --payment-option NO_UPFRONT --lookback-period-in-days SIXTY_DAYS

The first shows how much of your spend is already covered. The second returns the hourly commitment Cost Explorer suggests from your recent usage.

Gates an instance has to clear

1. It is running on demand and is not an ECS Managed Instance.
2. Billing shows no Reserved Instance or Savings Plan already covering it, and it carries no savings_plan=true or ri_covered=true tag.
3. It is not a Spot Instance.
4. It is production, by name or by an environment tag.
5. Its cost comes from your bill and is above zero.
6. It is a true commitment candidate: at least 60 days of history, running at least 70% of the time, and average CPU or memory of 30% or more.

When the rule holds back

Non-production instances belong to the scheduling lever instead, see EC2 Heatmap-Based Schedule Opportunity. With no live Savings Plan rate for the instance, nothing is shown; there is no flat-percentage fallback. Uptime that swings around the 70% line is damped, so an instance does not flip in and out of the list. When a Reserved Instance or Spot suggestion also fits the same instance, only the better one is kept, so this finding often gives way to EC2 Reserved Instance Opportunity.

Working out the saving

basis  = lower of (current monthly cost, on-demand hourly rate x 730)
saving = basis - (1-year Compute Savings Plan hourly rate x 730)

The recommendation appears only when the saving is positive, and the percentage in its title comes from that figure.

Buying the commitment

1. Review the Cost Explorer recommendation above against the instances ZopNight lists.
2. Size the hourly commitment to the baseline you will run all year, leaving peaks on demand.
3. Purchase the Compute Savings Plan in the Billing and Cost Management console.
4. Tag covered instances savings_plan=true if you want the finding cleared before billing data catches up.