AWS First Steps
Management

AWS Savings Plans

A flexible cost reduction model that discounts EC2, Fargate, and Lambda pricing in exchange for a 1-year or 3-year usage commitment

About 6 min readWritten and edited by Awashiro

Overview

AWS Savings Plans is a pricing model that applies rates lower than on-demand in exchange for committing to a consistent amount of usage (measured in USD/hour) for a 1-year or 3-year term. Unlike Reserved Instances (RIs), Savings Plans flexibly accommodate changes in instance family, region, OS, and tenancy. As of September 2026, four types are available - Compute Savings Plans, EC2 Instance Savings Plans, SageMaker AI Savings Plans, and Database Savings Plans - with usage beyond the commitment amount charged at on-demand rates.

Savings Plans Types and Comparison with RIs

Compute Savings Plans are the most flexible type, applying to EC2, Fargate, and Lambda across the board. Discounts are maintained even when you change instance family, region, OS, or tenancy, making them ideal for environments where workload configurations change frequently. The discount rate is lower than that of EC2 Instance Savings Plans, but that is a reasonable trade-off for the flexibility. EC2 Instance Savings Plans lock in a region and instance family in exchange for a higher discount rate than Compute Savings Plans. Within the same family, you're free to change instance size (m5.large to m5.2xlarge), OS (Linux to Windows), and tenancy (shared to dedicated). They deliver the best cost efficiency when workloads are concentrated in a specific region and instance family. In addition, SageMaker AI Savings Plans apply to SageMaker AI instance usage, and Database Savings Plans apply to database services such as Aurora, RDS, and DynamoDB (as of September 2026). Compared to RIs, AWS documentation puts the maximum discounts of EC2 Instance Savings Plans and Standard RIs, and of Compute Savings Plans and Convertible RIs, at the same level, but RIs are tied to a specific instance configuration and are far less flexible to change. Convertible RIs do apply their discount to matching instances, but to change instance family, OS, or tenancy you must perform a manual exchange, whereas Savings Plans follow configuration changes automatically. For new purchases, using Savings Plans as the first choice and limiting RIs to maintaining existing contracts is easier to manage. The maximum discount rate for each type changes with AWS pricing revisions, so check the values for your target region and instance family on the official AWS pricing page before purchasing.

Calculating Commitment Amounts and Purchase Strategy

The most critical aspect of purchasing Savings Plans is calculating the right commitment amount. If the commitment is too high, unused portions are wasted; if too low, you're not maximizing discount benefits. Cost Explorer's Savings Plans recommendations analyze past usage patterns to suggest optimal commitment amounts. Even when following recommendations, compare the 7-day, 30-day, and 60-day recommendations to account for seasonal fluctuations and project changes. As a purchase strategy, starting below the recommended amount and adding more after a few months of actual data is the safest approach. Three payment options are available - all upfront, partial upfront, and no upfront (Database Savings Plans offer only a 1-year, no-upfront option) - with all upfront offering the highest discount. However, many organizations choose no upfront for cash flow reasons, accepting the difference in discount rate. Compute Savings Plans and EC2 Instance Savings Plans can be combined: a hybrid strategy that allocates EC2 Instance Savings Plans (higher discount) to the stable baseline and Compute Savings Plans (higher flexibility) to the variable portion delivers strong cost efficiency.

Monitoring Utilization and Contract Renewal Decisions

After purchasing Savings Plans, continuously monitor two key metrics: utilization and coverage. Utilization is the ratio of actual usage to the commitment amount - the closer to 100%, the less waste. If utilization stays at a low level, reduce the commitment amount at the next renewal. AWS does not define the level that counts as too low, so setting your own acceptable line and monitoring against it keeps the decision consistent. Coverage is the ratio of Savings Plans-covered usage to total on-demand usage - low coverage indicates room for additional purchases. The recommended setup is to configure Savings Plans utilization and coverage budgets in AWS Budgets, receiving alerts when they fall below thresholds. For contract renewal decisions, the choice between 1-year and 3-year terms is crucial. Three-year terms generally offer higher discounts than 1-year terms but require forecasting workloads three years out. If your architecture may change significantly during a cloud-native migration, repeating 1-year terms carries lower risk. Savings Plans do not renew automatically when they expire; to continue coverage without a gap, you queue a replacement purchase in advance. At renewal time, re-analyze usage patterns and purchase the optimal plan fresh.

References (Official AWS Resources)

The primary sources for this page are the official AWS website and documentation. Check the official pages below for the latest specifications and pricing.

If this page and the official documentation disagree, treat the official documentation as authoritative.

ShareXB!

Related Terms

AWS Cost ExplorerAWS BudgetsAmazon EC2AWS FargateAWS Lambda

Related Services

AWS Cost ExplorerAWS BudgetsAmazon EC2AWS Lambda

Related Articles

Why AWS Pricing Is So Complex - The Economics and Game Theory Behind Pay-As-You-GoWe break down the three-tier pricing structure of On-Demand, Reserved Instances, and Spot Instances through the lens of airline yield management and demand forecasting economics, explaining the rational reasons behind the complexity of AWS pricing.Inside AWS Pricing - How Per-Second, Per-Millisecond, and Per-Request Billing Actually WorksDiscover how AWS's diverse billing granularities, including EC2's per-second billing, Lambda's per-millisecond billing, and S3's per-request billing, are measured, aggregated, and invoiced through the metering system.Reading AWS's Next 3 Years from re:Invent Announcements - Service Lifecycles and the Rules of DeprecationFace the reality that AWS services have lifespans, examining cases like CodeCommit's enrollment freeze and SimpleDB's de facto end, and provide a technology selection perspective for identifying services that will endure.Origins and Naming Conventions of AWS Service Names - Why S3 Has Three S'sDig into the origins of major service names like S3, EC2, Lambda, and Aurora, exploring the hidden patterns in AWS naming conventions, naming missteps, and the history of rebranding.Cost Management with AWS Budgets - Budget Alerts and Automated ActionsSet alerts on both actual and forecasted values, and use Budget Actions to automatically apply IAM policies or stop instances. Integrate with Slack to raise cost awareness across the team.

Similar Terms and Articles

AWS Savings PlansA pricing model offering up to 72% discount on EC2, Lambda, and Fargate with a 1- or 3-year usage commitmentSave Up to 72% with AWS Savings Plans - Choosing Between Compute and EC2 Instance PlansLearn how to achieve up to 72% cost savings by choosing between Compute and EC2 Instance Savings Plans. This guide covers Cost Explorer recommendations and monitoring utilization and coverage.Cost Reduction Strategy - Comparing and Choosing Between Savings Plans and Reserved InstancesA detailed comparison of AWS Savings Plans and Reserved Instances (RI) covering mechanics, discount rates, and flexibility. Learn how to choose among Compute, EC2 Instance, and SageMaker Savings Plans and build an effective purchasing strategy.AWS Reserved Capacity Strategy Flexibility - How Savings Plans Cross-Service Coverage Changes Cost OptimizationAWS Savings Plans deliver cross-service discounts spanning EC2, Fargate, and Lambda, revolutionizing reserved capacity strategy. We analyze how to choose between Compute, EC2, and SageMaker Savings Plans, and compare the flexibility gap with Azure RI.Break-Even Analysis of Savings Plans vs Reserved Instances - Finding the Optimal Commitment Strategy with Real Pricing DataCompare discount rates, flexibility, and break-even points between Savings Plans and Reserved Instances using actual pricing data, and learn how to choose the optimal commitment strategy based on your workload characteristics.