Service comparisons / Savings Plans vs Reserved Instances vs Spot Instances

Savings Plans vs Reserved Instances vs Spot Instances

Savings Plans and Reserved Instances cut prices for steady use in exchange for a one- or three-year commitment; Spot Instances use spare capacity at up to 90% off but can be interrupted. How to pick the right EC2 pricing option.

Last checked against AWS documentation · How we write our content

QuestionSavings PlansReserved InstancesSpot Instances
Use it whenSteady compute spend you can commit to, while instance types may changeSteady use of a specific instance type, or a database or cache that needs itWork that can stop and restart, such as batch, CI, rendering and stateless web tiers
CommitmentA dollar amount per hour for 1 or 3 yearsA specific configuration for 1 or 3 yearsNone
DiscountUp to 72% (EC2 Instance Savings Plans); up to 66% (Compute Savings Plans)Up to 72% (Standard); up to 66% (Convertible)Up to 90%
CoversCompute plans cover EC2, Fargate and Lambda in any RegionEC2, and also RDS, ElastiCache, OpenSearch and RedshiftEC2 (and Fargate Spot)
Watch out forA commitment you don't use is still billedOnly zonal Reserved Instances reserve capacityInstances can be reclaimed with a two-minute warning

On-Demand is the default: no commitment and the full price. Every other option trades flexibility for a discount, so the right answer depends on how steady and how interruptible the workload is.

How to choose

Exam traps