6
6
Table of Contents

Amazon RDS for MySQL 8.0 reached the end of RDS Standard Support on July 31, 2026. Eligible DB instances may continue under Amazon RDS Extended Support for an additional cost. Customers should upgrade to a supported major version as soon as practical after completing compatibility, rollback and change-window validation.

Purpose

Upgrade Amazon RDS for MySQL 8.0 to 8.4 with minimal application interruption and a controlled, low-data-loss-risk procedure. The change must proceed only when replication is healthy, switchover guardrails pass, application retry behaviour is validated and the rollback mechanism has been tested

Problem Statement

Upgrading a production MySQL database across major versions is one of the most high-stakes operations of a database. Compatibility breaks, unexpected downtime, and the risk of no easy rollback can stall upgrade plans for months. Amazon Relational Database Service (Amazon RDS) for MySQL 8.0 standard support ends on July 31, 2026, and Amazon RDS for MySQL now supports long-term support (LTS) version 8.4.

Context / Background

Amazon RDS for MySQL 8.0 reached the end of RDS Standard Support on July 31, 2026. Eligible MySQL 8.0 DB instances may continue receiving support through Amazon RDS Extended Support for an additional charge, subject to AWS eligibility and supported minor-version requirements. Customers should plan migration to MySQL 8.4 rather than treating Extended Support as the long-term target.

Objective

Upgrading RDS for MySQL 8.0 to 8.4. Here, we focus on the step-by-step implementation, covering pre-upgrade compatibility checks, Blue/Green Deployments, and rollback preparation. For an overview of upgrade strategies, Extended Support costs, and key considerations

MySQL 8.0 Standard Support Ends on July 31, 2026
MySQL 8.0 Standard Support Ends on July 31, 2026

A complete upgrade workflow covering three tightly coupled phases:

  1. Pre-upgrade checks: Identify incompatibilities using the MySQL RDS built-in validation.
  2. Blue/Green Deployments: Perform the upgrade with minimal downtime using Amazon RDS Blue/Green Deployments.

Prerequisites

Blue/Green Deployments and Amazon RDS for MySQL 8.4 are available in all AWS Regions. Before you begin, make sure you have the following resources in place:

  • An Amazon RDS for MySQL 8.0 instance with automatic backups enabled.
  • An Amazon Elastic Compute Cloud (Amazon EC2 instance) instance or bastion host in the same Virtual Private Cloud for running MySQL Shell.
  • A custom DB parameter group created for MySQL 8.4.

An AWS IAM user or role with at least the following permissions for Blue/Green Deployments:

a) Create Blue/Green Deployments

  • rds:CreateBlueGreenDeployment
  • rds:AddTagsToResource
  • rds:CreateDBInstanceReadReplica

b) Switchover Blue/Green Deployments

  • rds:SwitchoverBlueGreenDeployment
  • rds:ModifyDBInstance
  • rds:PromoteReadReplica

c) Delete Blue/Green Deployments

  • rds:DeleteBlueGreenDeployment
  • rds:DeleteDBInstance
  • (For rollback) An AWS Database Migration Service (AWS DMS) replication instance, or network connectivity between the 8.4 and 8.0 instances for native replication. Make sure the security groups associated with both instances allow MySQL traffic on port 3306 between them. If using AWS DMS, see AWS DMS identity-based policy examples for IAM permission best practices.

Phase 1: Pre-Upgrade Backup

1. Take a manual snapshot

  • Open AWS Management Console →AWS RDS → Databases
  • Select the production instance (e.g., database-1)
  • Actions → Take snapshot
  • Snapshot name: db1-pre-upgrade-<YYYYMMDD>
  • Click Take snapshot and wait for status to change to Available
Snapshot Created
Snapshot Created

2. Verify automated backups

  • Select the instance → Maintenance & backups tab
  • Confirm Automated backups retention is set between 1–35 days
  • If disabled, click Modify → Backup → Backup retention period → 7 days → Continue → Apply
  • Wait for the modification to complete before proceeding

Once both the manual snapshot and automated backup retention are confirmed, you have a safe rollback point before touching anything else.

Verify automated backups

Phase 2: Blue/Green Deployments (minimize downtime)

Amazon RDS Blue/Green Deployments lets you upgrade the major engine version, without affecting production. When you’re ready, you promote the staging environment to become the new production database with downtime typically five seconds or lower for single-Region configurations. This makes Blue/Green Deployments a practical choice for major version upgrades with minimal disruption. The following sections walk you through creating Blue/Green Deployments, upgrading the green environment to MySQL 8.4, and performing the switchover.
Phase 2: Blue/Green Deployments (minimize downtime)

Create and upgrade the green environment

Create the Blue/Green Deployments: Select the same engine version as the source instance initially. This avoids a failed automatic upgrade requiring you to rebuild the entire deployment.

Create and upgrade the green environment

Review and Confirm

Review and Confirm

AWS RDS is creating blue/green deployment bg-deployment-1.

blue/green deployment
After creation completes, manually upgrade the green instance to MySQL 8.4.x. Select your pre-configured MySQL 8.4 parameter group, or the default parameter group if you’re not customizing any parameters.
Default parameters

database-1Dashboard screenshotAWS console dashboard

Switchover

Before switching over:

  • Confirm Replica Log on the green instance is near zero.
  • Check for long-running queries on the blue instance
  • Verify both environments show Available status.
  • Verify that the application isn’t caching DNS, or if it is, then the cache TTL is 5 seconds or less.
  • Set the switchover timeout to your acceptable downtime window (maximum 60 minutes). During switchover, existing connections are dropped

AWS Management Console Switchover 1
AWS Management Console switchover 2

AWS Management Console switchover 3

Pre-switchover considerations

Consider the following prior to switchover.

  • Appropriately apply IAM policies
  • IAM roles aren't copied over from the blue environment to the green environment. Make sure that your IAM policies are appropriately applied to the green environment before you switch over the blue/green deployment. 
  • Reduce costs by deleting old blue databases after switchover

We recommend that you delete the old production environment database-1 after the switchover completes if you no longer need it.

You're billed for old instances according to the standard pricing model for DB instances. 

Pre-switchover considerations

Pre-switchover conditions 2

Pre-Switchover Conditions success
The new MySQL 8.4 instance takes the original name and endpoint. RDS automatically disconnects replication at this point. Blue/Green Deployments is a one-time operation.

You can delete the Blue/Green Deployments at your convenience; doing so does not delete the old instance. If you do not need a rollback path, the upgrade is complete at this point.

  1. Open the Amazon RDS console and select your new MySQL 8.4 instance.
  2. Open the Logs & events tab.
Amazon RDS Console

Phase 3: Rollback preparation

1. Restore from Snapshot

Blue/Green Deployments preserve the previous MySQL 8.0 environment after switchover, providing a strong foundation for rollback. However, Blue/Green switchover itself is a one-time operation. To avoid losing transactions written to MySQL 8.4 after switchover, establish and validate reverse replication from MySQL 8.4 to the old MySQL 8.0 instance before treating the rollback path as ready.

Actual rollback requires stopping application writes, allowing reverse replication to catch up, validating synchronization, stopping replication safely, enabling the old environment for application writes as required, and redirecting application traffic
Rollback preparation 1

db-snapshotrds snapshot recovery

The disadvantages are:

  • restored instance gets a new endpoint
  • data written after switchover is lost
  • restore can take minutes to hours
  • application reconfiguration is required

This is considered a disaster recovery rollback, not a near-zero-downtime rollback.

2.AWS DMS

If native replication is not suitable for your environment, you can use AWS DMS as an alternative to set up the rollback path.

Because the MySQL 8.0 -old instance is set to read-only after switchover, change the read_only parameter to 0 in its parameter group before creating the task.

Step 1: Create a DMS replication instance

  • Instance class & Allocated storage: based on workload
  • Engine version: use the default
  • Virtual private cloud (VPC): use the same VPC as both the MySQL 8.4 (source) and MySQL 8.0 (target) instances. Note: If the source and target instances are in different VPCs, you need to configure VPC peering or another network connectivity option before creating the replication instance.

Step 2: Create DMS endpoints

  • Source endpoint: use the MySQL 8.4 instance endpoint (after switchover)
  • Target endpoint: use the old MySQL 8.0 -old1 instance endpoint
  • Test both endpoint connections from the replication instance before proceeding

Step 3: Create a CDC-only DMS task

  • Migration type: CDC only (ongoing replication)
  • CDC start position: enter the binlog position from the switchover event (Logs & events → Recent events on the new MySQL 8.4 instance)
  • Include LOB columns in replication: if your tables contain LOB columns, consider using Limited LOB mode for faster replication. This mode truncates LOB value that exceeds the configured Maximum LOB size, so you need to set it appropriately.
  • Maximum LOB size (KB): query the maximum LOB size in your instance first, then set accordingly:

endpoints

Create endpoint

Create task

Settings RDS console
Single AZ deployment

task creationtask selectionstart tasktask management
12
Let's discuss your cloud challenges and see how CloudKeeper can solve them all!
Meet the Author
  • Vikas Singh
    DevOps Engineer

    Vikas specializes in AWS cloud infrastructure, DevOps engineering, and automation, with a focus on building reliable, scalable, and secure cloud environments.

No Comments Yet
Leave a Comment
Certified. Trusted. Industry Recognized.

Stop paying for cloud tools. Start paying for outcomes.

Get Started with CloudKeeper