Editorial photograph of an enterprise FinOps team comparing AWS Savings Plans against Reserved Instances on a boardroom screen
Article · AWS · SP versus RI

Savings Plans versus Reserved Instances.

AWS sells two compute commitment vehicles. Reserved Instances cover EC2, RDS, ElastiCache, OpenSearch, and Redshift. Savings Plans cover EC2, Fargate, Lambda, and SageMaker. The right buyer side mix is laddered, not exclusive.

Read the Framework AWS Hub
72%Max RI discount on 3 year
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Reserved Instances and Savings Plans both trade a commitment for a discount. RIs cover compute, RDS, ElastiCache, OpenSearch, and Redshift. Savings Plans cover compute, Fargate, Lambda, and SageMaker. Each behaves differently inside the AWS billing engine.

This piece reads as a buyer side decision framework. Use it with the Compute Savings Plans deep dive, the EDP commitment calculator, the RI cost analysis piece, and the AWS pillar hub.

Key Takeaways

What a Cloud FinOps lead needs to know in 90 seconds

  • Reserved Instances cover database services. Savings Plans do not cover RDS, ElastiCache, Redshift, or OpenSearch.
  • Savings Plans cover Fargate and Lambda. RIs do not.
  • Standard RIs reach 72 percent discount. Compute Savings Plans top at 66 percent.
  • Convertible RIs allow family changes. Standard RIs do not.
  • Savings Plans behave automatically. Coverage flows to the highest discount line.
  • RIs can be sold on the AWS Marketplace. Savings Plans cannot.
  • The buyer side play is hybrid. RIs on database stacks, Savings Plans on compute.

Why both vehicles exist

Reserved Instances are the legacy commitment model. AWS introduced Savings Plans in 2019 to simplify the family and region lock. The two vehicles now coexist because each covers a different part of the catalog.

Three reasons both still matter

  • Database coverage. RIs are the only commitment for RDS, ElastiCache, OpenSearch, and Redshift.
  • Standard RI discount ceiling. 72 percent on three year all upfront for locked production estates.
  • Modern compute estates. Savings Plans handle EC2, Fargate, and Lambda in one vehicle.
Editorial photograph of an AWS FinOps team building a hybrid Savings Plan and Reserved Instance coverage map
Editorial reference. Hybrid compute and database commitment coverage view across the AWS estate.

Coverage scope side by side

The coverage map decides which vehicle fits the workload. The map is service driven, not workload driven. Treat the table below as the first cut for any commitment review.

Savings Plan and RI coverage by service

ServiceReserved InstanceSavings Plan
EC2YesYes (Compute and EC2 Instance SP)
FargateNoYes (Compute SP)
LambdaNoYes (Compute SP)
SageMakerNoYes (SageMaker SP)
RDSYesNo
ElastiCacheYesNo
RedshiftYesNo
OpenSearchYesNo

The coverage gap to watch

Many enterprise teams discover the database coverage gap after they convert their compute estate to Savings Plans. RDS, ElastiCache, Redshift, and OpenSearch keep running at on demand rates until the team buys the matching RIs. The fix is to baseline the database spend and buy the RI portfolio at the same time as the Savings Plan ladder.

Discount math compared

The headline discount ceilings differ. The realized discount also differs because the family flex of Savings Plans usually keeps coverage at 80 to 95 percent across the term, while locked Standard RIs sometimes drop to 60 to 75 percent.

Discount ceiling by vehicle

Vehicle1 year3 year
Standard RI all upfront40%72%
Convertible RI all upfront34%66%
EC2 Instance Savings Plan all upfront42%72%
Compute Savings Plan all upfront36%66%
RDS RI all upfront40%69%
ElastiCache RI all upfront35%55%

Flexibility and modification

The flexibility profile separates the two vehicles further. Standard RIs are locked. Convertible RIs allow family swaps. Savings Plans behave like a hourly commit that AWS allocates automatically.

Six flexibility dimensions compared

  • Instance family change. Standard RI no. Convertible RI yes. Compute SP yes.
  • Region change. Standard RI no. Convertible RI no. Compute SP yes.
  • Size flex. All three flex within size inside the same family.
  • Modify after purchase. Standard RI limited. Convertible RI yes. SP implicit through allocation.
  • Sell on Marketplace. Standard RI yes. Convertible RI no. SP no.
  • Auto coverage allocation. SP yes. RI manual through tenancy.

When to use each

Each vehicle wins on a different workload type. Match the workload to the vehicle and avoid mixing the two on the same line. The decision is service first, workload second.

Five workload patterns and the right vehicle

  1. Locked production EC2 on c7i family. EC2 Instance SP three year all upfront.
  2. Dynamic compute across c, m, r families. Compute SP three year partial upfront.
  3. Fargate microservices estate. Compute SP one year ladder.
  4. RDS Postgres production cluster. Standard RI three year partial upfront.
  5. ElastiCache Redis on cm6 nodes. Standard RI one year partial upfront.

Hybrid coverage strategy

The buyer side play is hybrid coverage. RIs cover the database services. Savings Plans cover the compute. The two layers behave independently inside the AWS billing engine.

Hybrid layered allocation pattern

LayerVehicleTarget coverage
EC2 locked stackEC2 Instance SP60 to 80 percent
EC2 dynamic stackCompute SP40 to 60 percent
Fargate and LambdaCompute SP50 to 80 percent
RDS stable clustersStandard RI70 to 90 percent
ElastiCache stable nodesStandard RI70 to 85 percent
Redshift productionStandard RI80 to 95 percent

What to do next

The eight step checklist below moves an AWS estate from a single vehicle posture into a layered, hybrid coverage plan. Open it at the next FinOps review.

  1. Pull 90 days of spend by service. EC2, Fargate, Lambda, RDS, ElastiCache, Redshift, OpenSearch.
  2. Map current RI and SP coverage. By expiry date and commit value.
  3. Score the stable floor on each service. 60th to 80th percentile.
  4. Buy RIs for the database services. RDS, ElastiCache, Redshift, OpenSearch.
  5. Ladder Savings Plans across compute. Mix one and three year, mix family lock and flex.
  6. Run the net present value math. All upfront versus partial versus no upfront.
  7. Document the allocation policy. Account, business unit, chargeback.
  8. Brief the finance team. Cash, discount, ladder schedule.

Frequently asked questions

Do Savings Plans cover RDS and ElastiCache?

No. Savings Plans cover EC2, Fargate, Lambda, and SageMaker. RDS, ElastiCache, Redshift, and OpenSearch are only covered by Reserved Instances. Enterprise estates that converted compute coverage to Savings Plans often discover the database coverage gap on the next monthly bill. The fix is to buy the matching RI portfolio at the same time as the Savings Plan ladder.

Can we sell Savings Plans on the AWS Marketplace?

No. Savings Plans are not resellable on the AWS Marketplace. Standard Reserved Instances can be sold to other AWS customers through the Reserved Instance Marketplace. Convertible Reserved Instances and Savings Plans cannot. The marketplace resale value of Standard RIs is sometimes a relevant lever on locked production stacks where the workload pattern is uncertain.

Which carries the higher discount, RI or SP?

Standard Reserved Instances reach 72 percent discount on a three year all upfront commitment. EC2 Instance Savings Plans match that ceiling on the same term. Compute Savings Plans top at 66 percent because of the family and region flexibility. The realized discount depends on the workload pattern, the family lock, and the term length.

Can we modify a Savings Plan after purchase?

No. Savings Plans are immutable. The plan covers an hourly USD spend rate for the term. AWS allocates the coverage automatically to the lines with the deepest discount. Customers cannot exchange a Savings Plan for a different one. The flexibility sits in the allocation engine, not in the commitment itself.

What is the difference between Convertible and Standard RIs?

Standard RIs lock the instance family. Convertible RIs let the customer exchange the RI for a different family, size, or operating system inside the term. Standard RIs earn a higher discount ceiling. Convertible RIs trade discount for flexibility.

How do RIs and SPs interact with the EDP?

Both vehicles apply before the EDP discount. The EDP applies to net usage after Reserved Instance and Savings Plan coverage. Model the three layers together when sizing the EDP commit. SP and RI coverage reduce the spend that counts toward the EDP tier.

How Redress engages on commitment vehicles

Redress runs the commitment review as part of the AWS FinOps and EDP renewal engagement. The work pulls the spend curve across compute and database services, models the layered allocation, and runs the net present value math. The deliverable is the hybrid coverage strategy 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 commitment portfolio 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 and Reserved Instance 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 hybrid commitment portfolios.

AWS EDP Negotiation Guide

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

Open the Paper →
72%
Max RI discount
66%
Max Compute SP discount
3 year
Longest term
500+
Enterprise clients
100%
Buyer side

We layered Standard RIs on RDS and Redshift and Compute Savings Plans on EC2 and Fargate. The hybrid coverage strategy cut the on demand bill by 32 percent and removed the renewal cliff we had been carrying since the last all in commit on a single vehicle.

Director of Cloud FinOps
Global retail group
More Reading

More from this practice.

AWS Hub →
Compute SP Deep Dive
AWS · Article
Compute SP Deep Dive
Compute SP decoded.
12 min read
EC2 RI Cost Analysis
AWS · Article
EC2 RI Cost Analysis
RI cost analysis.
14 min read
AWS EDP Negotiation Guide
AWS · Landing
AWS EDP Negotiation Guide
The full negotiation playbook.
18 min read
AWS EDP Discount Benchmarks
AWS · Article
AWS EDP Discount Benchmarks
Discount benchmarks by tier.
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 commit is your envelope.

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

AWS commercial intelligence, monthly.

Compute SP versus RI benchmarks, layered coverage patterns, EDP discount curves, database RI movement, marketplace pass through, and the wider AWS commercial leverage signals across every renewal cycle.