/Glossary · Cost
What is Savings Plans?
Savings Plans are an AWS pricing model that offers lower rates in exchange for committing to a consistent hourly spend for one or three years. The discount applies automatically to eligible usage, without tying you to a specific instance.
How Savings Plans work
You commit to spending a dollar amount per hour, say ten dollars, for one or three years. All eligible usage up to that amount is billed at the discounted rate, and anything above it is billed at On-Demand prices. You can pay all upfront, partially upfront, or nothing upfront, and the discount grows the more you prepay and the longer the term.
Compute Savings Plans are the most flexible: they apply to EC2 across any family, size, and region, plus Fargate and Lambda. EC2 Instance Savings Plans give a bigger discount but are tied to one instance family in one region. There are also plans for SageMaker AI and for database services.
When to buy Savings Plans
They make sense when you have a stable, predictable compute baseline that will still be there for the full length of the commitment. Before buying, rightsize and clean up idle resources, because committing to wasted capacity only locks that waste in.
If your architecture is changing, for example moving from EC2 to containers or to Graviton, Compute Savings Plans protect you better than a plan tied to an instance family. For highly variable or short-lived workloads, Spot Instances or On-Demand pricing may be a better fit.
Best practices and common mistakes
Use Cost Explorer recommendations as a starting point and validate them against several weeks of data. Buy in stages, adding tranches every few months, instead of one large commitment. Track plan utilization and coverage in Cost Explorer and set up alerts in AWS Budgets.
Common mistakes: buying against peak usage instead of the steady baseline, committing for three years on an architecture that is about to change, and not revisiting coverage after a migration. Another is forgetting that a plan applies first to the usage with the highest available discount, which can muddy per-team analysis.
/FAQ
Questions about Savings Plans
Another question? Write to hello@nubent.com and an engineer will answer.
What is the difference between Savings Plans and Reserved Instances?
Reserved Instances are bought for a specific instance type or service. Savings Plans commit to an hourly spend and apply the discount flexibly to eligible usage. For compute, AWS recommends Savings Plans for their flexibility, although reservations still exist for services like RDS.
Can you cancel a Savings Plan?
Generally, no: it is a commitment for the full term. AWS lets you return a recently purchased plan within a short window and under limited conditions. That is why it pays to buy in stages and against a usage baseline you are confident you will keep.
Do Savings Plans apply to Fargate and Lambda?
Yes. Compute Savings Plans apply to EC2, AWS Fargate, and AWS Lambda. That makes them a strong fit for organizations that mix servers, containers, and serverless functions, or that plan to move between those models during the commitment term.
How we help with Savings Plans
FinOps and cost optimization
AWS cost optimization: spend visibility, rightsizing, Savings Plans, removal of idle resources and FinOps practices that keep the results in place.
Learn moreWell-Architected Review
A review of your workloads across the 6 AWS Well-Architected pillars, with Generative AI and SaaS lenses and a remediation plan you can actually execute.
Learn moreNext step
What should we build next on AWS?
30 minutes with an engineer. Concrete next steps, whether or not you work with us.