Explanation
Why the waste happens and who it affects.
Beginning in 2024, AWS automatically enrolls these into Extended Support to maintain security updates, adding incremental charges that scale with vCPU count. These costs often appear suddenly, impacting both production and non-production environments. For development and test databases in particular, the charges may outweigh their value, leading to hidden inefficiencies if not addressed promptly.
Billing model
The pricing dimensions that drive this cost.
RDS Extended Support incurs a per-vCPU, per-hour surcharge on top of standard RDS instance charges once a major engine version passes its RDS end of standard support date, which is set by AWS and is not the same as the community end-of-life date. Fees apply continuously, even if the instance is idle.
How to detect
4 checks to find it in your estate.
- Inventory all RDS instances and record engine type and major version
- Compare deployed versions against AWS published support timelines to determine Extended Support status
- Check billing data for "RDS Extended Support" line items and correlate to specific RDS instances
- Identify non-production or idle databases that are accruing Extended Support charges without business justification
How to fix
4 ways to remove the waste.
- Upgrade RDS instances to currently supported major versions to avoid Extended Support fees
- Plan upgrades in non-production first to validate compatibility before applying in production
- Decommission unused or development databases that no longer provide value
- Embed version monitoring in database governance processes to anticipate and prepare for end-of-life events
Documentation
Vendor references for pricing and configuration.