RDS Extended Support Pricing | How Much Old Engine Versions Cost Per Month | Usage.ai

Skip to content

Login<br>Get a Demo

Product

Resources

Learning Hub<br>Blogs<br>Case Studies<br>Documentation<br>FAQ

Glossary

Pricing

Company

Become a Partner<br>Careers<br>About Us<br>News

See Your Savings<br>Login<br>Get a Demo

All blog posts

AWS, RDS

RDS Extended Support Pricing: Staying on Old Engine Versions

Vishal Sharma

Senior Content Strategist

Originally Published on<br>May 6, 2026

Updated May 6, 2026

17 min read

On this page

When a MySQL or PostgreSQL major version reaches end of standard support, AWS does not force an upgrade. Instead, it automatically enrolls your database in Extended Support and begins charging an additional per-vCPU-hour surcharge on top of your normal instance costs.

The surcharge starts at $0.100 per vCPU-hour in US East for the first two years. In year 3, it doubles to $0.200 per vCPU-hour. For a 4-vCPU instance, that is $292/month in year 3 that does not appear anywhere in the instance pricing table and is not reduced by your reserved instance discount.

MySQL 5.7 and PostgreSQL 11 both entered year 3 Extended Support pricing on March 1, 2026. Every team still running these versions saw their Extended Support surcharge double on that date. PostgreSQL 12 entered year 1 pricing in March 2025. If you are running any of these versions today and have not scheduled an upgrade, this guide shows you exactly what it is costing you and what the upgrade timeline needs to look like to stop paying it.

Which RDS Engine Versions Are Currently in Extended Support?

Here is the current Extended Support status for all affected engine versions as of May 2026 (verify at aws.amazon.com/rds/mysql/pricing and aws.amazon.com/rds/postgresql/pricing — EOL dates and rates change).

Engine<br>Version<br>End of Standard Support<br>Year 1-2 Rate (US East)<br>Year 3 Rate (US East)<br>Year 3 Start Date

RDS MySQL<br>5.7<br>February 29, 2024<br>$0.100/vCPU-hr<br>$0.200/vCPU-hr<br>March 1, 2026 (ACTIVE NOW)

RDS PostgreSQL<br>11<br>November 9, 2023<br>$0.100/vCPU-hr<br>$0.200/vCPU-hr<br>March 1, 2026 (ACTIVE NOW)

RDS PostgreSQL<br>12<br>February 28, 2025<br>$0.100/vCPU-hr<br>$0.200/vCPU-hr<br>March 1, 2027

RDS MySQL<br>8.0<br>TBD (community EOL April 2026)<br>$0.100/vCPU-hr (expected)<br>TBD<br>TBD — verify at AWS

RDS PostgreSQL<br>13<br>November 13, 2025<br>$0.100/vCPU-hr<br>$0.200/vCPU-hr<br>November 2027

Aurora MySQL<br>2 (MySQL 5.7 compat.)<br>October 31, 2024<br>$0.100/vCPU-hr<br>NO Year 3 rate (stays Y1 price)<br>N/A — no Year 3 for Aurora MySQL

Aurora PostgreSQL<br>11<br>February 29, 2024<br>$0.100/vCPU-hr<br>$0.200/vCPU-hr<br>March 1, 2026 (ACTIVE NOW)

The Aurora MySQL anomaly is important: Aurora MySQL versions in Extended Support are charged at Year 1 rates for the entire duration, with no Year 3 escalation.

This is different from RDS MySQL and RDS PostgreSQL, which both double their surcharge in year 3. If you run Aurora MySQL 2 (MySQL 5.7 compatible), your Extended Support charge will not double — it stays at $0.100/vCPU-hr throughout. The same is not true for Aurora PostgreSQL, which does escalate to Year 3 pricing.

Also read: RDS Reserved Instances: Engine-by-Engine Pricing and Commitment Guide

What Is the Exact Extended Support Cost at Different Instance Sizes?

The Extended Support surcharge multiplies by the number of vCPUs on your instance. Here is the full cost breakdown at common instance sizes for US East (N. Virginia) Year 3 rates — the rates currently active for MySQL 5.7 and PostgreSQL 11 as of March 2026.

Instance Type<br>vCPUs<br>Y1-2 Surcharge/hr<br>Y1-2 Surcharge/month<br>Y3 Surcharge/hr<br>Y3 Surcharge/month

db.t4g.micro<br>$0.20<br>$146<br>$0.40<br>$292

db.m7g.large / db.r8g.large<br>$0.20<br>$146<br>$0.40<br>$292

db.m7g.xlarge / db.r8g.xlarge<br>$0.40<br>$292<br>$0.80<br>$584

db.m7g.2xlarge / db.r8g.2xlarge<br>$0.80<br>$584<br>$1.60<br>$1,168

db.r8g.4xlarge<br>16<br>$1.60<br>$1,168<br>$3.20<br>$2,336

db.r8g.8xlarge<br>32<br>$3.20<br>$2,336<br>$6.40<br>$4,672

db.r8g.16xlarge<br>64<br>$6.40<br>$4,672<br>$12.80<br>$9,344

How Does Extended Support Interact with Multi-AZ and Read Replicas?

This is where the actual monthly cost can shock teams that only modeled the primary instance. Extended Support charges apply to every running instance on the affected engine version, not just the primary.

Multi-AZ Deployments

A Multi-AZ RDS deployment runs a synchronous standby instance in a separate Availability Zone. Both the primary and the standby are charged the Extended Support surcharge. For a db.r8g.xlarge (4 vCPUs) MySQL 5.7 Multi-AZ in Year 3: primary surcharge: 4 vCPUs x $0.200 x 730 hrs = $584/month. Standby surcharge: $584/month. Total Multi-AZ Extended Support surcharge: $1,168/month. This is on top of the normal Multi-AZ instance cost of approximately $960/month (2 x $0.480/hr x 730 hrs). Combined effective cost: $2,128/month versus the $960/month before Extended Support year 3 began. MySQL 5.7 Multi-AZ effectively became 2.2x more expensive in March 2026.

Read Replicas

Every read replica running the same affected engine version is also charged the Extended Support surcharge independently. A primary with...