Autonomous Rate Optimization for your AWS Database Spend
Optimizing database spend used to mean handling each service on its own: a Reserved Instance here, a Reserved Node there, and nothing at all for serverless costs. Database Savings Plans put one discount instrument across a majority of that surface, turning a scattered set of services into a category you can manage as a whole. Now grouped, this cloud usage portfolio poses both an exciting opportunity to save but also a new level of effort to manage effectively.
Today we’re announcing support for AWS Database Savings Plans as part of Autonomous Discount Management™ (ADM) for AWS, in Early Access. ADM continuously optimizes the database spend for you, capturing more savings with less commitment risk while lifting the operational burden from your team.
The Broadest Savings Plan AWS Has Shipped
Database Savings Plans are the fourth Savings Plan type, alongside Compute, EC2 Instance, and SageMaker. Where a Reserved Instance comes with a stack of decisions that balance a higher discount against flexibility, a Database Savings Plan comes with few choices. Only one term and one payment option are available, 1-year No Upfront. You commit to a post-discount hourly spend amount, and receive a discount on eligible usage of ten different database services and counting, more services than any Savings Plan before it.
Working Database Savings Plans into an existing commitment strategy takes careful planning. Like a Reserved Instance/Node, a Savings Plan is immutable. Once purchased, the savings plan cannot be modified or exchanged, so the amount selected is owed hourly for a year. Aim too high and you pay for more than you need, aim too low and you leave savings on the table.
The discount ranges from 12% to 35% depending on the usage to which it applies, making it difficult to know how much to purchase. Database Savings Plans apply more broadly than Reserved Instances, covering serverless services that other instruments don’t discount. But they also yield a lower discount on the usage both can cover, presenting a challenge to structuring your discount portfolio.
The Nuance Runs Deep
Database Savings Plans cover a lot of ground, but not evenly. Previously un-discountable services like Aurora Serverless, DocumentDB, Neptune, Keyspaces, and Timestream are now discount-eligible. Others, like Redshift and MemoryDB, aren’t covered by a Database Savings Plan at all and still use Reserved Instances/Nodes. ElastiCache only qualifies on Valkey, not Redis or Memcached. For provisioned databases, Database Savings Plan eligibility favors newer instance generations, so older families still use Reserved Instances as the only available commitment option.
And it keeps evolving. AWS added OpenSearch in March 2026, suggesting that the program is being developed. Every change is another opportunity to save more for anyone tracking updates closely enough to act on them.
The choice between discount rate and commitment flexibility must be evaluated and acted on continuously at scale. At one or two resources, you can reason it out over coffee. Across a portfolio, those decisions number in the thousands and shift as cloud database usage changes. Capturing the full upside takes a deliberate strategy and the discipline to execute it consistently over time.
Enter ADM
You shouldn’t have to live in the minutia to get it right. ADM automates rate optimization for you. It manages complexity, adds flexibility with Adaptive Laddering™, and executes commitment purchases, the same way it already handles other immutable commitments.
ADM understands which usage is coverable, builds the portfolio that best fits your usage, and evolves with the rules governing Database Savings Plans. Adaptive Laddering distributes risk, deploying your commitments in small, frequent purchases that result in staggered expirations instead of one large one. This builds flexibility that allows your commitment portfolio to adapt to your changing usage.
ADM manages the blending of Database Savings Plans with higher-discount Reserved Instances/Nodes intelligently and steers the mix toward what you value most, flexibility or discount. You realize a higher Effective Savings Rate (ESR), lower Commitment Lock-in Risk (CLR), and remove a never-ending operational burden from your team.
Staying current is on us. Just as AWS added OpenSearch to the list of coverable services, so did our automation. If AWS makes further changes to this commitment offering, ADM will update the portfolio according to your defined strategy, allowing savings to climb while your team stays focused on the work that needs them.
Join the Early Access Program
We’re working with a small group of customers to shape this together before general availability. If you run databases on AWS and want that spend autonomously optimized for you, we’d like you in it.
- Already a ProsperOps customer? Talk to your ProsperOps team, or express interest from the Console, and we’ll confirm your eligibility.
- New to ProsperOps? Sign up for Early Access, and a ProsperOps FinOps specialist will reach out to talk through your opportunity and Early Access eligibility.
We’re on a mission to automate and simplify savings for cloud customers, and Database Savings Plans are the newest part of it.
Prosper on! 🖖
Mark
