Skip to content
FinOps workspace
COST LEDGER / DECISION GUIDE

AWS reserved instances: vs Savings Plans: decide before committing

Updated: 6 November 2026Get a quote for my project

AWS Reserved Instances and AWS Savings Plans exchange a commitment for eligible discounted usage. Compare their coverage rules and the demand remaining after rightsizing before deciding how much to commit.

Illustrative server rack in the foreground with a row of cabinets behind it
Illustration : cloud infrastructure.
On this page
  1. Commitment types and what each one attaches to
  2. Coverage rules that surprise buyers
  3. A buying sequence that limits regret
  4. The return window is short and calendar-bound
  5. Who should hold purchase rights
  6. Official sources used
  7. Frequently asked questions

AWS Reserved Instances: compare coverage before purchasing

An AWS Savings Plans vs Reserved Instances decision should use the same remaining workload baseline. Review EC2 pricing and operating hours and RDS workload costs separately. Eligible service coverage differs between instruments, so a discount description cannot be applied to every line of the account bill.

Commitment types and what each one attaches to

AWS documents four Savings Plans types. Each commits you to an amount of spend per hour. Compute, EC2 Instance and SageMaker AI plans run for one or three years and can be paid All upfront, Partial upfront or No upfront. Database Savings Plans, announced in December 2025, offer a single option: one year with no upfront payment. Reserved Instances, by contrast, commit you to an instance configuration.

InstrumentAttaches toFlexibility
Compute Savings PlansEC2 instance usage, plus Fargate and LambdaAny instance family, size, Region, OS and tenancy
EC2 Instance Savings PlansOne instance family in one RegionSize, OS and tenancy within that family
SageMaker AI Savings PlansSageMaker AI instance usageFamily, size, Region and component
Database Savings PlansAurora, RDS, DynamoDB, ElastiCache, DocumentDB, Timestream, Neptune, Keyspaces, DMS and OpenSearch ServiceEngine, family, size, Availability Zone and Region for eligible latest-generation provisioned instances and supported serverless usage; check the service-specific coverage
Reserved InstancesA specific configuration, Standard or ConvertibleConvertible RIs can be changed by a manual exchange; regional EC2 RIs provide size flexibility only for Linux/Unix with default tenancy; zonal RIs reserve capacity in the specified Availability Zone

Coverage rules that surprise buyers

  • Savings Plans do not apply to Spot usage or to usage already covered by Reserved Instances.
  • They do not reserve capacity. If you need guaranteed capacity, use On-Demand Capacity Reservations: the plan will still apply to them.
  • Amazon EKS charges are not covered, although the underlying EC2 instances are. The per-Region Dedicated Instance fee is not discounted either.
  • The terms of a purchased plan cannot be changed. As usage evolves, you can only buy additional plans.

A buying sequence that limits regret

  1. Rightsize and remove idle resources first, so the baseline excludes waste.
  2. Pull hourly eligible usage from Cost Explorer or Data Exports and look at the lowest sustained level over a window that includes your slowest period, not at the average.
  3. Open the Recommendations page in the Billing and Cost Management console, adjust the parameters, and compare its figure with your floor.
  4. Run the Purchase Analyzer to see the effect on coverage and utilization before adding the plan to the cart.
  5. Spread purchases over several dates and terms, so that renewals do not all fall on one day. AWS lets you queue a purchase for a future date.
  6. Record each plan with its type, commitment, expiry and the owner of the renewal decision.

To test a commitment against your own usage floor, try the commitment break-even calculator.

Illustrative rows of server cabinets in a large room lit with mint light
Cloud infrastructure and the operating scope of the review.

Planning a commitment purchase? Request my review quote.

The return window is short and calendar-bound

AWS allows you to return a Savings Plan whose hourly commitment is $100 or less, bought within the last seven days and in the same calendar month (UTC), subject to a return limit. For eligible returns, upfront payments are refunded in full, but usage previously covered by the returned plan is repriced at On-Demand rates or covered by another applicable plan. Active status, return quotas and seller-of-record restrictions also apply. Outside that window the commitment cannot be cancelled. The available window ends at the earlier of the seven-day limit and the UTC calendar month end. Verify eligibility in the account before relying on a return.

Returning needs the root user, or an IAM user with the savingsplans:returnSavingsPlan permission, which the AWSSavingsPlansFullAccess managed policy includes.

Who should hold purchase rights

A return can only be requested under the same management account that was used for the purchase, and with billing transfer the account that bought the plan must request it itself, even when another account pays its bill. Decide in advance which account buys. Also decide whether an external provider only recommends, with the purchase made by a role that your finance team approves. If a provider is to buy, write the approval threshold into the contract. The guide on consulting versus managed FinOps covers how to delegate that authority in writing.

Official sources used

Documents behind the statements above, as read in October 2026.

Frequently asked questions

Can all AWS services use the same commitment?

No. Compute Savings Plans cover EC2, Fargate and Lambda. Database and SageMaker AI usage need their own plan types, and usage outside the services listed for a plan type is not covered.

Should we buy before rightsizing?

Size the commitment after approved usage changes. A plan creates a fixed hourly spending obligation; it does not require the same resources to remain running, but reduced demand can leave it underused. Rightsize first, buy against the lower baseline, and leave room for planned architecture changes.

Questions before a cost review

What is an AWS reserved instance?

For EC2, a Reserved Instance is a billing discount for matching usage, rather than a physical instance. Its configuration and scope determine the benefit. AWS documents Reserved Instances.

How long can you reserve an EC2 Reserved Instance?

EC2 Reserved Instances are offered for one-year or three-year terms. Compare the eligible configuration and demand over that term before purchasing. See the EC2 terms.

What are the differences between AWS On-Demand, Spot, and Reserved instances?

On-Demand does not require a long-term commitment. Spot uses interruptible spare capacity. Reserved Instances discount matching EC2 usage under a term commitment. Select the model from workload continuity and utilization requirements. Compare EC2 purchase options.

What does reserved instance mean?

In this EC2 context it means a term-based billing benefit for matching usage. Capacity behavior depends on scope; do not assume every reservation or Savings Plan guarantees capacity.

Continue your review

Get a quote for my cloud costs

A specialist in cloud cost control reads your request and proposes a quote.

Get my quote

Before committing to database usage, follow the RDS cost optimization sequence and verify the eligible demand left after approved schedule and sizing changes. Keep separately billed block storage in the EBS volume and snapshot cost review.

Get my FinOps quote