Savings Plans and Reserved Instances: A Commitment Strategy That Does Not Backfire

Commitments are the biggest single discount on AWS and the easiest way to lock in waste for three years. How we size, sequence and monitor Savings Plans and Reserved Instances for EU enterprises.

Savings Plans and Reserved Instances: A Commitment Strategy That Does Not Backfire

Commitments are the biggest single discount on AWS, and the easiest way to lock in waste for three years. We regularly see estates with high Savings Plan coverage and a bill that is still too large: the commitment was sized against oversized instances, bought in one block, and never revisited. The discount was real; it was applied to capacity nobody needed. This post is how we size, sequence and monitor commitments so they keep paying back.

Two numbers, not one

Every commitment conversation should start with two numbers, tracked separately in Cost Explorer:

They pull in opposite directions. Buying more raises coverage and risks utilisation; buying less protects utilisation and leaves coverage on the table. A dashboard that reports only coverage rewards overcommitting, which is how teams end up with 90% coverage and an unused commitment line on every invoice. High coverage on the wrong commitment is a loss, not a win.

Which instrument covers what

InstrumentApplies toFlexibility
Compute Savings PlanEC2 (any family, size, region, OS, tenancy), Fargate, LambdaHighest; follows you through migrations
EC2 Instance Savings PlanOne instance family in one region, any size, OS or tenancyDeeper discount, locked to family and region
SageMaker Savings PlanSageMaker AI instance usageAny family, size or region within SageMaker
Reserved InstancesRDS, ElastiCache, OpenSearch, Redshift, and EC2Engine, family and region specific
Database Savings PlansManaged database services, per AWS's current list of enginesNewer instrument; check coverage before buying

A few practical rules fall out of that table:

Sequence: shrink first, commit second

The order matters more than the instrument.

  1. Remove idle and rightsize first. Every unattached volume, forgotten environment and oversized instance you commit against becomes a three-year obligation. Rightsizing after a purchase does not reduce the commitment; it reduces utilisation.
  2. Commit to the floor, not the average. Look at hourly eligible on-demand spend over the last 30 to 60 days, after rightsizing. Commit near the lower end of that range, the level you are confident will still be running every hour for the term. Peaks stay on-demand or move to Spot.
  3. Flexible instruments first, specific ones second. A Compute Savings Plan for the stable compute floor, then EC2 Instance Savings Plans only for families you are sure about, then database commitments engine by engine.

A worked example (illustrative numbers)

An estate's eligible compute spend, after rightsizing, runs between $38 and $61 an hour on demand over the last 60 days, with a clear daily pattern and a floor of about $40.

Savings Plan commitments are expressed as dollars per hour of discounted spend, which is why the commitment is lower than the on-demand floor it covers. The real discount depends on your instance mix, region, term and payment option; use the AWS recommendation and pricing tools for your own numbers.

Ladder purchases instead of buying in one block

A single large purchase creates a single large expiry date and a single large bet on today's forecast. Laddering spreads both:

Laddering costs a little coverage in the first months. It removes the scenario where a three-year commitment bought in one afternoon outlives the architecture it was sized for.

Term and payment option

Three-year terms and all-upfront payment give the deepest discounts, and both increase the cost of being wrong. Our defaults:

Remember what cannot be undone. Savings Plans cannot be resold, and AWS allows returning a Savings Plan only within a short window after purchase and under specific limits. Standard EC2 Reserved Instances can be listed on the Reserved Instance Marketplace, with conditions; most other commitments are simply yours for the term.

Using the AWS recommendations without trusting them blindly

Cost Explorer produces Savings Plan and Reserved Instance purchase recommendations based on a 7, 30 or 60 day lookback. They are a useful starting point:

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

What the recommendation does not know:

Treat it as an upper bound, then cut it back to the floor you are confident in.

Organisation-level sharing

By default, Savings Plan and Reserved Instance discounts are shared across all accounts in an AWS Organization's consolidated bill. That raises utilisation, because a commitment bought for one account can absorb usage in another. It also means the account that bought the commitment does not necessarily get the benefit.

Decide deliberately:

Either way, report amortised cost to teams, so commitment benefits and fees land on the workloads that consume them. Without that, showback is skewed by whoever happens to run on covered capacity.

Monitoring after the purchase

Commitments drift as soon as they are bought. Four controls keep them honest:

What this looks like at ccX

Commitment strategy is the first of the six levers in our two-week AWS Cost Optimization Review, and it is deliberately sequenced after rightsizing and idle clean-up so you never commit against waste. We model Savings Plans and Reserved Instances against your actual hourly usage curve, recommend a laddered purchase plan with coverage and utilisation targets, and set up the budgets and alerts that keep it on track. We currently run commitment strategy in production across an EU institution's multi-account estate. Fixed fee, read-only access, never a percentage of savings.

If your Savings Plans were bought once and have not been looked at since, book a 30-minute scoping call.

Where to go from here

Discount levels, eligible services and return terms for Savings Plans and Reserved Instances change over time. Verify them against current AWS pricing and documentation before purchasing.


Sitemap