- Newest
- Most votes
- Most comments
Your summary of the differences between EC2 Savings Plans and Reserved Instances is generally accurate, but let me provide a more comprehensive comparison:
- EC2 Savings Plans:
A) Compute Savings Plans:
- Offer the most flexibility
- Provide savings up to 66% off On-Demand pricing
- Require a commitment to a consistent amount of compute usage ($/hour) for 1 or 3 years
- Apply across EC2 instance families, sizes, AZs, Regions, OS, and tenancy
- Also apply to Fargate and Lambda usage
B) EC2 Instance Savings Plans:
- Offer savings up to 72% off On-Demand pricing
- Require commitment to a specific EC2 instance family in a chosen Region
- Provide flexibility in instance size, OS, and tenancy within the chosen family and Region
- Reserved Instances (RIs):
- Offer up to 72% discount compared to On-Demand pricing
- Require commitment to a specific instance configuration (family, size, Region, OS, and tenancy)
- Come in two types: Standard (less flexible, higher discount) and Convertible (more flexible, lower discount)
- Provide capacity reservation in a specific Availability Zone (if specified)
Key differences:
- Flexibility: Compute Savings Plans are the most flexible, followed by EC2 Instance Savings Plans, then Convertible RIs, and finally Standard RIs.
- Scope: Compute Savings Plans can apply to EC2, Fargate, and Lambda, while RIs and EC2 Instance Savings Plans only apply to EC2.
- Commitment: Savings Plans require a commitment to a consistent usage amount ($/hour), while RIs require commitment to specific instance attributes.
- Capacity Reservation: Only RIs offer the option for capacity reservation in a specific Availability Zone.
It's worth noting that AWS now recommends Savings Plans over Reserved Instances for most use cases due to their greater flexibility and ease of use.
Sources
Compute Savings Plans and Reserved Instances - Savings Plans
Reserved Instances for Amazon EC2 overview - Amazon Elastic Compute Cloud
Reserved Instances - Amazon EC2 Reserved Instances - AWS
It's all depending on your use case and how you plan to achieve your goals. As these Savings options provide you the discounts, it's up to how you utilize them based on your infra/workload setup and goals that you have. For example, if you have limited workloads that are very business critical with less changes on the setup in coming year either 1 year or 3 year and you have a goal to optimize cost, then you choose maximum savings option which gives bigger discount based on your commitment.
If you have a workloads which is managed by multiple business units scattered across regions and have plans to optimize or modernize in coming months then choosing SP's over RI would give better flexibility. At the end of the day, it's all up to your use case and your goals.
Remember Compute Savings plan not only covers EC2, but also covers Fargate & Lambda.
Thank you Anil for you reply and insight. Our servers work load is 'light' and remain some what consistent. They process basic json data for our app on iPhone and Android and some basic html reporting tables for our web pages. We've never needed to touch the EC2 instances after creating them or move them to another region. We're going to go with Reserved Instances or EC2 Instance Savings Plans. Best Regards, Donald
Relevant content
- asked a year ago
- asked 3 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
Whats your use case for one of these? Y
Hi Gary, Our use case is application development and production instances. Our servers work load is 'light' and remain some what consistent. They process basic json data for our app on iPhone and Android and some basic html reporting tables for our web pages/servers. We've never needed to touch the EC2 instances after creating them or move them to another region. We're going to go with Reserved Instances or EC2 Instance Savings Plans. Best Regards, Donald