Skip to content
Cloud Efficiency Hub

Underutilized RDS Commitment Due to Workload Drift

The short version

RDS workloads often evolve - changing engine types, rightsizing instances, or shifting to Aurora or serverless models.

Jason DiDomenico

Director of FinOps @ Discover Financial Services

AWS service
AWS RDS
Category
Databases
Reference
CER-0030
Type
Underutilized Commitment

Explanation

Why the waste happens and who it affects.

When these changes occur after Reserved Instances have been purchased, the existing commitments may no longer match active usage. This results in silent overspend, as underutilized RIs continue billing without offsetting usage.

Unlike Convertible EC2 RIs, RDS RIs cannot be exchanged. Selling unused RDS RIs is not supported. In rare cases, AWS Support may approve a goodwill adjustment, but this is not guaranteed. The most effective way to recover value is to steer eligible workloads back toward the reserved configuration.

Billing model

The pricing dimensions that drive this cost.

  • Standard RDS Reserved Instances are billed hourly regardless of instance usage
  • RIs are tied to specific configurations and cannot be modified once purchased, but for most engines they are size-flexible: the discount applies automatically across sizes of the same instance class type in the same Region and engine, and across Single-AZ and Multi-AZ, so rightsizing within the family keeps the RI utilized (size flexibility does not apply to RDS for SQL Server or RDS for Oracle License Included)
  • If RDS usage patterns change or migrate away from covered configurations, the RI continues to accrue cost without providing benefit

How to detect

4 checks to find it in your estate.

  • Identify underutilized RDS Reserved Instances using billing and utilization data
  • Break down the instance classes, engines, and regions with low or zero usage
  • Trace whether existing workloads have moved off those configurations - and why
  • Quantify the cost of unused commitment to prioritize remediation

How to fix

6 ways to remove the waste.

  • Evaluate whether current or new workloads can run on the reserved instance types
  • Prioritize launching new RDS instances that align with the unused commitment
  • Where feasible, upgrade or shift workloads to covered instance classes while monitoring performance and future fit
  • Document changes made to consume the commitment and reassess once the reservation expires
  • In rare cases, contact AWS Support to request a reservation adjustment - note that approval depends on RI type, remaining term, and value parity
  • For future commitments on workloads likely to change engine, instance family or size, or move to Aurora Serverless, consider Database Savings Plans, which apply across supported engines, instance families, sizes, deployment options and Regions

Documentation

Vendor references for pricing and configuration.