AWS Practice
AWS EC2 Instance Savings Plans. The Buyer Guide.
EC2 Instance Savings Plans give the deepest compute rate, but they lock the family and region. Read the trade against Compute plans and Reserved Instances first.
EC2 Instance Savings Plans give the deepest compute rate, but they lock the family and region. Read the trade against Compute plans and Reserved Instances first.
AWS EC2 Instance Savings Plans deliver the deepest compute discount, but the family and region lock means the rate only pays off on workloads that genuinely will not move.
An EC2 Instance Savings Plan commits you to a steady hourly spend on a particular instance family within one region, for a one or three year term. In exchange you get the deepest Savings Plan rate available. The plan is documented on the AWS compute Savings Plans pricing page.
The rate beats the flexible Compute plan, but the discount only applies inside the chosen family and region. Move the workload and the commitment can sit idle.
The family and region are fixed for the term. Instance size is not, so you keep size flexibility within the family. The mechanics are set out in the Savings Plans user guide.
As with all Savings Plans, three year all upfront gives the deepest rate. The general pricing model is on the EC2 pricing page.
EC2 Instance Savings Plan lock and flexibility
| Attribute | Status | Effect | Buyer action |
|---|---|---|---|
| Instance family | Locked | Deepest rate within family | Pick stable families only |
| Region | Locked | No discount if workload moves | Confirm region permanence |
| Instance size | Flexible | Move sizes freely | Right size without penalty |
| Operating system | Flexible | Covers OS changes | No action needed |
The three tools overlap but solve different problems. Compute Savings Plans trade rate for flexibility. EC2 Instance plans trade flexibility for rate. Reserved Instances add a capacity reservation.
Choosing wrongly is the most common and expensive mistake, because each tool is right only for a specific workload profile.
Reserved Instances can guarantee capacity in a specific Availability Zone, which Savings Plans do not. Where a capacity reservation matters, the Reserved Instances model is still the right tool.
The lock is only a risk if the workload moves. The discipline is to apply EC2 Instance plans only to workloads with a confirmed, stable family and region for the full term.
The standard advice is to always choose the EC2 Instance plan over the Compute plan because it gives a deeper discount. We disagree. In roughly two thirds of the estates we reviewed in 2024 and 2025, the deeper rate was applied to workloads that later changed family or moved region, stranding 15 to 25 percent of the commitment. The flexible Compute plan would have kept the discount through the change. The buyer side move is to reserve EC2 Instance plans for workloads with confirmed family and region permanence, and default everything migrating or uncertain to Compute plans. The deeper rate is only deeper if the commitment is actually used.
Source: Redress Compliance advisory engagement file, 2024 to 2025.
On EC2 compute the deepest rate only beats the flexible one if the workload never moves. Lock the rate to permanence, not to optimism.
The work is workload classification. Bring a stability and roadmap view of each workload, family by family. The lever is matching the tool to the profile.
Tag each workload by family, region, and roadmap. Anything with a planned migration goes on Compute plans; only confirmed stable workloads take the EC2 Instance rate.
White Paper · AWS
AWS Savings Plans Top 10 Negotiation Recommendations
Ten moves every cloud owner and CPO should make before committing to AWS Compute or EC2 Savings Plans: term, coverage, and exit math. Read it free.
An EC2 Instance Savings Plan commits you to a steady hourly spend on a specific instance family within one region for one or three years, in exchange for the deepest Savings Plan rate. The discount only applies inside the locked family and region, so the rate pays off only on workloads that stay put.
It locks the instance family and the region for the full term. Instance size and operating system remain flexible, so you can right size within the family without losing the rate, but commitment outside the locked family or region earns no discount.
No. The deeper rate only beats the flexible Compute plan if the workload stays on the same family and region for the term. Applying it to workloads that later migrate strands the commitment, so it should be reserved for workloads with confirmed permanence.
EC2 Instance plans discount more deeply but lock the family and region, while Compute plans cover any family, region, and services like Fargate and Lambda at a shallower rate. Use EC2 Instance plans for stable known workloads and Compute plans for anything migrating or uncertain.
Reserved Instances are the right tool when you need a capacity reservation in a specific Availability Zone, which Savings Plans do not provide. If the workload only needs a rate discount rather than guaranteed capacity, a Savings Plan is usually the better fit.
Yes. Instance size is flexible within the locked family, so you can move between sizes and right size workloads without losing the discount. Only the family and region are fixed for the term.
In our 2024 to 2025 reviews, 15 to 25 percent of EC2 Instance commitment was tied to families or regions the estate later moved off, leaving it idle. Classifying workloads by permanence before committing removes most of that waste.
Classify each workload by family, region, and roadmap. Apply EC2 Instance plans only to workloads with confirmed permanence for the term, default migrating or uncertain workloads to Compute plans, and use Reserved Instances where a capacity guarantee is required.
Family and region lock, the Reserved Instance comparison, coverage targets, and the levers that capture the deeper rate without stranding commitment.
Used across more than five hundred enterprise engagements. Independent. Buyer side. Built for procurement leaders running the next renewal cycle.
