Skip to content
CloudPouch Docs

How to find Amazon RDS Extended Support costs

Amazon RDS Extended Support bills you per vCPU-hour for every MySQL or PostgreSQL database (including Aurora) running an engine major version past its standard support end date — and enrollment is automatic, so the first sign is often a bigger RDS bill. CloudPouch shows which databases are enrolled today, which will enroll within the next 12 months, and what the surcharge costs per month.

How the charge works

Section titled “How the charge works”

When a MySQL or PostgreSQL major version reaches the end of RDS standard support, AWS does not stop the database. It keeps patching critical security issues under RDS Extended Support and charges for that service per vCPU-hour, on top of the normal instance and storage cost. Two properties make it easy to miss:

  • Enrollment is automatic. No opt-in, no confirmation email you’d act on — running the old version past the deadline is the enrollment.
  • The rate increases over time. AWS prices Extended Support in stages: the per-vCPU-hour rate rises after the first phase, so a database that was “only” mildly expensive to keep on an old engine gets noticeably worse in later years. Check the RDS pricing page for your engine — for example RDS for MySQL pricing — for current rates per region.

Because the charge scales with vCPUs, one large production database on an outdated engine can quietly outcost a whole fleet of small ones.

Find affected databases with CloudPouch

Section titled “Find affected databases with CloudPouch”
  1. Open CloudPouch and select the AWS profile that can read RDS and cost data.
  2. Choose Current Month or Previous Month.
  3. Open Amazon Relational Database Service from the AWS services table.
  4. Click Check Cost Insights.
  5. Review the RDS Extended Support section.

For each database, CloudPouch shows the engine and version, whether it is already enrolled, the current monthly support cost, and the cumulative support cost since enrollment — the number that usually gets upgrade projects approved.

The 12-month lookahead

Section titled “The 12-month lookahead”

CloudPouch also flags databases that will enter Extended Support within the next 12 months if nothing changes, together with the future monthly cost they would add. This is the cheapest moment to act: an engine upgrade planned six months ahead of the deadline is routine maintenance, while the same upgrade after enrollment is an emergency with a running meter. The enrollment reporting is consistent across the current-month, previous-month, and future-enrollment views, so numbers you quote from one view match the others.

How to prioritize

Section titled “How to prioritize”

Do not simply upgrade the most expensive database first. Rank by cost impact, then filter by feasibility:

  • Major engine version upgrades can change SQL behavior — application compatibility testing comes first.
  • Databases with tight maintenance windows or weak rollback plans need more lead time, not less.
  • A database that is barely used but enrolled in Extended Support may be a candidate for retirement rather than upgrade — CloudPouch’s RDS insights also flag unused and over-provisioned databases in the same run.
Section titled “Related pages”