| Savings Plans | Reserved Instances | |
|---|---|---|
| What you commit to | A dollar amount per hour (for example, $10/hour) | A specific instance type or database setup |
| Term | 1 or 3 years (Database Savings Plans: 1 year) | 1 or 3 years |
| Flexibility | Applies automatically as your usage changes | Tied to what you reserved |
| Covers containers and serverless | Yes, Compute Savings Plans cover Fargate and Lambda | No |
| Reserves capacity | No | Zonal Reserved Instances do |
| Best for | Most startups whose setup is still changing | Fixed, predictable workloads |
All Savings Plans figures in this post come from the AWS Savings Plans FAQ, checked November 16, 2026.
| Type | Maximum discount | Covers |
|---|---|---|
| Compute Savings Plans | Up to 66% | EC2, Fargate and Lambda, any instance family or region |
| EC2 Instance Savings Plans | Up to 72% | EC2, one instance family in one region |
| SageMaker Savings Plans | Up to 64% | SageMaker machine learning instances |
| Database Savings Plans | Up to 35% | Aurora, RDS, DynamoDB, ElastiCache, DocumentDB, Neptune, Keyspaces, Timestream, DMS and OpenSearch |
The “up to” figures are the maximums, usually for a three-year term paid upfront. One-year, no-upfront plans save less.
AWS now offers Savings Plans for databases. They cover newer (Generation 7 and later) database instances across services, instance types and regions. They come with a one-year term and no upfront payment. That makes them much easier to start with than database Reserved Instances, which lock you into one database setup.
One catch: you can’t combine Database Savings Plans with Reserved Instances on the same database workload. Use one or the other for each database.
This is where startups lose money. A commitment is charged whether you use it or not.
If you’re on AWS Activate credits, wait before buying. Credits already cover your bill, and a commitment made now may not match what you run when the credits end. Plan the purchase for the month before credits run out.
Infranexa manages cloud and DevOps for startups on AWS and Azure for a fixed monthly fee. Part of that is cost: we clean up waste first, size the right commitment from your actual usage, and review coverage every quarter as you grow, so you get the discount without paying for capacity you don’t use.
Book a free cloud assessment and we’ll tell you how much of your AWS bill could be covered by a Savings Plan.
For most startups, yes, because they’re more flexible and cover Fargate and Lambda. Reserved Instances are still useful when you need reserved capacity or for workloads that won’t change.
Compute Savings Plans cover EC2, Fargate and Lambda. EC2 Instance Savings Plans cover one EC2 instance family in one region. SageMaker Savings Plans cover SageMaker. Database Savings Plans cover Aurora, RDS, DynamoDB, ElastiCache, DocumentDB, Neptune, Keyspaces, Timestream, DMS and OpenSearch.
Generally no. A Savings Plan is a commitment for its full term, which is why it’s safest to commit only to usage you’re sure of.