Amazon RDS · Finder + guided fix

RDS Optimize EOL Version

OptimizeEOL Version

Upgrade RDS and Aurora from end-of-life versions to avoid AWS Extended Support fees. Save up to 50% by migrating to current MySQL and PostgreSQL versions.

Guided fix
Effort: Advanced
Action: Optimize
Amazon RDS

What happens, in order.

Finder · read-only
Finds the opportunity
Scans your connected accounts with a read-only role. It can see resource metadata and usage; it can’t change anything.
You
Review in Recommendations
It appears in your Recommendations view with what it would save.
Guided fix
You make the change
You apply it yourself, following the fix’s step-by-step instructions; the write-up below explains it.

Finder role

Read-only. It can see resource metadata and usage. It can’t change anything.

Fixer role

Not used here: this one is a guided fix, so the change is yours to make.

Saves by

AWS RDS and Aurora database instances running on older, end-of-life (EOL) versions of MySQL and PostgreSQL can incur significant costs due to AWS's Extended Support fees. This finder identifies such instances, providing visibility into potential cost-saving upgrade opportunities before the onset of these fees.

AWS RDS and Aurora database instances running on older, end-of-life (EOL) versions of MySQL and PostgreSQL can incur significant costs due to AWS’s Extended Support fees. This finder identifies instances on versions approaching end-of-life, allowing you to plan upgrades before these additional costs apply.

Overview

Problem Statement

When AWS database engine versions reach their end-of-life (EOL), customers face a critical decision: upgrade to a newer version or pay for Extended Support. AWS introduced Extended Support fees for RDS and Aurora instances running EOL versions of MySQL and PostgreSQL to encourage migration to newer, more secure, and feature-rich versions.

These Extended Support fees can significantly increase your database costs, sometimes by as much as 1.5x the base instance cost, depending on the specific database engine and version. Organizations often miss these impending fees due to lack of visibility into database version lifecycles or insufficient planning for version upgrades.

Solution

CloudFix scans your AWS accounts to identify RDS and Aurora database instances running on versions that are approaching or have reached AWS end-of-life support. The finder calculates the potential Extended Support fees these instances will incur and helps you proactively plan version upgrades to avoid these additional costs.

By upgrading your database instances before Extended Support fees apply, you can maintain optimal database performance and security while avoiding unnecessary costs.

AWS Services Affected

Amazon RDS

Amazon Aurora

How It Works

The RDS Optimize EOL Version finder uses your cost and usage data, read-only, to identify RDS and Aurora MySQL and PostgreSQL instances on versions that are approaching or already in AWS Extended Support. It estimates the Extended Support fees each instance will incur based on AWS pricing and lists the opportunities in your Recommendations, prioritized by potential savings.

Implementation Approach

CloudFix provides this as a finder-only feature to help you identify which database instances would benefit from version upgrades. Due to the complexity and potential business impact of database upgrades, CloudFix does not automatically apply these changes.

Your team should carefully plan and execute database version upgrades following AWS best practices, including:

Creating database snapshots before upgrading
Testing compatibility with applications in non-production environments
Planning for potential downtime during the upgrade process
Reviewing application code for SQL syntax compatibility with newer engine versions
Scheduling upgrades during maintenance windows with minimal business impact

FAQ

What are RDS Extended Support fees?

When an RDS or Aurora database engine version reaches its end of standard support date, AWS charges additional hourly fees to continue supporting the outdated version. These fees are calculated based on the database instance’s vCPU count and can significantly increase your overall database costs.

How much do Extended Support fees cost?

Extended Support fees vary by engine type, but generally cost between $0.05 to $0.2 per vCPU per hour, depending on the database engine and region. For example, for MySQL 5.7, AWS charges approximately $0.12 per vCPU-hour in US East regions, which can increase your database costs by 20-30% for typical instances.

Which database versions are affected by Extended Support fees?

Currently, Extended Support applies to RDS for MySQL 5.7 and PostgreSQL 11, with more versions to be added as they reach end of standard support. AWS regularly updates the list of versions subject to Extended Support fees.

Is upgrading database versions risky?

Database upgrades carry some inherent risk, but can be safely performed with proper planning and testing. AWS provides detailed upgrade guides for each database engine, and features like RDS Blue/Green deployments can minimize risk by creating a separate staging environment for testing before promoting the upgrade to production.

How long do the Extended Support fees apply?

AWS typically offers Extended Support for three years after a version reaches its end of standard support date. After this Extended Support period ends, you must upgrade as AWS will no longer support or maintain the version.

Browse all 110+ finders

See whether this one applies to your account.

A free savings assessment reports which fixers can be applied to your environment. Results typically within 24 hours.

Get a free savings assessment See how CloudFix works

What happens, in order.

Finds the opportunity

Review in Recommendations

You make the change