Stop Paying On-Demand Prices: Savings Plans, Reserved Instances and Spot Explained
Published by Rushikesh Dhule, LessBill · October 29, 2026 · Updated November 16, 2026
On-Demand pricing is the most expensive way to run anything in the cloud. It is built for flexibility: start a server, stop it, pay by the second. But most companies run the same core servers 24/7 for years, and still pay the flexible price.
AWS, Azure and Google Cloud all give big discounts if you commit to steady usage or run work that can be interrupted. Used well, they can cut compute costs by half or more. Used badly, they lock you into paying for things you don't need. Here is how to get it right.
The discount options at a glance
On AWS, these are the maximum discounts compared with On-Demand:
- Compute Savings Plans (up to 66% off): commit to a dollar amount per hour for 1 or 3 years. Applies to any EC2 instance family, size and region, plus Fargate and Lambda.
- EC2 Instance Savings Plans (up to 72% off): bigger discount, but locked to one instance family in one region.
- Standard Reserved Instances (up to 72% off): commit to a specific instance type. Also the main way to discount RDS, ElastiCache and OpenSearch.
- Convertible Reserved Instances (up to 66% off): like Standard, but you can exchange them for other types.
- Spot Instances (up to 90% off): spare capacity with no commitment, but AWS can take it back with a two-minute warning.
The biggest discounts need a 3-year term and full payment upfront. A 1-year term with no upfront payment saves less, but is much safer for a growing company.
1. Clean up before you commit
The worst mistake is committing to waste. If a server is oversized or idle, a discount just makes you pay less for something you shouldn't pay for at all, for one to three years.
Do this first: turn off idle resources, rightsize oversized instances, and schedule dev environments to stop at night. Then look at what's left.
2. Commit to your baseline, not your peak
Look at your hourly compute spend over the last 30 to 60 days and find the lowest level it rarely drops below. That is your baseline. Commit to that amount, or a little less, and let anything above it run On-Demand or Spot.
Example: your EC2 spend never drops below $8 an hour, even at night. A Savings Plan covering $6 to $8 an hour will be fully used every hour. A plan covering $12 an hour would waste money every quiet hour.
3. Start with Compute Savings Plans
For most small and mid-size teams, Compute Savings Plans are the safest first step. They apply automatically to whatever you run: change instance types, move regions, or shift workloads to Fargate or Lambda, and the discount follows.
Choose EC2 Instance Savings Plans or Standard Reserved Instances only for workloads you are confident will stay on the same instance family for the whole term, such as a database that won't change.
4. Use Spot for anything that can be interrupted
Spot can cut costs by up to 90%, but instances can be reclaimed at short notice. That makes it perfect for work that can restart:
- CI/CD build runners
- Batch jobs, data processing and rendering
- Stateless web or worker nodes in Kubernetes, mixed with On-Demand nodes
- Dev and test environments
Spread Spot across several instance types and availability zones so a single interruption doesn't take everything down.
5. Don't forget databases and other services
Compute Savings Plans don't cover RDS, ElastiCache, Redshift or OpenSearch. These often run 24/7 for years and are ideal for Reserved Instances. Check them separately, because they're easy to miss.
6. Track coverage and utilization every month
Two numbers tell you if your commitments are working:
- Coverage: how much of your eligible spend is discounted. Low coverage means you're still overpaying On-Demand.
- Utilization: how much of your commitment you actually use. Below 100% means you're paying for unused commitment.
Both are in AWS Cost Explorer under Savings Plans and Reservations. Review them monthly and add small commitments as your baseline grows, instead of one big purchase.
What about Azure and Google Cloud?
The same ideas apply:
- Azure: Reservations (for specific VM types and services) and the Azure Savings Plan for compute (flexible, like AWS Compute Savings Plans), plus Azure Spot VMs.
- Google Cloud: resource-based and spend-based Committed Use Discounts, automatic Sustained Use Discounts on some machine types, and Spot VMs.
Discount levels vary by service, term and region, so always check each provider's pricing page before buying.
The break-even rule for any commitment
A commitment bills you whether you use it or not. So the question is not "how big is the discount" but "how often will I actually use this capacity". The rule: a commitment with discount d breaks even when you use it (1 - d) of the time.
| Discount | Break-even usage | If you use it 60% of the time |
|---|---|---|
| 20% | 80% | You lose money |
| 30% | 70% | You lose money |
| 40% | 60% | Break even |
| 50% | 50% | You save |
Worked example: you commit to $1.00 an hour of Compute Savings Plan at a 30% discount. That costs $730 a month no matter what, and covers $1.00 / 0.70 = $1.43 an hour of On-Demand usage. If your usage stays at $1.43 an hour or more, you save $313 a month ($1,043 - $730). If it falls to $1.00 an hour of On-Demand usage, you save nothing. Below that, the plan costs more than having no plan.
That is why the advice above is to commit to your baseline. AWS advertises up to 66% off for Compute Savings Plans and up to 72% for EC2 Instance Savings Plans, and up to 90% off for Spot, but those are maximums. Get a recommendation based on your own last 30 days:
aws ce get-savings-plans-purchase-recommendation --savings-plans-type COMPUTE_SP --term-in-years ONE_YEAR --payment-option NO_UPFRONT --lookback-period-in-days THIRTY_DAYSRelated guides: Idle Dev and Staging Environments: Stop Paying for Empty Hours and Moving from x86 to Arm in the Cloud: A Step-by-Step Cost Guide.
Let LessBill find the waste first
The order matters: remove waste, then commit. LessBill connects to AWS, Azure and GCP with read-only access and finds idle and oversized resources across 60+ resource types, with an estimated monthly saving for each fix, so you only commit to what you really need. It's free during beta. Run your first scan.
Discounts are AWS's advertised maximums as of October 2026. Actual savings depend on term, payment option, instance type and region.


Comments
Post a Comment