AWS expanded its Savings Plans portfolio with Database Savings Plans, a spend-based discount model for managed database services that can cut costs by up to 35%. This is the first time the Savings Plans model has extended beyond compute, and it changes how DB teams can commit to long-term database spend.
Usage.ai added native support for Database Savings Plans in January 2026.
What Are AWS Database Savings Plans?
Instead of committing to a specific instance class, engine, or Region (like Reserved Instances require), you commit to a consistent hourly spend amount for a one-year term. AWS automatically applies discounts across all eligible usage up to that committed amount, every hour, without manual action.
The model mirrors how
How Database Savings Plans Differ From Reserved Instances
Reserved Instances require you to specify at purchase the exact instance class, database engine, deployment type, and AWS Region. All four must match the running workload for the discount to apply. Change any one of them and the RI no longer applies.
Modern database environments regularly resize, upgrade instance generations, migrate engines, or shift from Single-AZ to Multi-AZ. Each is a routine decision, but each can strand an RI and create unexpected cost exposure.
Database Savings Plans decouple the discount from configuration. Committed spend follows actual usage rather than a specific setup that may change.
A few key structural differences:
- Flexibility: RIs break on config changes; Savings Plans follow spend through routine changes
- Max discount: RIs offer up to 40%+ for 3-year All Upfront; Database Savings Plans offer up to 35% (serverless) or up to 20% (provisioned Gen 7+)
- Term: RIs support 1-year or 3-year; Database Savings Plans are 1-year only
- Billing order: RIs are applied first each billing hour; Savings Plans apply second, to remaining eligible usage
- Coverage automation: RIs must match configuration exactly; Savings Plans apply automatically across eligible spend
For DynamoDB, it's worth noting you cannot combine Database Savings Plans with DynamoDB reserved capacity on the same workload.
What's the Financial Impact?
Discount ranges by deployment model:
- Serverless (Aurora Serverless v2, Aurora DSQL, ElastiCache Serverless for Valkey, DocumentDB Serverless, Neptune Serverless, OpenSearch Serverless) up to 35%
- Provisioned Gen 7+ instances (Aurora, RDS, ElastiCache Valkey, DocumentDB, Neptune, DMS, Timestream InfluxDB) up to 20%
- DynamoDB / Keyspaces on-demand throughput up to 18%
- DynamoDB / Keyspaces provisioned throughput up to 12%
Beyond the headline discount, the stronger financial argument is reducing stranded RI cost. When an RI becomes stranded because an instance was resized or upgraded, you keep paying for the RI while also paying on-demand rates for the new configuration. For large database environments with frequent change, the avoided waste from stranded RIs can equal or exceed the small discount difference between the two commitment models.
What Changes If You're Currently Using Reserved Instances?
Existing RIs continue functioning normally for the remainder of their term with no disruption, no immediate action required.
The decision point comes at renewal. Teams should evaluate how often their databases resize, change capacity modes, or shift deployment models. If the answer is frequently, the flexibility of a spend-based commitment is likely worth the small discount difference compared to an RI.
For the full breakdown of how Usage.ai automates RI and Savings Plan optimization
SOCIAL SHARE CARD GENERATOR