Editorial photograph of a cloud FinOps team modeling AWS Savings Plans pricing scenarios across compute and SageMaker workloads
Article · AWS · SP Pricing 2026

Savings Plans pricing, 2026.

Compute SPs, EC2 Instance SPs, and SageMaker SPs each sit on a different rate curve. Term length and payment option move the discount inside the curve. The buyer side framework to model the price before committing.

Read the Framework AWS Hub
32 to 72%Savings Plan discount range
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

AWS Savings Plans price across three product lines. Compute SPs at up to 66 percent off. EC2 Instance SPs at up to 72 percent. SageMaker SPs at up to 64 percent on machine learning workloads. The buyer side framework models the price before committing.

This piece reads as a pricing reference. Use it with the Compute SP deep dive, the EC2 SP buyer guide, the EDP commitment calculator, and the AWS pillar hub.

Key Takeaways

What a FinOps lead needs to know in 90 seconds

  • Three Savings Plan families exist. Compute, EC2 Instance, SageMaker.
  • The discount range spans 32 to 72 percent. Term and payment option move the line.
  • Compute SP is the most flexible. Family, region, and compute service flex.
  • EC2 Instance SP carries the deepest discount. 72 percent ceiling at three year all upfront.
  • SageMaker SP is its own family. Covers SageMaker only, separate commit.
  • Pricing is hourly. Commit stated in USD per hour over one or three years.
  • The ladder beats the single buy. Quarterly tranches smooth the renewal cliff.

Why pricing matters

Savings Plan pricing is one of the largest cloud spend levers for any enterprise running production AWS workloads. A modest pricing miscalculation across a $30 million annual estate costs the business seven figures over a three year commit.

Three pricing dimensions worth attention

  • Term. One year versus three year.
  • Payment option. All upfront, partial upfront, no upfront.
  • Product line. Compute, EC2 Instance, SageMaker.
Editorial photograph of a CFO and FinOps team reviewing AWS Savings Plan pricing scenarios on a strategy whiteboard
Editorial reference. Savings Plan pricing scenarios mapped to trailing 18 month workload pattern.

Compute SP price curve

Compute Savings Plans price across all compute services. The discount applies to EC2, Fargate, and Lambda. The curve favors longer terms and larger up front commitments.

Compute SP discount by term and payment

TermNo upfrontPartial upfrontAll upfront
1 year27 to 31%29 to 33%32 to 36%
3 year50 to 54%55 to 60%62 to 66%

Why the partial upfront usually wins

The cash cost of all upfront is 100 percent of the term commit on day one. The partial upfront pays 50 percent. The discount gap between the two is usually three to five percentage points. The net present value math favors partial upfront on most enterprise estates.

EC2 Instance SP price curve

EC2 Instance Savings Plans match Standard Reserved Instance discount ceilings on EC2 only. The plan locks the instance family and the region in exchange for the deeper discount.

EC2 Instance SP discount by term and payment

TermNo upfrontPartial upfrontAll upfront
1 year32 to 36%35 to 39%38 to 42%
3 year55 to 60%62 to 67%67 to 72%

SageMaker SP price curve

SageMaker Savings Plans cover SageMaker workloads. The plan covers SageMaker training, inference, and notebook usage at a separate commit from the compute commits.

SageMaker SP discount by term and payment

TermNo upfrontPartial upfrontAll upfront
1 year20 to 24%22 to 26%25 to 29%
3 year45 to 50%52 to 58%58 to 64%

Term and payment combinations

The combination of term and payment option produces six price points per product line. The right choice depends on the cost of capital, the workload stability, and the cash flow profile.

Four pricing decision rules

  1. Three year all upfront for locked production. Deepest discount on stable workloads.
  2. Three year partial upfront for most estates. Best balance of discount and cash.
  3. One year ladder for variable estates. Quarterly tranches absorb workload swings.
  4. No upfront for cash constrained scenarios. Lower discount, no day one cash.

Discount benchmark by use case

The realized discount differs by workload pattern. Stable production stacks land in the upper band. Dynamic estates land in the lower band. The buyer side play is to match the SP type to the workload.

Six use cases and the right SP

  • Stable production EC2. EC2 Instance SP three year all upfront.
  • Dynamic compute. Compute SP three year partial upfront.
  • Fargate microservices. Compute SP one year laddered.
  • Lambda heavy workloads. Compute SP one year laddered.
  • SageMaker training. SageMaker SP three year partial upfront.
  • SageMaker inference. SageMaker SP one year laddered.

What to do next

The eight step checklist below moves an AWS estate from a default Savings Plan posture into a priced, laddered strategy. Open it at the next FinOps review.

  1. Pull 90 days of compute and SageMaker on demand spend. Net of current SPs.
  2. Score the stable floor. 60th to 80th percentile usage.
  3. Run the discount benchmark. All payment options across one and three year terms.
  4. Run the net present value math. All upfront versus partial upfront versus no upfront.
  5. Match the SP product to the workload. EC2 Instance versus Compute versus SageMaker.
  6. Build the ladder. Stagger one and three year commits across quarters.
  7. Document the allocation policy. Account, business unit, chargeback.
  8. Brief the finance team. Cash schedule, discount, and term horizon.

Frequently asked questions

What is the AWS Savings Plans 2026 discount range?

The range spans 32 to 72 percent across product lines and term combinations. Compute SP reaches 66 percent on a three year all upfront commit. EC2 Instance SP reaches 72 percent. SageMaker SP reaches 64 percent. Lower terms and no upfront payments reduce the discount.

Should we commit one year or three year?

Three year terms unlock the deepest discount tier. They also lock the workload for thirty six months. One year terms fit dynamic estates and laddered portfolios. Most enterprise estates run a mix, with three year commits on stable production and one year ladders on variable workloads.

All upfront, partial upfront, or no upfront?

All upfront earns the deepest discount but consumes cash on day one. Partial upfront pays half and earns a discount in the middle. No upfront pays month by month. On most estates with cost of capital between 7 and 11 percent, partial upfront wins on net present value math.

Are Savings Plan prices public?

The Savings Plan rate card is published on the AWS pricing pages. The customer can view the per service and per instance rate at any time. The actual discount applied to a workload depends on the SP product line, the term, the payment option, and the current on demand price.

Do Savings Plans cover databases?

No. Savings Plans cover compute services and SageMaker. They do not cover RDS, ElastiCache, Redshift, or OpenSearch. Reserved Instances cover those database services. Enterprises that converted compute coverage to Savings Plans should also buy the matching RI portfolio for the database tier.

How do Savings Plan prices interact with the EDP?

Savings Plan coverage applies before the EDP discount. The net usage after SP coverage is what counts toward the EDP commit and earns the EDP discount. Buyer side modeling treats the two layers together when sizing the EDP commit. The SP layer reduces the spend flowing into the EDP commit base.

How Redress engages on SP pricing

Redress runs the Savings Plan pricing review as part of the AWS FinOps and EDP renewal engagement. The work pulls the spend curve, models the ladder, and runs the net present value math on payment options. The deliverable is the optimized pricing stack and the residual commit map.

Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.

Score your AWS Savings Plan price stack in under five minutes.
Open the EDP Commitment Calculator →
White Paper · AWS

Download the AWS EDP Negotiation Guide.

A buyer side framework for the next AWS Enterprise Discount Program renewal. Commit sizing, discount tier benchmarks, flexibility clauses, Savings Plan layering, marketplace pass through.

Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for AWS customers running EDP, Private Pricing Agreements, and Savings Plan portfolios.

AWS EDP Negotiation Guide

Open the white paper in your browser. Corporate email only.

Open the Paper →
32 to 72%
SP discount range
3
SP product families
Hourly
Commit unit
500+
Enterprise clients
100%
Buyer side

We modeled six payment combinations across three product lines for an estate spending $48 million annually on AWS. The partial upfront three year commit landed 16 percentage points deeper than the existing portfolio and freed $7 million of cash on day one.

Chief Financial Officer
Global retail group
More Reading

More from this practice.

AWS Hub →
Compute SP Deep Dive
AWS · Article
Compute SP Deep Dive
Compute SPs decoded.
12 min read
EC2 SP Buyer Guide
AWS · Article
EC2 SP Buyer Guide
EC2 Instance SPs explained.
14 min read
Savings Plans vs Reserved Instances
AWS · Article
Savings Plans vs Reserved Instances
The decision framework.
12 min read
EDP vs Savings Plan
AWS · Article
EDP vs Savings Plan
Layered stack decoded.
14 min read
AWS Knowledge Hub
AWS · Hub
AWS Knowledge Hub
Full AWS research base.
10 min read
Editorial photograph of enterprise contract negotiation strategy

Your AWS price is your envelope.

We have run 500+ engagements across 11 publishers. Every engagement starts with one conversation.

AWS commercial intelligence, monthly.

Compute SP price movement, EC2 Instance SP benchmarks, SageMaker SP rates, EDP discount curves, marketplace pass through trends, and the wider AWS commercial leverage signals across every renewal cycle.