AWS Database Savings Plans: Everything You Need to Know

AWS has recently introduced a major shift in how customers save on managed databases: Database Savings Plans. These new commitments introduce more flexibility than classic Reserved Instances while expanding coverage to services that historically had no reservation model at all.

This has big implications. For example, Database Savings Plans offer discounts of up to 35% on serverless databases and up to 20% on modern instance-based workloads. For serverless, this is the first time commitment-based discounts have been available, so the savings are entirely net-new. Database Savings Plans don’t just apply to RDS, but apply to a broad range of managed AWS databases—meaning a single dollar-per-hour commitment can follow your spend across many AWS-managed databases instead of being tied to one engine or instance family. However, these changes also introduce complexities, with new incentive structures and tradeoffs to consider.

This essential guide explains what Database Savings Plans actually deliver — the benefits, the limitations, and how to build the right coverage strategy going forward.

What are AWS Database Savings Plans

Database Savings Plans are a commit-to-spend model that discounts eligible database usage up to the amount you commit to per hour. They provide flexibility across services, instance families, and regions.

You choose a dollar per hour commitment, with a one-year term and no upfront payment. 

AWS automatically applies discounted rates across supported database services.

The Advantage of Database Savings Plans: One plan Covers Many Database Services

A single Database Savings Plan applies across a broad range of managed databases including:

• Amazon Aurora
• Amazon RDS any engine
• Amazon DynamoDB
• Amazon ElastiCache Valkey
• Amazon DocumentDB
• Amazon Neptune
• Amazon Keyspaces
• Amazon Timestream
• AWS Database Migration Service

This consolidates what used to be multiple reservation mechanisms into one flexible commitment, making it easier for FinOps and engineering teams to reduce the risk of over-committing to a single database service or instance family.

#1: Expansion of Service Coverage Depth (Plus What’s Included and What’s Not)

At nOps, we’ve analyzed AWS’s latest Database Savings Plans pricing data (effective December 3, 2025) across 20,725 pricing records covering 9 database services and 36 AWS regions. Here’s what the numbers reveal:

(Each record represents a unique combination of service, region, instance type, and deployment option (single-AZ, Multi-AZ, serverless, etc.) with its specific Database Savings Plan rate. More records = more pricing options = better chance your exact configuration is covered.)

What’s Included

What’s NOT Included:

Key Insight: The breadth of coverage means most modern database workloads can benefit. However, AWS is strategically encouraging migration to newer instance families (generation 7+) and modern database engines (Valkey instead of Redis) through pricing incentives. Older instance families and legacy engines require traditional Reserved Instances or remain on-demand.

#2: Flexibility across sizes and regions as workloads change

Because Database Savings Plans are tied to a dollar-per-hour commitment rather than a specific instance type or configuration, your discounts keep applying when you:

• Move a workload from RDS to Aurora
• Change instance sizes or switch instance families
• Shift databases into different regions

The implication: you can change where and how your databases run without stranding previously purchased commitments.

#3: Serverless databases finally get discounts

Serverless workloads historically had no commitment-based savings. Now they receive the highest benefit.

Why Serverless Discounts Matter: Real-World Impact

The 30-35% discount on serverless databases is particularly valuable because these workloads previously had ZERO commitment-based savings options. Organizations using Aurora Serverless v2, DocumentDB Serverless, or Neptune Serverless for cost efficiency (pay-per-use) can now combine that benefit with commitment discounts.

#4: DynamoDB discount coverage expands

DynamoDB now receives discounts whether using pay-per-request or provisioned throughput.

This is the first time DynamoDB on demand receives database commitment savings.

DynamoDB Pricing Breakdown

The Database Savings Plans pricing data shows DynamoDB coverage includes both on-demand (18% discount) and provisioned capacity (12% discount) billing modes. Our analysis reveals 432 unique DynamoDB pricing combinations across all 36 AWS regions, covering both standard and Infrequent Access storage classes.

Unlike other database services, DynamoDB has two distinct billing modes, and Database Savings Plans cover both from a single commitment. This creates a unique opportunity to maximize discounts across your entire DynamoDB portfolio—one commitment can simultaneously discount your provisioned capacity tables (steady workloads), on-demand tables (variable/spiky workloads), and even replicated writes for Global Tables deployments.

#5: A significant hidden advantage: automatic application

If the usage of one of the services covered by Savings Plans is reduced or retired, Database savings automatically apply to other eligible DB services — ensuring ongoing coverage and savings.

Meaning, if you migrate from RDS → Aurora → Serverless → Valkey, your commitment stays in use rather than being stranded. DSPs protect coverage during modernization instead of penalizing architectural change.

This is perfect for long-term transformation.

The Trade-Offs of Database Savings Plans

#1: Lower discounts than classic Reserved Instances

Flexibility comes at the price of reduced discount depth. Database Savings Plans improve coverage and reduce the risk of stranded commitments, but they usually don’t beat classic Reserved Instances or Reserved Capacity on pure percentage savings for long-lived, stable workloads. Here is how the discounts compare.

#2: How AWS Pricing Nudges Customers Toward Modern Databases

The new Database Savings Plans from AWS don’t just offer discounts; they steer customer architecture through pricing incentives.

Database Savings Plans reward:

• Migration to Aurora
• Serverless architectures
• Adoption of Valkey
• Instance modernization to seventh-generation families

And they apply economic pressure against

• Redis
• Older RDS engines
• Commercial database engines
• Long-term RI discount expectations

Database Savings Plans are available only on a one year term. There are no three year Savings Plan terms, which limits long term discount potential and further reinforces AWS’s push toward shorter, more flexible commitments on newer services.

The Challenges of AWS Database Savings Plans: More complexity for FinOps and engineering teams

It’s clear that you get a better discount if you migrate to modern and serverless architectures. However, modernization doesn’t happen overnight. These discount drives do provide incentives to modernize the stack, but they also add the extra complexity of managing both RDS Reserved Instances (RI) and Database Savings Plans. Especially if migrating to a modern stack is on the horizon, how you manage new or existing RIs becomes important, as they become an additional layer to balance.

How nOps Analyzes Database Savings Plans Opportunities

At nOps, we’ve built automated analysis capabilities that match your actual database usage patterns against Database Savings Plans pricing to identify optimization opportunities. Here’s how it works:

1. Usage Pattern Analysis

We analyze your real-time usage data to identify:

• Database services in use (RDS, DynamoDB, Neptune, etc.)
• Instance types and sizes
• Regional distribution
• Usage consistency (24/7 vs. variable)
• Current on-demand vs. Reserved Instance coverage

2. Pricing Matching Engine

Our system matches your usage to Database Savings Plans pricing by:

• Service code (AmazonRDS, AmazonDynamoDB, etc.)
• Usage type (InstanceUsage, ServerlessV2Usage, etc.)
• Region code
• Instance family and size

3. Savings Calculation

For each customer, we:

• Calculate live usage and existing commitments on eligible database services and how they sit within the costs
• Project the Database Savings Plan cost and where it can be used for maximum savings.
• Project potential monthly and annual savings
• Continually adjust the commitments based on usage patterns (including variable and spiky workloads) to maximize ROI

Key Takeaways

Under new Database Savings Plans, it’s clear that you get a bigger discount and better flexibility if you modernize your database stack to newer engines, serverless options, and seventh-generation instance families. 

But modernization doesn’t happen overnight. While you’re in transition, Database Savings Plans add another layer of complexity on top of existing RDS Reserved Instances. To maximize savings without overcommitting, it’s best to use a hybrid approach that blends Database Savings Plans and Reserved Instances, and to adopt an adaptive “laddering” strategy rather than a one-time “big bang” of long-term RIs. Commitments are fixed, but your cloud usage is not—especially as workloads shift from traditional compute to GenAI and modern databases. At nOps, we help customers continuously adjust their commitment mix so they maintain flexibility and coverage as their architectures evolve.

Key benefits of nOps automated Database Savings Plan Management include:

• Real-time tracking of Database Savings Plan utilization and existing commitments utilization 
• Identification & remediation of underutilized commitments
• Detection of opportunities to increase coverage and automatically cover the baseline usage right away, while laying the foundation to cover spiky and variable usage with maximum flexibility. 

Curious what that looks like in your environment? Book a demo call with one of our AWS Experts to find out how much you can save today.

nOps manages $2 billion in cloud spend for our customers and is rated 5 stars on G2.