On AWS, a three year Savings Plan or Reserved Instance discounts deeper, roughly up to 72 percent against on demand versus closer to 66 percent for a one year term, but it locks you in for three times as long with no way to cancel. The right choice is not the deepest discount, it is the longest term your forecast can defend: commit three year terms only to the steady floor of demand you are confident will still run in three years, use one year terms for demand that is steady but less certain, and leave variable peaks on demand. Because the unused portion of any commitment is still owed, term length is a utilization risk you carry, so the buyer goal is high utilization across a laddered portfolio rather than the maximum headline discount.
Here is the real tradeoff between the two terms, the math that decides it, and a laddering approach that captures most of the discount without betting three years on a forecast you cannot stand behind.
What do you actually gain by going from one year to three?
The three year term buys a deeper discount in exchange for a longer lock. Indicative depths run to roughly up to 72 percent against on demand for three year all upfront Savings Plans and Reserved Instances, against roughly up to 66 percent for the equivalent one year term, with the exact gap depending on instance family, region, and payment option. That marginal six or so points sounds small, but on a large steady base it compounds. The catch is that the deeper rate only pays off if the committed capacity stays utilized for all thirty six months. A three year commitment that goes underutilized in month twenty after a rearchitecting or a migration can easily give back more than the extra discount it bought. Verify current depths against the AWS pricing pages, since published rates change.
One year or three year: which fits which workload?
| Dimension | One year term | Three year term |
|---|---|---|
| Indicative discount | Roughly up to 66 percent vs on demand | Roughly up to 72 percent vs on demand |
| Lock in | 12 months, refreshes annually | 36 months, no cancellation |
| Forecast confidence needed | Moderate, one year horizon | High, three year horizon |
| Best for | Growing or shifting fleets, newer workloads | Mature, stable demand floors and steady databases |
| Main risk | Smaller discount left on the table | Stranded commitment if the workload moves or shrinks |
The deciding question is not how much discount you can get, it is how confident you are the demand will still be there. Figures are indicative; confirm against current AWS pricing.
How do you ladder the two terms together?
Treat coverage as layers against a demand profile. Identify the floor that runs every hour through troughs and quiet seasons, then split it by confidence. The deepest, most certain part of the floor, a stable production database or a baseline service that has run flat for years, carries three year commitments. The next layer, steady but subject to a possible rearchitecting or growth, carries one year commitments that you renew or adjust annually. The variable peak above the floor stays on demand. Laddering staggers your renewal dates too, so you are never forced to recommit the whole portfolio in a single quarter against one point in time forecast. Aim for utilization in the high nineties on every layer rather than the highest coverage percentage.
A worked example
A scaling fintech was about to put its entire steady compute base on three year all upfront Savings Plans to chase the deepest rate. Reviewing the demand profile showed that only about 60 percent of that base was genuinely durable production demand; the rest was a platform mid rearchitecting that would change instance families within a year. We put the durable 60 percent on three year terms, the uncertain portion on one year terms, and left the variable peak on demand. When the rearchitecting landed, the one year layer simply was not renewed against the old families, avoiding a stranded three year lock, while the three year base kept compounding its deeper discount. The laddered structure was part of the program that left the company 41 percent lighter on cloud spend. Figures are verified against billing data and anonymised.
Frequently asked questions
Is a three year AWS Savings Plan worth it?
Can you cancel an AWS Savings Plan or Reserved Instance early?
How do you split coverage between one year and three year terms?
Get your AWS commitment term right
We size and ladder AWS Savings Plan and Reserved Instance portfolios to a forecast you can defend, as an independent advisory that takes zero provider commissions and answers only to you. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on a Fixed Fee or a no risk Gainshare basis. Download the AWS Savings Plan kit, read the deeper AWS cost optimization guide, and compare instruments in Reserved Instances versus Savings Plans.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.