AWS AURORA MYSQL VERSION UPGRADE

Perform major version in-place upgrade by modifying the cluster on green environment.Perform fast database clone from the older Aurora major version (blue environment) and create it as an older Aurora major version (green environment).The updated architecture includes the following steps: The following diagram illustrates this updated architecture. However, for the Aurora MySQL major version upgrade procedure with minimum database downtime, you can use database clone and in-place upgrade process (using Aurora MySQL 1.22.3 or higher version). The following diagram illustrates this architecture.įor more information about cloning databases, see Creating an Aurora clone through the AWS Management Console. During the database switchover process, redirect the production traffic from the blue to green environment.During downtime, stop the application and make sure all the changes are applied on the green environment.

Apply the changes on the green environment and test the application.

The MySQL binary log replication is the key process to replicate data between these two environments and allows you to perform database environment switchover with minimum downtime.įor generic database change management processes such as minor version upgrades, application changes, and data reorganization, you can use blue-green deployment with the fast database cloning or snapshot feature, but fast database cloning is faster to create a database copy quickly, easily, and cost-effectively. After the green environment is ready and tested, the production traffic is redirected from the blue to green environment.

The blue environment database changes made by the production applications in the blue environment are continually replicated to the green environment using the MySQL binary log replication. The desired change is applied on the green database environment only.īlue-green deployment allows you to make these database changes on the green environment without impacting the blue environment, and test with the current production data set and rollback capabilities. In parallel, the green environment is staged running a different version, with schema changes like new or modified indexes on a very large table. In a blue-green deployment, the blue environment represents the current database version serving production traffic. You can also use this solution for any major database reorganization or changes with minimal impact on the primary database. You can use blue-green deployment for an Aurora MySQL major version upgrade for different types of Aurora MySQL clusters that support binary logs, including Aurora MySQL Global Database. This is useful for database administrators or DevOps team members responsible for the Aurora MySQL upgrades. However, the time needed for an in-place upgrade can vary depending on the properties of your schema and how busy the cluster is.This post shows how you can perform a major upgrade for Aurora MySQL with minimal downtime using a blue-green deployment. Aurora MySQL started supporting major version upgrade in-place from Aurora MySQL 1.22.3 or higher version. As is common for open-source MySQL databases, you must manually perform a major version upgrade. MySQL database major version upgrades can contain database changes that may not be backward compatible with existing applications. An Aurora DB cluster consists of one or more DB instances connected to a shared and distributed Aurora storage volume. Performing major version upgrades for Amazon Aurora MySQL with minimum downtime Amazon Aurora combines the performance and availability of commercial databases with the simplicity and cost-effectiveness of open-source databases.

Aws aurora mysql version