AWS Savings Plans vs Reserved Instances: discount vs flexibility.

01 Key findings

1. The 6-point gap is the price of flexibility. Standard RIs reach up to 72% and Compute Savings Plans near 66%. That spread buys the freedom to move across families, regions and operating systems — almost always worth paying for a changing estate.

2. Coverage and utilisation beat the headline rate. A commitment covering 100% of a workload at 60% beats one covering 70% at 72%, because the uncovered portion runs at full on-demand. The effective saving is decided by how well the commitment matches actual usage.

3. Savings Plans exist because RIs were painful. AWS launched Savings Plans in 2019 to remove the constant rebalancing, exchanging and Marketplace selling RIs demanded. For most new commitments the real question is which Savings Plan type, with Standard RIs reserved for narrow cases.

4. Stranded commitment is the core RI risk. A Standard RI bound to a family you abandon mid-term bills on while delivering zero coverage; the only escape is the RI Marketplace at a partial recovery. Savings Plans commit to spend, so the discount follows the workload.

5. One genuine RI advantage survives. Zonal Reserved Instances reserve capacity in a specific Availability Zone, which no Savings Plan offers — decisive for scaling or DR in a constrained instance type.

02 Discount vs flexibility scorecard

Relative commercial strength across the dimensions that move an AWS commitment decision. Five dots = strongest. Savings Plans dominate flexibility and coverage; Reserved Instances win discount depth, resale and capacity reservation.

03 Discount depth compared

The discount ladder is consistent across both instruments: the more you lock down, the deeper the discount. Standard RIs at three-year all-upfront sit at the top of the savings ladder; Compute Savings Plans sit higher on price because they buy flexibility. The numbers below are ceilings, not typical outcomes — realised discount depends on family, region, payment option, and match to actual usage.

Payment option moves the number too: all-upfront beats partial-upfront beats no-upfront, with a few points of spread between them. The wider commercial structure these sit inside is documented in our AWS Enterprise Agreement and EDP pillar, where EDP applies to net spend after RI or Savings Plan discounts — so the reductions compound rather than add.

04 Commitment profiles

05 Flexibility & stranded risk

The core risk with Reserved Instances is stranded commitment. A Standard RI bound to a specific family cannot follow a workload that re-architects onto a newer instance generation or migrates to a different region. The commitment continues to bill while delivering no coverage, and the only escape is the RI Marketplace, where a seller often recovers only part of the outlay. Convertible RIs mitigate this through exchange, but at a lower discount and with the administrative friction of managing exchanges across an estate.

Savings Plans remove the stranding risk for compute by committing to spend rather than configuration. As workloads move across families and regions, the discount follows automatically with no exchange to manage. The trade-off is that neither Savings Plans nor most RIs can be cancelled, so over-committing to a baseline that later shrinks leaves unused commitment in both models. The discipline is to commit only the spend floor you are confident will persist, and cover the variable layer with more flexible instruments. See AWS Savings Plans for the full mechanics.

One genuine RI advantage survives the flexibility argument: zonal Reserved Instances can reserve capacity in a specific Availability Zone, which Savings Plans do not. For workloads that must guarantee capacity for scaling events or disaster recovery in a constrained instance type, a zonal RI buys an insurance no Savings Plan offers. It is a narrow case, but where it applies it is decisive.

06 Worked coverage example

Consider an estate spending $1,000,000 per year on EC2 across always-on production, steady-state batch, and spiky development workloads. A naive approach commits the full $1,000,000 to a three-year Standard RI portfolio at 72%, but development load that disappears in month eight strands a quarter of that commitment, dragging the effective discount down sharply.

The disciplined approach segments the spend. The $600,000 always-on production floor goes to a three-year Compute Savings Plan at roughly 60%, following the workload as families evolve. The $250,000 steady batch on a mature family goes to a three-year EC2 Instance Savings Plan or Standard RI near 70%. The remaining $150,000 of spiky development stays on on-demand, where paying full rate on transient load beats stranding a commitment. The blended outcome captures most of the available discount while carrying almost no stranded-commitment risk — which a single-instrument approach cannot match. This is core to our AWS optimization work, where commitment coverage is modelled from billing data rather than forecast.

07 Common commitment mistakes

Four mistakes recur. The first is over-committing on a forecast that includes growth which has not yet materialised, stranding commitment when the growth slips. The second is buying Standard RIs on a family the estate is actively migrating away from — the classic stranded-commitment trap. The third is ignoring payment-option economics, paying no-upfront when the cash position would have supported all-upfront and captured several more points of discount.

The fourth, and most common in practice, is treating commitment as a one-time annual purchase rather than a continuous coverage discipline. Workloads change weekly; a portfolio reviewed once a year drifts out of alignment and leaves both uncovered on-demand spend and stranded commitment at the same time. The estates that capture the most discount review coverage monthly and adjust the variable layer accordingly.

08 Term & payment options

Both instruments come in one-year and three-year terms, and the term choice is its own discount lever. The three-year term roughly doubles the one-year discount on the same commitment, but it doubles the exposure to workload change, instance-generation refreshes, and AWS pricing moves. For a stable production floor the three-year term is the clear economic choice; for anything uncertain, the one-year term preserves optionality at a known cost. Many estates ladder their commitments on a staggered schedule so no single renewal forces an all-or-nothing decision.

Payment option moves the number again. All-upfront captures the deepest discount, partial-upfront a little less, no-upfront the least. The right choice is a treasury decision as much as a procurement one: an estate with the cash and a stable baseline captures the extra points with all-upfront, while one that prefers to preserve cash flow accepts a slightly shallower discount for monthly billing. Modelling the floor from at least twelve months of billing data, then committing to it with the deepest term and payment the floor can safely bear, is the discipline that separates a well-run commitment portfolio from a guessed one.

09 The verdict