Skip to main content
← Back to Articles
GuideCost Optimization

What Is the Maximum AWS Savings Plan Discount? The Answer Depends on the Plan

The 72 percent discount everyone quotes is a product property, not a price. It belongs to EC2 Instance Savings Plans, which lock one instance family in one region; the flexible Compute Savings Plan most teams actually buy is capped at 66 percent, and the newer Database and SageMaker products at 35 and 64. AWS's own rate table priced m6a.large at 27 percent on the 1-year no-upfront plan and 54 percent at the absolute 3-year all-upfront maximum, where the family-locked product paid exactly the same. Here is where each ceiling lives, why your rate diverges from any headline, the ten-minute lookup that replaces the guesswork, and the order of operations that keeps the commitment sized on your bill instead of AWS's best case.

8 min readBy Hermann Lotter
What Is the Maximum AWS Savings Plan Discount? The Answer Depends on the Plan

72%

is the EC2 Instance Savings Plan ceiling, and it costs a lock to one instance family in one region

54%

is what m6a.large actually saved at the 3-year, all-upfront maximum: half the headline

27%

on the 1-year, no-upfront plan most teams buy first

The direct answer: there are four maximums, and the famous one belongs to the most restrictive product

There is no single maximum AWS Savings Plan discount. AWS sells four plan types and caps each at a different ceiling: Compute Savings Plans at up to 66 percent, EC2 Instance Savings Plans at up to 72 percent, Database Savings Plans at up to 35 percent, and SageMaker AI Savings Plans at up to 64 percent. The 72 percent everyone quotes belongs to the EC2 Instance product, which locks the commitment to a single instance family in a single region. The flexible product most teams actually buy is the 66 percent one. And the rate a specific instance receives is a lookup, not a headline: on the day we read AWS's rate table, m6a.large in N. Virginia saved 27 percent on a 1-year, no-upfront commitment and 54 percent at the 3-year, all-upfront maximum.

The distinction matters because commitments are nearly irreversible. The terms cannot be changed after purchase; the only exit is a return window for plans of $100 per hour or less, bought within the last seven days of the same calendar month. Size the commitment on a ceiling your plan type never pays and the error is contractual for a year or three. The order of operations is fixed: find your row first, then decide how much to commit.

If you only take one thing: the maximum is a property of the product, the discount is a property of your usage. Never put the first where the second belongs.

Four products, four ceilings, one blurred headline

The lineup first. Compute Savings Plans apply to EC2, Fargate and Lambda regardless of family, size, region, OS or tenancy, capped at 66 percent. EC2 Instance Savings Plans trade flexibility for depth: up to 72 percent, in exchange for locking the commitment to one instance family in one region. Database Savings Plans arrived in December 2025 and cover a dozen database services at up to 35 percent. SageMaker AI Savings Plans cap at 64 percent. Four products, four ceilings, one landing page: the Savings Plans home page says "save up to 72%" without naming which product holds it.

AWS's own documentation carries the attribution, if you read past the overview. The user guide's opening paragraph says you can save up to 72 percent on your compute workloads and then, in the same breath, describes the cross-family, cross-region flexibility that belongs to the 66 percent product. The plan types page and the Savings Plans versus Reserved Instances comparison table state the split correctly, and the launch post in November 2019 had it right from day one: Compute Savings Plans up to 66 percent, "just like Convertible RIs"; EC2 Instance Savings Plans "the largest discount", up to 72 percent, "just like Standard RIs". The compressed headline is the later invention.

  • ✓Compute Savings Plans: up to 66 percent, any EC2 family, size, region, OS or tenancy, plus Fargate and Lambda.
  • ✓EC2 Instance Savings Plans: up to 72 percent, one instance family in one region, any size, OS and tenancy inside it.
  • ✓Database Savings Plans: up to 35 percent, across a dozen database services, engines, generations and regions.
  • ✓SageMaker AI Savings Plans: up to 64 percent, any SageMaker instance family, size, component and region.

The stack behind your rate, with the receipts

A Savings Plan rate is priced per usage type, and the ceiling is what remains when every dial is turned to its best case: the deepest product, the longest term, the largest upfront payment, the cheapest family in the cheapest region, the right OS, shared tenancy. Miss one dial and the rate moves. This is not a metaphor, it is how the rate table is built: every instance in every region carries an On-Demand price and a Savings Plan rate for each combination of term and payment option, and the discount is the gap between them.

Here is the ladder for one instance, read from AWS's own table (m6a.large, US East N. Virginia, Linux, shared tenancy, at the time of writing). Twenty-seven percent at 1 year with no money down: $0.06348 against an On-Demand rate of $0.0864. Forty-nine percent at 3 years, still no upfront: $0.04382. Fifty-four percent at 3 years all upfront: $0.03976. Three commitments, three different discounts, one instance, and neither advertised ceiling anywhere in sight. The same day, the family-locked EC2 Instance Savings Plan priced m6a.large at exactly the same $0.03976. Giving up cross-family flexibility bought nothing at all for this chip.

Run the same read across the mainstream families and the pattern holds. At the 1-year no-upfront default, m5.large saved 26 percent and r6a.large 28 percent. At the absolute maximum stack, 3 years all upfront, the sampled families priced between 53 and 56 percent. AWS's own Reserved Instances page publishes averages in the same spirit: 40 percent for a 1-year standard commitment, 60 percent for a 3-year, 31 and 54 percent for convertible. The vendor is telling you what typical looks like, on the same page where the ceiling lives.

If you only take one thing: the gap between 27 percent and 54 percent is the same instance under three different commitments. Term and payment option are pricing decisions, not footnotes.

The 75 your model quotes was real. AWS retired it.

Plenty of decks and old blog posts still say 75 percent. That number has a provenance: AWS's own Reserved Instances pricing page said "up to 75%" at the end of 2019, and the archived page is still there to check. The live page says up to 72 percent for the same product. Between those two dates the headline moved down three points while the published averages stayed identical: 40 percent for 1-year standard, 60 percent for 3-year.

Savings Plans never had a 75. They launched in November 2019 with the split already in place, 66 for the flexible product and 72 for the family-locked one. If a model, a memo or a vendor calculator says 75 percent today, it is quoting a page AWS revised years ago, and it is quoting an RI number at that. The current maximums are 66 and 72 percent, and neither is a promise about your bill.

Look up your row before you size anything

The lookup takes ten minutes and replaces every assumption in the model. Three surfaces, in the order that catches the most error.

  • ✓The public rate table: Savings Plans pricing page → the Compute Savings Plans tabs for EC2, Fargate and Lambda, and the EC2 Instance tab beside them → filter to your instance, region, OS and tenancy → read the "Savings over On-Demand" column for each term and payment option. This is where the 27 and 54 percent figures in this article came from.
  • ✓Your account's own recommendation: Cost Explorer → Recommendations → Savings Plans, or the CLI: 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 THIRTY_DAYS. The recommendation prices your actual usage, which is exactly why waste inside the lookback period gets priced into the commitment.
  • ✓After purchase, the truth: Cost Explorer → Savings Plans → utilization report, where the On-Demand spend equivalent and total net savings lines show what the commitment actually delivered against what the same usage would have cost at list price.

When 72 percent is genuinely on the table

The ceiling is real for someone. The stack it describes is specific: a fleet that will not leave one instance family in one region for three years, cash on hand for the full upfront payment, and the family-locked EC2 Instance Savings Plan product. Organisations with a stable, homogeneous fleet and a treasury function do get deep discounts. What they give up is flexibility, and what they carry is the risk: if the architecture moves to a different family or region, the commitment stays behind.

None of the fine print below makes the commitment a bad instrument. It makes the ceiling the wrong number to put in the box marked expected savings.

  • ✓Terms cannot be changed after purchase. The only exit is the return window: plans of $100 per hour or less, bought within the last seven days, in the same calendar month, subject to return limits.
  • ✓Amazon EKS control-plane charges are not covered, even when the underlying EC2 instances are.
  • ✓Dedicated Instance fees, $2 per hour per region, are not discounted.
  • ✓The Compute Savings Plan discount on Fargate covers vCPU and memory but not the OS licence fee.
  • ✓Savings Plans do not apply to spot usage, and SLES prices differ from the corresponding RI rates.

The order that survives contact with your bill

The sequence that keeps the commitment honest: rightsize first, because a recommendation built from existing usage will happily commit your waste for three years. AWS's own target coverage guidance says the quiet part: set coverage that leaves room to rightsize instances and clean up idle resources before committing further, then buy incrementally against the stable residue. Price the floor second, from your own rows, at the term and payment option you will actually accept. Commit third, at the flexible tier unless the fleet is genuinely family-stable, and let the utilization report grade the homework each quarter.

Upload your most recent AWS bill and we will read your Savings Plan rows the way this article does: which ceiling your plan type allows, what your instances are actually paying, and the gap between the two, before you sign the next commitment.

  1. For the instrument choice this article deliberately avoids: Savings Plans vs Reserved Instances, and what Reddit actually says about it.
  2. The EDP layer above Savings Plans, and the sequencing rule
  3. For the cleanup that must come before committing: the 30-day cost reduction guide

The short version

  • • There is no single maximum AWS Savings Plan discount: Compute Savings Plans cap at 66 percent, EC2 Instance Savings Plans at 72 percent, Database Savings Plans at 35 percent and SageMaker AI Savings Plans at 64 percent.
  • • The rate a specific instance gets is priced per usage type: m6a.large in N. Virginia saved 27 percent at 1 year no upfront, 49 percent at 3 years no upfront and 54 percent at the 3-year all-upfront maximum.
  • • AWS publishes its own estimate of typical on the Reserved Instances page: averages of 40 percent for a 1-year standard commitment and 60 percent for a 3-year.
  • • The 75 percent still quoted in decks is a retired number: AWS's RI page said up to 75 percent in December 2019 and says up to 72 percent today, and Savings Plans never had a 75.
  • • Price your floor before you commit: read your own rate row, clean the waste first, and commit only the stable residue, because Savings Plan terms cannot change after purchase.

Frequently Asked Questions

What is the maximum AWS Savings Plan discount?

It depends on the plan. EC2 Instance Savings Plans go up to 72 percent but lock the commitment to one instance family in one region. Compute Savings Plans, the flexible product that also covers Fargate and Lambda, cap at 66 percent. Database Savings Plans cap at 35 percent and SageMaker AI Savings Plans at 64 percent. The rate a specific instance receives depends on term, payment option, region, OS and tenancy, and comes from the rate table, not the headline.

Why is my Savings Plan discount lower than 72 percent?

Because the ceiling assumes the best case of the deepest product. On the day we read AWS's rate table, m6a.large in N. Virginia saved 27 percent on a 1-year no-upfront Compute Savings Plan, 49 percent at 3 years no upfront, and 54 percent at the 3-year all-upfront maximum. A model sized on 72 percent will overcommit unless your stack genuinely reaches it.

How much does m6a.large cost with a Savings Plan?

In US East (N. Virginia), Linux, shared tenancy, at the time of writing: $0.0864 per hour on demand, $0.06348 per hour (27 percent off) on a 1-year no-upfront Compute Savings Plan, $0.04382 (49 percent off) at 3 years no upfront, and $0.03976 (54 percent off) at 3 years all upfront. The family-locked EC2 Instance Savings Plan priced the same instance identically. Rates change, so read the current table before committing.

Can you cancel an AWS Savings Plan?

Not during the term: the commitment terms cannot be changed after purchase. The exception is the return window. Any Savings Plan with an hourly commitment of $100 or less, purchased in the last seven days and in the same calendar month, can be returned subject to return limits, with upfront charges refunded and covered usage rebilled at On-Demand rates.

HL

Hermann Lotter.FinOps practitioner who has led cloud and AI cost optimization inside a 180-person organisation, identifying six-figure annual savings across AWS and LLM spend. He writes Easy Entropy from hands-on engagements, not theory, and takes on scoped AWS FinOps consulting engagements.LinkedIn

Free Assessment

Want this outcome in your AWS bill?

Get a free cloud cost analysis and a prioritized optimization roadmap.

Request Free Analysis →

Topics covered

AWS Savings PlansSavings Plan DiscountCompute Savings PlansEC2 Instance Savings PlansAWS Cost OptimizationCommitment Discount

Related Articles