- The Commitment Contract Model: Reserved Instances (RIs) require committing to specific instance types and operating systems. Savings Plans shift the contract to an hourly dollar spend commitment (e.g. $100/hr of compute), automatically applying discounts to eligible EC2, Fargate, and Lambda workloads.
- Discount Variance: Standard RIs and EC2 Instance Savings Plans offer the deepest discounts (up to 72% off on-demand pricing for 3-year all-upfront), but completely lock you to a single instance family in a specific region. Compute Savings Plans offer up to 66% discounts with universal flexibility across instance types, operating systems, and serverless containers.
- The Secondary Marketplace Advantage: Standard Reserved Instances are the ONLY commitment vehicle that can be legally resold on the AWS RI Marketplace if you downsize or repatriate workloads. Savings Plans are strictly non-refundable and cannot be transferred or sold.
- Financial Optimization Links: Cross-link with our AWS Enterprise Discount Program (EDP) audit framework and our Datadog custom metric cost optimization guide.
For organizations spending more than $20,000 monthly on Amazon Web Services, paying unhedged On-Demand rates for compute infrastructure is pure financial malpractice. AWS offers substantial discounts—ranging from 20% to 72%—in exchange for long-term contract commitments.
However, navigating the commitment matrix between Compute Savings Plans, EC2 Instance Savings Plans, and legacy Reserved Instances (Standard vs. Convertible) represents a perilous FinOps minefield. Choosing the wrong vehicle can permanently lock your budget into obsolete CPU architectures or prevent you from repatriating workloads.
Savings Plans vs. Reserved Instances: What Is the Difference?
Savings Plans commit to a dollar-per-hour spend and automatically apply discounts across changing instance families, regions, and serverless compute (Fargate/Lambda). Reserved Instances commit to specific server configurations, offering slightly higher discounts and access to the secondary RI resale marketplace.
Understanding the tradeoffs between discount depth and architectural flexibility is essential before signing multi-year agreements.
AWS Compute Commitment Matrix
The following engineering table outlines the differences across the four primary AWS compute discount mechanisms:
| Commitment Type | Max Discount (3-Yr All Upfront) | Eligible Services | Flexibility Across Families / Regions | Resale Marketplace Access |
|---|---|---|---|---|
| Compute Savings Plan | Up to 66% | EC2, AWS Fargate, AWS Lambda | 100% universal (any family, OS, or region) | No (Zero resale option) |
| EC2 Instance Savings Plan | Up to 72% | EC2 instances only | Single family in one region (e.g. m6i in us-east-1) | No (Zero resale option) |
| Standard Reserved Instance | Up to 72% | EC2, RDS, ElastiCache, Redshift | Locked to instance family and region | Yes (Can sell unused RIs on Marketplace) |
| Convertible Reserved Instance | Up to 54% | EC2 instances only | Exchangeable for higher-value instances | No (Zero resale option) |
The Cloud Repatriation Trap of 3-Year Savings Plans
One of the most dangerous errors engineering leaders make is purchasing 3-year All-Upfront Savings Plans to demonstrate quick quarterly cost cuts to executive boards. While a 66% headline discount looks compelling in slide decks, it creates an unyielding lock-in barrier.
If your engineering team determines that migrating database workloads to dedicated bare-metal infrastructure would save $300,000 annually, you cannot execute that repatriation without writing off the remaining amortized balance of your Savings Plan. Because Savings Plans cannot be sold on the secondary market, commit to 1-year terms or retain standard RIs for workloads targeted for repatriation.
The 70/20/10 Tiered Hedging Strategy
World-class FinOps teams manage cloud commitments like an institutional investment portfolio:
- 70% Baseline Hedged with Compute Savings Plans: Cover immutable core workloads with 1-year No-Upfront Compute Savings Plans, giving developers freedom to upgrade from x86 to Graviton processors or migrate from EC2 to Fargate without penalty.
- 20% Covered by Standard RIs for Database Services: Use Standard RIs for stable Amazon RDS (PostgreSQL/MySQL) or OpenSearch instances that require dedicated hardware and can be resold if modified.
- 10% On-Demand / Spot Elasticity: Leave variable burst traffic, ephemeral CI/CD pipelines, and experimental environments on uncommitted On-Demand or Spot instances.
Never sign a 3-year commitment on EC2-specific Savings Plans; hardware generations evolve too rapidly, and instance family lock-in prevents migrating to Graviton4 or bare metal. Standardize on 1-Year Compute Savings Plans (No Upfront) for 70% of your minimum baseline compute to balance significant savings (up to 44%) with architectural agility.