Savings Plans

What it is

Savings Plans give you lower prices than On-Demand in exchange for a commitment to spend a set amount per hour, such as $10 an hour, for a 1-year or 3-year term. You commit to dollars per hour, not to specific instances, so the discount follows your usage as you change instance types, sizes, RegionsAWS RegionA separate geographic area where AWS runs its services, such as us-east-1 in Northern Virginia, made up of several Availability Zones. Most resources live in one Region; you choose Regions for latency, data residency, and the services you need.Glossary entryClose, or even services.

Any usage above the commitment is charged at On-Demand rates. The commitment is charged every hour whether you use it or not, and it cannot be cancelled during the term. Savings Plans therefore suit steady, predictable usage, the baseline that runs all the time.

Plan types

Plan type	Applies to	Savings up to	Flexibility
Compute Savings Plans	EC2 instances, AWS Fargate (ECS and EKS), and AWS Lambda	66%	Any instance family, size, OS, tenancy, or Region, and across EC2, Fargate, and Lambda
EC2 Instance Savings Plans	EC2 instances of one instance family in one Region, such as m5 in us-east-1	72%	Any size, OS, or tenancy within that family and Region
Database Savings Plans	Aurora, RDS, DynamoDB, ElastiCache, DocumentDB, Neptune, Keyspaces, Timestream, DMS, and OpenSearch Service, including serverless usage	35%	Any engine, instance family, size, Availability ZoneAZ (Availability Zone)An isolated location within an AWS Region, made up of one or more data centers with their own power, cooling, and networking. The AZs in a Region are linked by fast, low-latency connections, so spreading resources across them protects against the failure of one site.Glossary entryClose, or Region (latest instance generations); 1-year term, no upfront only
SageMaker AI Savings Plans	SageMaker AI instances	64%	Any instance family, size, Region, or component, such as training or inference

Both compute plan types also cover EC2 instances that run in Amazon EMR, Amazon EKS, and Amazon ECS clusters. The EKS cluster fee itself is not covered.

The trade-off is simple: the more flexible the plan, the smaller the discount. Choose an EC2 Instance Savings Plan when you are sure of the instance family and Region; choose a Compute Savings Plan when you expect to change families, move Regions, or move to containers or Lambda.

Each plan type covers only its own services, so steady compute and steady databases need two plans: a Compute Savings Plan for EC2, Fargate, or Lambda plus a Database Savings Plan for Aurora, RDS, or DynamoDB. A Compute plan never covers database usage.

Terms and payment options

• Term: 1 year or 3 years. Longer terms give bigger discounts.
• Payment: All Upfront, Partial Upfront, or No Upfront. Paying more upfront gives a bigger discount.
• You can queue a purchase to start on a future date, for example when an existing plan or Reserved InstanceRI (Reserved Instance)A billing discount for committing to an instance type in a Region or Availability Zone for one or three years. It is not an instance: running instances that match are billed at the lower rate. AWS now recommends Savings Plans instead.Glossary entryClose expires.
• A plan with a commitment of $100 an hour or less can be returned within seven days of purchase, in the same calendar month, if you made a mistake.

How the discount is applied

1. Reserved Instances apply first.
2. EC2 Instance Savings Plans apply next, then Compute Savings Plans, because Compute plans are more widely applicable.
3. Within each hour, the commitment goes first to the usage with the highest savings percentage, until the commitment is used up. The rest is charged On-Demand.
4. Each hour's commitment can be used only in that hour; unused commitment is lost, not carried over.

Savings Plans do not apply to Spot Instances, and they do not reserve capacity. If you also need guaranteed capacity, combine a Savings Plan with an On-Demand Capacity Reservation; the Savings Plan rate applies to the reserved capacity.

Sharing across accounts

In AWS Organizations, a Savings Plan applies first to the account that bought it, and then, if discount sharing is turned on, to other accounts in the organization. The management account controls sharing in Billing preferences: for the whole organization, for groups of accounts defined with cost categories, or not at all for particular accounts. Many organizations buy plans centrally in one account and share them.

Security, resilience, performance, and cost

Security

• IAM controls who can view, purchase, and return Savings Plans; returning a plan requires the savingsplans:ReturnSavingsPlan permission.
• The management account decides which accounts share Savings Plans and Reserved Instance discounts.

Resilience and performance

• Savings Plans are a billing construct: they change the price, not the resources. They do not make workloads more available and do not guarantee capacity.

Cost

• Recommendations in the Billing and Cost Management console and Cost Explorer suggest an hourly commitment based on your past usage, with the estimated monthly savings. Purchase Analyzer estimates the effect of a purchase on cost, coverage, and utilization.
• Commit to your steady baseline, not your peak. A typical mix: a Savings Plan for the instances that run around the clock, On-Demand with Auto Scaling for short peaks, and Spot Instances for fault-tolerantFault toleranceThe ability of a system to keep working without interruption when a component fails, because enough redundant capacity is already running. It goes further than high availability, which may allow a short failover.Glossary entryClose work that can be interrupted, such as batch jobs.
• Watch two measures:
  • Utilization: how much of your commitment you actually use. Low utilization means you committed too much.
  • Coverage: how much of your eligible usage the plans cover. Low coverage means you could save more by committing more.

Monitoring

• Cost Explorer shows Savings Plans utilization and coverage reports.
• AWS Budgets can alert you when utilization or coverage falls below a target.
• The Cost and Usage Report has savingsPlan columns for detailed analysis.

Savings Plans or Reserved Instances?

	Compute Savings Plans	EC2 Instance Savings Plans	Convertible RIs	Standard RIs
Savings up to	66%	72%	66%	72%
Commitment	Dollars per hour	Dollars per hour	An instance configuration	An instance configuration
Any instance family	Yes	No	By manual exchange	No
Any Region	Yes	No	No	No
Fargate and Lambda	Yes	No	No	No
Capacity reservation	No	No	Only zonal RIs	Only zonal RIs

Standard RIs cannot be exchanged, but you can sell ones you no longer need on the Reserved Instance Marketplace. Convertible RIs can be exchanged during the term for another Convertible RI with a different instance family, type, platform, scope, or tenancy, but cannot be sold on the Marketplace.

Reserved Instances still matter for services that Savings Plans do not cover, and for zonal RIs, which reserve capacity in an Availability Zone. For EC2, AWS recommends Savings Plans for their flexibility.

Reverse mindmap: when the question points here

• Yes, when the question says
  • Steady compute usage, lowest cost, 1 or 3 years→ leads to Savings Plans
  • Flexible across instance families, Regions, Fargate, Lambda→ leads to Compute Savings Plan
  • Highest discount, one instance family in one Region→ leads to EC2 Instance Savings Plan
  • Steady RDS, Aurora, or DynamoDB usage→ leads to Database Savings Plan
  • Steady Lambda and Fargate plus steady Aurora→ leads to Compute Savings Plan plus Database Savings Plan
• Buy the right amount
  • How much to commit→ leads to Savings Plans recommendations
  • Commitment bought by mistake this week→ leads to Return it, $100 per hour or less
  • Start when current Reserved Instances expire→ leads to Queued purchase
  • Discount for all accounts in the organization→ leads to Discount sharing
• Keep it efficient
  • Paying for unused commitment→ leads to Low utilization; commit less next time
  • Much usage still On-Demand→ leads to Low coverage; commit more
  • Alert when utilization drops→ leads to Savings Plans utilization budget
• No, when the question says
  • Guaranteed capacity in an Availability Zone→ leads to On-Demand Capacity Reservation or zonal RI
  • Interruptible batch jobs at the lowest price→ leads to Spot Instances
  • Sell Reserved Instances you no longer need→ leads to Standard RIs on the Reserved Instance Marketplace
  • Change instance family during an RI term→ leads to Exchange Convertible RIs
  • Short or unpredictable workloads→ leads to On-Demand

Key takeaways

• Savings Plans trade a 1- or 3-year commitment in dollars per hour for discounts on steady usage.
• Compute (up to 66%) is the most flexible; EC2 Instance (up to 72%) gives the deepest EC2 discount for one family in one Region; Database (up to 35%) covers managed databases; SageMaker AI (up to 64%).
• Reserved Instances apply first, then EC2 Instance plans, then Compute plans; Spot is never covered.
• Savings Plans do not reserve capacity; add an On-Demand Capacity Reservation when you need it.
• Use recommendations to size the commitment, and watch utilization and coverage.

Sources

• Savings Plans User Guide: What are Savings Plans?
• Savings Plans User Guide: Savings Plans types
• Savings Plans User Guide: Compute Savings Plans and Reserved Instances
• Savings Plans User Guide: Understanding how Savings Plans apply to your usage
• Savings Plans User Guide: Understanding Savings Plans recommendations
• Savings Plans User Guide: Purchasing Savings Plans
• Savings Plans User Guide: Returning a purchased Savings Plan
• AWS Billing User Guide: Reserved Instances and Savings Plans discount sharing
• Amazon EC2 User Guide: Reserved Instances for Amazon EC2 overview
• Amazon EC2 User Guide: Types of Reserved Instances (offering classes)
• Amazon EC2 User Guide: Regional and zonal Reserved Instances (scope)
• Database Savings Plans
• Savings Plans FAQ