Opportunity Name
Database Purchase Savings Plans
AWS Resource Type
Multiple AWS Database Services (Aurora, RDS, DynamoDB, ElastiCache, DocumentDB, Neptune, Keyspaces, Timestream, DMS)
Opportunity Description
AWS introduced Database Savings Plans in December 2025, enabling customers to reduce database infrastructure costs by committing to a fixed hourly spend on supported database services. These Savings Plans can provide up to 35% savings compared to on-demand pricing.
This CloudFix Finder analyzes historical database usage and spending to determine optimal Database Savings Plans commitment levels. It evaluates multiple coverage scenarios (10% through 100%) and provides estimated savings, utilization, and coverage metrics for each option.
The Finder uses AWS Cost Explorer APIs to analyze historical usage patterns and estimate potential savings based on different hourly commitment levels. This allows customers to compare multiple commitment strategies and select the coverage level that best aligns with their risk tolerance and budget.
Database Savings Plans cover the following AWS services:
-
Amazon Aurora
-
Amazon RDS (all engines)
-
Amazon DynamoDB
-
Amazon ElastiCache
-
Amazon DocumentDB
-
Amazon Neptune
-
Amazon Keyspaces
-
Amazon Timestream
-
AWS Database Migration Service (DMS)
The recommendation report generated by CloudFix includes a comparison table of coverage levels, estimated annual savings, utilization metrics, and instructions for purchasing the recommended plan.
Criteria for identifying the opportunity
The Finder identifies opportunities for Database Savings Plans when the following conditions are met:
-
Historical database spending exists
-
AWS Cost Explorer analysis detects on-demand usage for supported database services.
-
-
Analysis period configured
-
Historical spending is analyzed over a configurable lookback period (7, 30, or 60 days).
-
The default lookback period is 30 days.
-
-
Data accuracy window applied
-
The most recent two days of cost data are excluded to account for AWS billing data processing delays.
-
-
Sufficient spend detected
-
The management account must have a non-zero average hourly on-demand database spend.
-
-
Savings threshold met
-
The estimated annual savings from purchasing a Database Savings Plan must exceed the configured minimum threshold (default $100 annually).
-
-
Coverage level analysis completed
-
CloudFix runs multiple AWS Cost Explorer analyses to evaluate 10 coverage levels, ranging from 10% to 100% of eligible database usage.
-
Each coverage level includes estimated metrics such as:
-
Hourly commitment amount
-
Estimated annual savings
-
Estimated savings percentage
-
Estimated utilization
-
Estimated coverage of database usage
Potential Savings (range in % on annual basis)
Database Savings Plans can provide up to approximately 35% savings compared to on-demand pricing for supported database services.
Actual savings depend on:
-
Current on-demand database spending
-
Selected commitment level
-
Usage consistency over time
-
Service mix across supported database services
CloudFix provides estimated savings for 10 coverage levels, allowing customers to balance cost savings against commitment risk.
What happens when the Fixer is executed?
This opportunity does not include an automated Fixer.
When the recommendation is generated, CloudFix provides:
-
A detailed coverage comparison report
-
Estimated savings and utilization metrics
-
Instructions for purchasing Database Savings Plans
Customers must purchase the Savings Plan directly through AWS.
Can CloudFix implement the fix automatically once I accept the recommendation?
No.
Database Savings Plans must be purchased manually through the AWS Management Console or AWS CLI.
CloudFix provides recommendations and purchase instructions but does not automatically execute the purchase.
Does this fix require downtime?
No.
Purchasing a Database Savings Plan does not affect application availability or service performance. Savings Plans apply automatically to eligible database usage without requiring any infrastructure changes.
Bill Gleeson
Comments