Up to 72% Cost Reduction with AWS Savings Plans - Choosing Between Compute and EC2 Instance Plans

Choosing between Compute plans and EC2 Instance plans achieves cost reductions of up to 72%. This article introduces Cost Explorer's recommendation feature and the monitoring of utilization / coverage.

About 7 min readLast updated: 2026-10-31

Overview of Savings Plans

Savings Plans is a pricing model in which you commit to an amount of compute usage per hour (USD/hour) and receive discounts of up to 72% off On-Demand prices. Like RI (Reserved Instances), it is a discount based on a commitment, and it offers more flexible commitments than RI. Compute Savings Plans applies across EC2, Fargate, and Lambda, and also accommodates changes in instance family and region.

How to Choose a Plan

Compute Savings Plans applies to usage of EC2, Fargate, and Lambda, and automatically follows changes in instance family, size, OS, and region. The discount rate is up to 66%. EC2 Instance Savings Plans is limited to a specific instance family and region, but the discount rate is higher, at up to 72%. For stable workloads, choosing EC2 Instance plans is a good fit, and for workloads with large fluctuations, choosing Compute plans is a good fit. With Cost Explorer's recommendation feature, you analyze usage patterns over the past 7/30/60 days and check the optimal commitment amount. There is an approach of starting with an amount somewhat lower than the recommended amount and making additional purchases in stages.

Purchasing Strategy and Analysis

When purchasing Savings Plans, you use Cost Explorer's recommendation feature to check the optimal commitment amount based on past usage patterns. There are three payment options, All Upfront, Partial Upfront, and No Upfront, and All Upfront offers the highest discount rate. There are 1-year and 3-year commitment terms, and although the 3-year term has a larger discount rate, you choose while taking into account the risk of workload fluctuations. There is a way of combining Compute Savings Plans and EC2 Instance Savings Plans, covering the stable baseline with EC2 Instance plans and the fluctuating portion with Compute plans. You regularly monitor Savings Plans utilization and coverage in Cost Explorer and evaluate whether the commitment is excessive or insufficient.

Monitoring Savings Plans

When Savings Plans utilization (the percentage of the purchased commitment that is actually used) is low, it indicates excessive commitment. When coverage (the percentage of On-Demand usage discounted by Savings Plans) is low, there is room for additional purchases. In Budgets, you set budgets for Savings Plans utilization and coverage and issue alerts when they fall below a threshold. When you share Savings Plans through consolidated billing in Organizations, discounts are applied automatically across member accounts, and coverage across the entire organization improves. You analyze usage patterns every quarter and carry out additional purchases and renewals of Savings Plans in a planned manner.

Purchase Costs of Savings Plans

The Savings Plans commitment amount is calculated with Cost Explorer's recommendation feature. The discount rate differs depending on the payment method: All Upfront / Partial Upfront / No Upfront. There are 1-year and 3-year commitment terms, and the 3-year term has a larger discount rate, but you choose while taking into account the risk of workload fluctuations. There is an approach of starting with an amount somewhat lower than the recommended amount and making additional purchases in stages while watching utilization. Because excessive commitment means the unused portion is wasted, careful estimation is important.

Differences from Reserved Instances

Commitment-based discounts include Savings Plans and Reserved Instances (RI). RI is a mechanism for receiving discounts tied to the attributes of a specific instance, and in some cases it also involves reserving capacity. Savings Plans, on the other hand, is a method of receiving discounts by committing to a certain amount of spending, and it is applied flexibly across instance types and regions. In environments with many configuration changes, the highly flexible Savings Plans is easy to work with, and if you fix a specific configuration and use it over the long term, RI is also an option. It is important to choose the appropriate discount method according to how stable your company's usage patterns are.

Commitment Terms and Payment Methods

With Savings Plans, you choose the commitment term and the payment method. The longer the term, the higher the discount rate, but that also means committing to a usage amount over a long period. For payment, the discount rate changes with the proportion paid upfront: All Upfront gives the largest discount, and the more the payment shifts to installments or deferred payment, the smaller the discount becomes. You choose by balancing the size of the discount against cash flow and the future outlook. The stronger the expectation that usage will continue stably, the more advantageous long-term / upfront terms are. Designing a manageable commitment, based on the business situation and the stability of usage, is the key to avoiding over-purchasing.

Centralized Management Across an Organization

In organizations that operate multiple accounts, Savings Plans discounts can be shared across the entire organization. Under consolidated billing, the discount from a plan purchased in one account is automatically applied to eligible usage in other accounts as well. This means you can cover usage across the entire organization together more efficiently than by purchasing separately for each account. If you manage purchasing centrally, you can decide the purchase amount while looking at overall usage, and you can reduce duplication. You monitor discount coverage and utilization at the organization level and carry out organization-wide purchases in a planned manner.

Summary

Savings Plans is a pricing model that provides discounts of up to 72% through a commitment to compute resource usage. Compute plans apply across EC2, Fargate, and Lambda, and EC2 Instance plans provide a higher discount rate with a fixed instance family. You regularly monitor utilization and coverage and carry out additional purchases in a planned manner through quarterly analysis of usage patterns.

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.

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.90% of AWS Is Born from Customer Feedback - Working Backwards and Customer-Driven InnovationWe explain how the Working Backwards process and the Customer Obsession principle shape AWS service development. Learn about the innovation mechanism that starts with PR/FAQ documents and the process for incorporating customer feedback.AWS's Culture of Price Reductions - The Flywheel and Economies of Scale Behind 100+ Price Cuts Since 2006This article analyzes AWS's culture of price reductions, which passes the benefits of scale on to customers, and the economies of scale, hardware generation transitions, and competitive strategy behind it. It also introduces major past price reductions and their impact.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.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.Cloud Cost Budget Management - Spending Control and Alerts with AWS BudgetsThis article explains budget settings / cost alerts / automated actions with AWS Budgets. It introduces how to choose between Budgets and Cost Explorer, how to select budget types, and organization-wide budget management through Organizations integration.Why CloudWatch Logs Costs More Than You Expect - The Cost Structure of Ingestion, Storage, and AnalysisThis article explains the pricing structure where CloudWatch Logs ingestion costs over 20 times more than storage, the cost explosions caused by VPC Flow Logs and Lambda logs, and optimization strategies using the Infrequent Access class and S3 export.Resource Optimization with AWS Compute Optimizer - Instance RightsizingAnalyzes CloudWatch metrics with ML and generates recommendations that optimize resource sizes for EC2 / Lambda / EBS / ECS Fargate. This article explains how to use Graviton migration recommendations and improve accuracy with enhanced metrics.