Avoid Surprise AWS RDS Charges in 2026

From 31 Jul 2026 Amazon Web Services (AWS) will automatically start charging anyone using RDS MySQL 8.0 Community Edition for “Extended Support”. Your monthly database costs could increase significantly (in many cases close to double).

TL;DR

• MySQL 8.0 goes End of Life (EOL) In April 2026
• From 31 Jul 2026 AWS will start charging extra for “Extended Support”
• There are options, you don’t have to upgrade to MYSQL 8.4

What Happens When AWS RDS MySQL 8.0 Reaches End of Life?

• AWS automatically enrols your RDS MySQL 8.0 instance into Extended Support
• Additional charges are added to your monthly AWS bill
• Security updates continue for up to 3 more years
• No automatic optimisation or performance improvements

This is primarily a commercial decision by AWS, not a technical upgrade.

Your Options

Option 1: Do Nothing and Pay for Extended Support

This is the default outcome if no action is taken and there is nothing wrong with it. AWS will automatically upgrade your instance to Extended Support.

Pros

• No work required
• Continued security patches
• Supported until approximately July 2029

Cons

• Higher monthly costs
• No technical benefit
• Unnecessary operational spend

For cost-conscious businesses, this is rarely the best long-term choice.

Option 2: Upgrade to MySQL Community 8.4

Move to MySQL Community 8.4, which is supported until 31 July 2029.

Pros

• Avoid Extended Support charges
• Remain on community MySQL

Cons

• Requires application compatibility testing
• Potential query or driver differences
• Requires Developer time and regression testing

Option 3: Move to Aurora MySQL 8.0 (Best of both worlds)

For most organisations, the most cost-effective and lowest-risk option is to migrate to Amazon Aurora MySQL 8.0. 

Aurora is AWS’s MySQL-compatible database engine. It is fully compatible with MySQL 8.0, and for most applications behaves identically.

Aurora MySQL 8.0 is supported until 30 April 2028, without Extended Support charges.

Why this is attractive:

• 100% MySQL 8.0 compatible
• Avoids 2026 Extended Support price increases
• Often improved performance and storage resilience
• Potential for zero-downtime migration (dependant on data etc)

Warning: MySQL community reserved instances are not compatible with Aurora MySQL reserved instances. You will have to calculate if this is worthwhile for you as there maybe options to transfer your reservations.

Why SMEs Should Plan Now

• Avoid sudden AWS bill increases in 2026
• Schedule migration during low-risk periods
• Controlled testing window
• Maintain predictable cloud operating costs
• Avoid rushed engineering decisions

Leaving this until mid-2026 could result in rushed decisions, increased costs, or unnecessary operational risk.

Summary: Best Path for AWS RDS MySQL Users

Need Help With an AWS RDS to Aurora Migration?

We are a UK-based Linux and AWS consultancy specialising in:

• AWS RDS optimisation
• Aurora MySQL migrations
• Zero-downtime database cutovers
• Cost reduction and cloud optimisation for SMEs

If you would like a review of your current AWS RDS MySQL estate and projected 2026 cost exposure, contact us.

Frequently Asked Questions

Will AWS automatically upgrade my RDS MySQL 8.0 instance?
Yes. After 31 July 2026, AWS will automatically enrol your instance into Extended Support unless you migrate or upgrade beforehand.

Is Aurora MySQL fully compatible with MySQL 8.0?
Yes. Aurora MySQL 8.0 is designed to be fully compatible with MySQL 8.0 Community Edition.

Can the migration be done with zero downtime?
In most cases, yes. Using replication and controlled cutover techniques, downtime can be reduced to seconds or avoided entirely.

How long does an RDS to Aurora migration take?
Typically a few days including testing, depending on database size and complexity.