AWS Practice
AWS Savings Plans vs Reserved Instances. The real trade.
Savings Plans and Reserved Instances both trade a usage commitment for a discount. The differences in flexibility and exit decide which one costs you less.
Savings Plans and Reserved Instances both trade a usage commitment for a discount. The differences in flexibility and exit decide which one costs you less.
Savings Plans and Reserved Instances reach similar headline discounts, but the flexibility, the exit path, and the capacity guarantee are where the real money is won or lost.
A Savings Plan commits you to a dollar amount of compute per hour for one or three years. A Reserved Instance commits you to a specific instance configuration for the same term. Both reach the same maximum discount, but the unit of commitment is different.
That difference in unit is the whole decision. A dollar per hour commitment flexes across whatever you run. An instance commitment only pays off if you keep running that instance.
AWS documents both on its Savings Plans page and its Reserved Instances pricing page. Read the discount tables there before you model anything.
You commit to spend, AWS applies the discounted rate to usage that matches the plan, and any usage above the commitment bills at On Demand. Usage below the commitment is still charged. You pay for what you promised, used or not.
The three year term and the All Upfront option each add discount. They also each add risk. Three years is a long time for a cloud architecture to stay still, and All Upfront ties up cash you could deploy elsewhere.
AWS commitment instruments compared
| Instrument | Max discount | Flexibility | Exit / resale |
|---|---|---|---|
| Compute Savings Plan | Up to 66% | Any family, size, region, Lambda, Fargate | None, runs to term |
| EC2 Instance Savings Plan | Up to 72% | Size within one family and region | None, runs to term |
| Standard RI | Up to 72% | Fixed family and region | Sellable on RI Marketplace |
| Convertible RI | Up to 66% | Exchangeable for other configs | Exchange only, no resale |
Compute Savings Plans are the most flexible instrument AWS sells. The discount moves with your usage, so re architecting mid term does not strand the commitment. That flexibility costs a few points of discount versus the locked options.
The trade is simple. You pay a small premium for the right to change your mind. On most estates that premium is cheaper than the shelfware a locked commitment creates.
The standard cloud advice is to maximize the discount by buying three year All Upfront EC2 Instance Savings Plans across the estate. We disagree. In roughly two thirds of the AWS estates we benchmarked in 2024 and 2025, the locked three year commitment stranded 20 to 35 percent of its value when workloads moved family or region before the term ended. The buyer side move is to commit conservatively to a Compute Savings Plan baseline you are certain to use, then layer additional commitment only as usage proves stable. The extra few points from locking are not worth the shelfware they create.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
On AWS the cheapest commitment is the one you are certain to consume, not the one with the largest headline discount.
A Reserved Instance still wins in two specific cases: when you need a capacity guarantee in a named Availability Zone, and when you want an exit route through resale. Savings Plans give neither.
If your workload must have capacity reserved, a zonal Reserved Instance or a separate capacity reservation is the only instrument that delivers it. The discount is secondary to the guarantee.
Savings Plans and Reserved Instances are billing constructs. A capacity reservation is a separate object that holds capacity in an Availability Zone. AWS explains the distinction in its Reserved Instances documentation. Do not assume a discount instrument guarantees capacity.
Standard Reserved Instances can be listed for sale on the Reserved Instance Marketplace if your needs change. That resale path is the only true exit among these instruments, and it is worth keeping a portion of commitment in Standard RIs for that reason alone.
The savings come from sizing the commitment to proven, stable usage and refusing the pressure to commit everything at once. Use Cost Explorer recommendations as an input, not an instruction.
Use the AWS Cost Explorer recommendations to see the savings curve, then commit below the recommended line. The recommendation assumes your usage is permanent. You know it is not.
Before a commitment expires, pull the actual coverage and utilization. Renew only the portion that stayed used, drop the rest to On Demand, and re evaluate the term length against your current architecture roadmap.
Both reach up to 72 percent off On Demand, but only locked instruments hit the top rate. Compute Savings Plans cap near 66 percent because you pay for flexibility. EC2 Instance Savings Plans and Standard RIs reach the higher number by giving up flexibility.
No. Savings Plans cannot be sold or cancelled and run to the end of their term. Only Standard Reserved Instances can be listed on the AWS Reserved Instance Marketplace, which makes them the only commitment with a resale exit.
No. A Savings Plan is purely a billing discount and never reserves capacity. To guarantee capacity in an Availability Zone you need a zonal Reserved Instance or a separate On Demand Capacity Reservation.
Choose 1 year unless the workload and architecture are genuinely fixed for three years. The extra discount on the three year term is often lost to shelfware when usage moves family or region before the commitment ends.
A Compute Savings Plan applies across any instance family, size, region, plus Lambda and Fargate. An EC2 Instance Savings Plan is locked to one instance family in one region in exchange for a higher discount.
Convertible RIs let you exchange for other configurations during the term but cannot be resold and cap near 66 percent. In most cases a Compute Savings Plan delivers similar flexibility with less administrative overhead.
Commit only the stable usage floor you have held for two quarters or more, layer additional commitment in tranches as usage proves stable, and default to the flexible Compute Savings Plan rather than locked instruments.
An Enterprise Discount Program commitment sits on top of these instruments and counts Savings Plan and RI spend toward the EDP commit. Model the EDP discount and the instrument discount together, not separately, before signing.
Savings Plan and Reserved Instance layering, EDP commitment math, the discount levers, and the renewal moves that cut an over committed AWS estate.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
