Aurora MySQL database engine updates 2024-03-15 (version 3.04.2, compatible with MySQL 8.0.28) - Amazon Aurora

Aurora MySQL database engine updates 2024-03-15 (version 3.04.2, compatible with MySQL 8.0.28)

Version: 3.04.2

Aurora MySQL 3.04.2 is generally available. Aurora MySQL 3.04 versions are compatible with MySQL 8.0.28. For more information on community changes that have occurred, see MySQL 8.0 Release Notes.

For details of the new features in Aurora MySQL version 3, see Aurora MySQL version 3 compatible with MySQL 8.0. For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see Comparison of Aurora MySQL version 2 and Aurora MySQL version 3. For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see Comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition.


This version is designated as a long-term support (LTS) release. For more information, see Aurora MySQL long-term support (LTS) releases in the Amazon Aurora User Guide.

We recommend that you don't set the AutoMinorVersionUpgrade parameter to true (or enable Auto minor version upgrade in the AWS Management Console) for LTS versions. Doing so could lead to your DB cluster being upgraded to a non-LTS version such as 3.05.2.

Currently supported Aurora MySQL releases are 2.07.9, 2.7.10, 2.11.*, 2.12.*, 3.03.*, 3.04.*, 3.05.*, and 3.06.*.

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using Amazon RDS Blue/Green Deployments from any currently available Aurora MySQL version 2 cluster into an Aurora MySQL version 3.04.2 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see Upgrade planning for Aurora MySQL version 3 in the Amazon Aurora User Guide. For general information about Aurora MySQL upgrades, see Upgrading Amazon Aurora MySQL DB clusters in the Amazon Aurora User Guide.

For troubleshooting information, see Troubleshooting upgrade issues with Aurora MySQL version 3.

If you have any questions or concerns, AWS Support is available on the community forums and through AWS Support. For more information, see Maintaining an Amazon Aurora DB cluster in the Amazon Aurora User Guide.


Fixed security issues and CVEs:

The following CVE fixes are included in this release:

Availability improvements:

  • Fixed an issue where a read replica DB instance can't be launched successfully when there's high workload in the writer DB instance.

  • Fixed an issue where an Aurora MySQL writer DB instance can fail over due to a defect in the component that communicates with Aurora storage. The defect occurs as a result of a breakdown in the communication between the DB instance and underlying storage following a software update.

  • Fixed an issue that can cause a database instance restart when running SHOW STATUS and PURGE BINARY LOGS statements concurrently. PURGE BINARY LOGS is a managed statement that is run to honor the user-configured binlog retention period.

  • Fixed an issue that, during the restart of a database instance, can cause an additional restart.

  • Fixed an issue with lock contention caused by an audit logging thread that can lead to high CPU utilization and client application timeouts.

  • Fixed an issue where an Aurora MySQL database instance can experience multiple restarts during instance startup while large rollback segments are initialized.

  • Fixed an issue that can cause a DB instance to restart while running a query that references an aggregate function.

General improvements:

  • Fixed an issue that can cause a parallel query to fail due to transient network issues while reading data from the Aurora DB cluster volume

  • Fixed an issue where the user is unable to interrupt any query or set session timeouts for performance_schema queries.

  • Fixed an issue where binary log (binlog) replication configured to use custom SSL certificates (mysql.rds_import_binlog_ssl_material) could fail when the replication instance is undergoing a host replacement.

  • Fixed an issue related to audit log file management that can cause log files to be inaccessible for download or rotation, and in some cases increase CPU usage.

  • Optimized AUTO_INCREMENT key recovery to reduce the completion time for restoring snapshots, performing point-in-time recovery, and cloning DB clusters with large numbers of tables in the database.

  • Fixed an issue where SQL statements referring to some performance_schema tables can return an error due to these tables being missing after migrating from Community MySQL to Aurora MySQL versions 3.04.0 and 3.04.1.

  • Fixed an issue where small read replica instances can experience increased replication lag after upgrading from Aurora MySQL versions lower than 2.11.*.

  • Fixed an issue that can cause duplicate key errors for AUTO_INCREMENT columns using descending indices after a snapshot restore, backtrack, or database cloning operation.

  • Fixed an issue that can cause modifications of the table_open_cache database parameter not to take effect until the DB instance is restarted.

  • Fixed an issue where the reader DB instance is unable to open a table, with ERROR 1146. This issue occurs when running certain types of online Data Definition Language (DDL) statements while the INPLACE algorithm is being used on the writer DB instance.

  • Fixed an issue to avoid an instance restart during Aurora Serverless v2 scaling when the internal monitoring process erroneously submits duplicate scaling requests.

  • Fixed an issue that can cause a database restart when connected binary log (binlog) consumers are using duplicate binlog replication server IDs.

Upgrades and migrations:

  • Fixed an issue that can cause major version upgrades to Aurora MySQL version 3 to fail due to the presence of orphaned entries for already deleted tablespaces in InnoDB system tables in Aurora MySQL version 2.

Integration of MySQL Community Edition bug fixes

This release includes all community bug fixes up to and including 8.0.28, in addition to the following. For more information, see MySQL bugs fixed by Aurora MySQL 3.x database engine updates.

  • Fixed an issue where cache line value can be calculated incorrectly, causing a failure during database restart on Graviton-based instances. (Community Bug Fix #35479763)

  • Repeated running of a stored routine, having as a subquery a SELECT statement containing multiple AND, OR, or XOR conditions, led to excessive consumption and possibly eventual exhaustion of virtual memory. (Community Bug Fix #33852530)