As of November 18, 2026, this post sums up the official pages linked here.
The problem
Your Amazon RDS line on the AWS bill went up this month. Nobody changed an instance size, added storage or bought anything new. The database runs the same version as last month. The new cost is RDS Extended Support.
This can catch many teams this year. RDS for MySQL 8.0 reached its RDS end of standard support on July 31, 2026. RDS for PostgreSQL 13 reached it on February 28, 2026. In this post we show what the charge is and why it started without anyone clicking anything. We also show how to find the databases behind it and stop it safely.
Root cause: an old major version keeps running, for a fee
Here is how AWS describes it. Extended Support "allows you to continue running a database on a major engine version" past its RDS end of standard support date. AWS charges extra for this. (RDS Extended Support)
Charges start "the day after the RDS end of standard support date." (RDS Extended Support charges)
For the two versions most teams ask about, AWS's own calendars show:
| Version | RDS end of standard support | Extended Support year 1 pricing starts | Year 3 pricing starts | RDS end of Extended Support |
|---|---|---|---|---|
| RDS for MySQL 8.0 | 31 July 2026 | 1 August 2026 | 1 August 2028 | 31 July 2029 |
| RDS for PostgreSQL 13 | 28 February 2026 | 1 March 2026 | 1 March 2028 | 28 February 2029 |
(Sources: MySQL on Amazon RDS versions and Release calendar for Amazon RDS for PostgreSQL. MySQL 5.7, PostgreSQL 11 and PostgreSQL 12 are already past their end of standard support too; see the same pages.)
The MySQL page also notes that "MySQL 5.7 and 8.0 are now only available under RDS Extended Support."
Why nobody "turned it on"
Enrollment is the default in many setups:
- With the AWS CLI or RDS API, if you "don't specify the RDS Extended Support setting, Amazon RDS defaults to enabling RDS Extended Support." AWS adds that the same default applies when you automate with CloudFormation or other services. It keeps the database available past the end of standard support. In the console, the setting "isn't selected by default." (Creating a DB instance with RDS Extended Support)
- When an enrolled database reaches the date, RDS enrolls it automatically. AWS says this "doesn't change the database engine and doesn't impact the uptime or performance of your DB instance." (RDS Extended Support)
So the database keeps working exactly as before. The only thing that changes is the bill.
How the charge is priced
For provisioned RDS for MySQL instances, AWS says "RDS Extended Support is priced per vCPU per hour." The price also depends "on the AWS Region and calendar date." (Amazon RDS for MySQL pricing)
The pricing pages give these examples:
- RDS for MySQL 5.7 in US East (Ohio): "$0.100 per vCPU-hr between March 1, 2024 to February 28, 2026. Starting March 1, 2026, you will be charged $0.200 per vCPU-hr." (Amazon RDS for MySQL pricing)
- RDS for MySQL 5.7 on a db.r5.large in US East (N. Virginia) in the first year: "$0.200 per hour, or 2 vCPUs x $0.100 per vCPU-hr." (same page)
- RDS for PostgreSQL 12 in US East (Ohio): "$0.100 per vCPU-hr between March 1, 2025 to February 28, 2027. Starting March 1, 2027, you will be charged $0.200 per vCPU-hr." (Amazon RDS for PostgreSQL pricing)
These are AWS's worked examples, not the rate for every version and Region. Read the pricing page for your engine, version and Region before you estimate a bill. The formula AWS gives is simple: number of vCPUs x the hourly rate for your Region and pricing year, for every hour the instance runs.
Five details make the bill bigger than people expect. All five come from the FAQ on the MySQL and PostgreSQL pricing pages and the charges page:
- Multi-AZ standbys pay too. With one standby, you are charged "on both your primary and standby instances." With two readable standbys, on the primary and both standbys.
- Read replicas pay too, if they run a major version past its end of standard support.
- Reserved Instances do not help. "RDS Extended Support charges are independent of instance charges. Therefore, Reserved Instance discounts are not applicable to RDS Extended Support charges."
- A restore can start a new charge. Snapshots themselves are not charged. But restoring a DB snapshot "to a new DB instance after end of standard support" is charged "RDS Extended Support pricing for that instance." The same applies if you create a new instance on that version.
- The price goes up in year 3. The first two years use the year 1 and 2 rate. Year 3 pricing starts "on the first day of the third year."
Step 1: find the databases behind the charge
List every DB instance with its engine, version and enrollment:
aws rds describe-db-instances \ --query 'DBInstances[].[DBInstanceIdentifier,Engine,EngineVersion,DBInstanceClass,MultiAZ,EngineLifecycleSupport]' \ --output table AWS says that if Extended Support is available for a database, the response includes EngineLifecycleSupport. The value open-source-rds-extended-support means the database is enrolled. The value open-source-rds-extended-support-disabled means enrollment was turned off. (Viewing enrollment in RDS Extended Support)
Enrollment alone is not a charge. AWS notes that "Charges for RDS Extended Support only start when your DB engine version has reached the RDS end of standard support." So the list you care about is: enrolled and on a major version whose end of standard support has passed. For Aurora clusters and Multi-AZ DB clusters, run describe-db-clusters as well, because the setting lives at the cluster level.
In the console, the Databases page has an RDS Extended Support column. If you do not see it, AWS says to turn it on under the Preferences icon. (same page)
The command lists one Region at a time, so run it in every Region you use (add --region).
Step 2: check the dates for each version
You can read the support dates from the CLI instead of a web page:
aws rds describe-db-major-engine-versions \ --engine mysql \ --major-engine-version 8.0 AWS says the response includes SupportedEngineLifecycles, with a start and end date for standard support (open-source-rds-standard-support) and for Extended Support (open-source-rds-extended-support). This works for the open source engines (MariaDB, MySQL and PostgreSQL), not the commercial ones. (Viewing support dates, describe-db-major-engine-versions)
Use --engine postgres for PostgreSQL.
Step 3: stop the charge the right way
AWS lists two things that stop the charge. One is upgrading "to an engine version that's covered under standard support." The other is deleting "the database that's running a major version past the RDS end of standard support date." (RDS Extended Support charges)
Option A: plan and test a major version upgrade (the usual fix)
Upgrade to a major version with a long standard support window, not just the next one. AWS warns that "The charges will restart if your target engine version enters RDS Extended Support in the future." (same page) Two examples from the calendars:
- MySQL: 8.4 has RDS end of standard support on 31 July 2029.
- PostgreSQL: 14 reaches its RDS end of standard support on 28 February 2027, only a few months away. PostgreSQL 16 runs to 28 February 2029, and 17 to 28 February 2030.
For RDS for MySQL, MariaDB and Aurora MySQL, AWS says you can use Blue/Green Deployments to move off an Extended Support version. This works as long as Blue/Green supports your engine, Region and version. (Amazon RDS for MySQL pricing FAQ)
If you upgrade in place, know what the command does. The CLI reference covers --engine-version. It says: "Changing this parameter results in an outage and the change is applied during the next maintenance window unless the ApplyImmediately parameter is enabled." A major upgrade with a non-default parameter group needs a parameter group from the new version's family. You must also set --allow-major-version-upgrade. (modify-db-instance) Test on a restored copy first. That copy is charged Extended Support while it runs on the old version.
Option B: delete what nobody uses
Old read replicas, a forgotten test database, a copy restored "just to check something." Each one is charged on its own. If it is not needed, take a final snapshot and delete it. Snapshots are not charged Extended Support. (Amazon RDS for MySQL pricing FAQ)
Be careful with "just turn it off"
You can change enrollment at any time with the EngineLifecycleSupport setting. In the CLI, that's --engine-lifecycle-support open-source-rds-extended-support-disabled. But AWS warns about disabling it on a database "that is already past its standard support end date." In that case, "the instance or cluster automatically upgrades to the next supported major version." (RDS Extended Support)
That is a major version upgrade you did not test, and if the database is in production, it happens to production. Use this only after the application has been tested on the new version.
Step 4: stop new charges from appearing
- Set the option on purpose in code. Because the CLI and API default to enrollment, add
--engine-lifecycle-support(orEngineLifecycleSupport) to your create and restore scripts so the choice is visible. AWS notes that if you setopen-source-rds-extended-support-disabledand the end of standard support has passed, creating the instance "will always fail." That is a useful guard against new databases on old versions. (Creating a DB instance with RDS Extended Support) - Put the next dates on the calendar. PostgreSQL 14 (28 February 2027) is the next big one for many teams. Run the Step 1 command a few months ahead of each date.
When it still goes wrong
- The charge came back after an upgrade. You upgraded to a version that later reached its own end of standard support. AWS's example: a PostgreSQL 11 database upgraded to 12 on April 30, 2024 was charged again from March 1, 2025. (RDS Extended Support charges)
- The bill is bigger than one instance should cost. Count the standbys and read replicas. Each is charged.
- You bought Reserved Instances and the line is still there. RI discounts do not apply to this charge.
- Extended Support has an end too. AWS says it is available "for up to 3 years past the RDS end of standard support date." After that, RDS "will automatically upgrade your major engine version." (RDS Extended Support)
What to check first
- Which DB instances and clusters are on MySQL 5.7, MySQL 8.0, PostgreSQL 11, 12 or 13, and are they enrolled?
- How many vCPUs does each have, counting standbys and read replicas?
- Which ones can be deleted, and which need an upgrade plan?
- Is the target version far enough from its own end of standard support?
- Do your create and restore scripts set
--engine-lifecycle-supporton purpose?
Docs checked (November 18, 2026)
- Amazon RDS User Guide, Amazon RDS Extended Support with Amazon RDS (what it is, automatic enrollment, changing enrollment, forced upgrade when disabled past the date, up to 3 years)
- Amazon RDS User Guide, Amazon RDS Extended Support charges (start date, standbys, what stops the charge, charges restarting, the PostgreSQL 11 example)
- Amazon RDS User Guide, Creating a DB instance or a Multi-AZ DB cluster with RDS Extended Support (CLI and API default to enrollment, console does not, disabled option makes creation fail past the date)
- Amazon RDS User Guide, Viewing enrollment in RDS Extended Support (
EngineLifecycleSupportvalues, console column, enrollment vs charges) - Amazon RDS User Guide, Viewing support dates for engine versions and AWS CLI describe-db-major-engine-versions (
SupportedEngineLifecycles) - Amazon RDS User Guide, MySQL on Amazon RDS versions (MySQL 5.7, 8.0 and 8.4 dates)
- Amazon RDS for PostgreSQL Release Notes, Release calendar for Amazon RDS for PostgreSQL (PostgreSQL 13, 14, 16 and 17 dates)
- AWS CLI, modify-db-instance (
--engine-lifecycle-supportvalues,--engine-versionoutage note,--allow-major-version-upgrade) - Amazon RDS for MySQL pricing and Amazon RDS for PostgreSQL pricing (per vCPU-hour pricing, the Ohio and N. Virginia examples, Multi-AZ, read replicas, Reserved Instances, snapshots and restores, Blue/Green)
If AWS changes a date or price after we publish this, tell us at info@cloudskillconsulting.com and we'll update the post.
CloudSkill Consulting LLC helps teams with fixed-fee cloud projects, FinOps reviews and IT staffing. Learn more at cloudskillconsulting.com.
