Hi,
This detailled guide will help you understand: https://www.cloudzero.com/blog/savings-plans-vs-reserved-instances
In essence, Reserved Instances are based on the commitment to use an instance at a particular price over a specific period, while Savings Plans are based on the commitment to spend a particular dollar amount per hour over a specific period.
Best,
Didier Answer from Didier Durand on repost.aws
AWS
aws.amazon.com › what is cloud computing? › cloud comparisons hub › compute › what’s the difference between on-demand instances and reserved instances?
On-Demand Instances vs Reserved Instances - Instance Types Comparison - AWS
2 days ago - Reserved Instance pricing is not based on use. The price is fixed and locked in. On-Demand Instance pricing is based on use—projected for an equivalent three-year period. You can save more by choosing different payment plans and options within Reserved Instances.
AWS
docs.aws.amazon.com › savings plans › user guide › what are savings plans? › compute savings plans and reserved instances
Compute Savings Plans and Reserved Instances - Savings Plans
Compute Savings Plans are a flexible pricing model that offers low prices, just like Amazon EC2 Reserved Instances (RI), but with added flexibility. With Savings Plans, you can reduce your bill by committing to a consistent amount of compute usage (measured in $/hour), instead of specific instance ...
Difference between Savings Plans and Reserved Instance
Hi guys, I am researching the Amazon EC2 Pricing Models. I see the EC2 Savings Plans and Reserved Instance are quite similar. Do you know the difference between these two Pricing models. I think in... More on repost.aws
Reserved instance vs savings plan?
At the end of the day the actual rates themselves are exactly the same (EC2 savings plan vs. RI). So it's more a question of usage patterns and flexibility. Overall, savings plans are better because they offer more flexibility (though are a bit harder to calculate up-front). In my opinion I think RIs will be depreciated eventually because savings plans are superior in basically every way. RIs assume 24x7 usage and lock you into a specific machine for the term. With SPs you simply commit to a certain amount of spend per hour/month, and then however you use that is up to you. Hence you can have 1 machine on 24x7, or 24 machines on for 1 hour a day - that's up to you. You don't get that flexibility with RIs. Calculating a savings plan can be confusing at first bit it's not really that bad, you just have to change your unit from Total Instances (RIs) to Family Spend per hour per month (SPs). In short: Calculate the total hours you will need for each instance type (eg. M4, M5, M6g, etc) in a given month. This can be a combination of 24x7 instanced and on-demand. Knowing the total hours, calculate the total cost of each instance type, given the savings plan rate. Sum the total monthly spend for the entire family (eg. M4+M5+M6g, etc). Divide that total spend by 730 - this is your hourly spend rate which you will purchase your SPs with. Suppose you commit to $1/hr of M-family usage. Amazon will bill you $730 at the beginning of the month for your commitment. At that point, any usage of M-class machines is credited at the savings plan rate, up to $730. After you hit $730, you will be billed for normal on-demand rates. So really all you have to do is figure out how much you intent to spend in a month across a given family, divide by 730. More on reddit.com
RIs Vs Savings Plans
Ignore the other comment. Your best option here is a compute savings plan. It will cover EC2 and Fargate usage. A compute savings plan would get the same discount as a convertible RI, same for a standard RI and an EC2 instance savings plan. In terms of scaling, buy what you need now with a CSP, if you scale up and need more, just buy another one. But make sure the usage is going to be there for at least the amount of time to get to the breakeven point versus on demand. Hope this helps! More on reddit.com
Reserved Instances vs Cost Savings Plans for EC2
Convertible RIs end up being the same price as Compute Savings Plans, and standard RIs end up being the same price as EC2 Savings Plans. For me, Savings Plans have completely rendedered RIs obsolete, especially the CSP (as opposed to the EC2SP). No instance type or region restrictions -- just spin up your instances, change them, do whatever, and it will be billed at the lower rate. No need to "trade in" convertible instances, etc. For your use case where you know you will be within a single instance family in a single region, you may as well use the EC2SP. You just commit to $x/hr and it doesn't matter if you spin up 16 t3.small or 8 t3.medium or 1 t3.2xlarge... it will just be billed at the lower rate and you can change the instance type at will. More on reddit.com
What Is the Difference Between AWS Reserved Instance and Savings Plans?
The primary difference between AWS Reserved Instances and Savings Plans is the commitment to an hourly spend; Savings Plans require you to commit to an hourly spend, while Reserved Instances don’t.
cloudwards.net
cloudwards.net › cloud computing › cloud computing platforms › cloud computing platform comparisons
AWS Savings Plan vs Reserved Instances in 2025
Why Use AWS Reserved Instances?
Use AWS Reserved Instances for stable workloads on guaranteed compute at low rates.
cloudwards.net
cloudwards.net › cloud computing › cloud computing platforms › cloud computing platform comparisons
AWS Savings Plan vs Reserved Instances in 2025
What Are the 3 Types of Reserved Instances That Are Available From AWS?
The three types of AWS Reserved Instances are Standard, Convertible and Scheduled.
cloudwards.net
cloudwards.net › cloud computing › cloud computing platforms › cloud computing platform comparisons
AWS Savings Plan vs Reserved Instances in 2025
Videos
54:54
Savings Plans and Reserved Instances - What purchase strategy is ...
04:17
AWS Interview Question | Difference between Saving Plan and Reserved ...
07:02
AWS Savings Plans vs Reserved Instances - YouTube
38:04
Comparison of Amazon EC2 Reserved Instances vs. AWS Saving Plans ...
03:30
AWS Savings Plans Explained: Save Big Without Overcommitting - YouTube
Top answer 1 of 3
2
Hi,
This detailled guide will help you understand: https://www.cloudzero.com/blog/savings-plans-vs-reserved-instances
In essence, Reserved Instances are based on the commitment to use an instance at a particular price over a specific period, while Savings Plans are based on the commitment to spend a particular dollar amount per hour over a specific period.
Best,
Didier
2 of 3
1
Hi Steven,
It really depends on the resources you would like to cover, if you want to cover compute resources (EC2, Lambda, Sagemaker), I recommend SP as the pricing model is basically the same as RI, and it has more flexibility and you are commiting to the hourly cost, unless you have requirement to resell the Standard RI. Of course for other resources such as RDS, RedShift and OpenSearch (ElasticSearch) you can only purchase RI.
You can also get some insights from this YouTube video created by AWS: Savings Plans and Reserved Instances - What purchase strategy is right for you?
Hope it helps.
Amazon Web Services
aws.amazon.com › compute › savings plans › compute and ec2 instance
Compute and EC2 Instance Savings Plans
1 day ago - AWS offers two types of Savings Plans: ... Compute Savings Plans provide the most flexibility and help to reduce your costs by up to 66%. These plans automatically apply to EC2 instance usage regardless of instance family, size, AZ, Region, OS or tenancy, and also apply to Fargate or Lambda usage.
AWS Builder Center
builder.aws.com › content › 34hckD6jdObfp0MN45qM685iEoJ › a-comprehensive-cost-optimization-savings-plans-vs-reserved-instancesri
A comprehensive cost optimization savings plans vs ...
October 31, 2025 - Connect with builders who understand your journey. Share solutions, influence AWS product development, and access useful content that accelerates your growth. Your community starts here.
Yotascale
yotascale.com › blog › aws-reserved-instances-vs-savings-plans
Understanding AWS Savings Plans vs Reserved Instances in 2025 - Yotascale Blog
In short, Savings Plans deliver nearly all the cost benefits of RIs while removing the constraints that make RIs a challenge to manage effectively. Reserved Instances still exist for those who prefer instance-specific commitments, but they introduce several limitations:
Finout
finout.io › blog › aws-savings-plans-vs-reserved-instances-5-key-differences-in-2025
AWS Savings Plans vs Reserved Instances: 5 Key Differences in 2025
August 13, 2025 - The flexibility of Savings Plans makes them attractive for dynamic workloads where usage may fluctuate, as users can shift resources within families, sizes, and locations without losing the benefit of discounted pricing. AWS Reserved Instances (RIs) are a cost-saving model for Amazon EC2 where customers commit to using a specific instance type, size, and region for a one- or three-year period.
PTP
ptp.cloud › home › aws cost savings plans vs reserved instances explained
AWS Cost Savings Plans vs Reserved Instances Explained
March 26, 2021 - Compute Savings Plan: This plan offers flexibility similar to convertible RIs, allowing you to commit to a specific hourly compute usage rate at a discounted price. It applies automatically to EC2 instances, AWS Fargate, and Lambda usage, regardless of instance family, size, availability zone, or region. While both Reserved Instances and Savings Plans offer cost-saving opportunities, they have key differences and similarities:
AWS re:Post
repost.aws › knowledge-center › ec2-savings-plan-reserved-instances
Decide on Savings Plans or Reserved Instances for EC2 instances | AWS re:Post
June 2, 2025 - Savings Plans and Reserved Instances offer cost savings compared to On-Demand pricing. Typically, longer term commitment results in higher savings, such as a three-year term instead of a one-year term.
Economize
economize.cloud › blog › aws-savings-plan-vs-reserved-instances
AWS Savings Plan vs Reserved Instances: An Overview
AWS Savings Plan vs Reserved Instances: An Overview