# Database engine updates for Amazon Aurora MySQL version 3
<a name="AuroraMySQL.Updates.30Updates"></a>

The following are database engine updates for Amazon Aurora MySQL version 3.

**Topics**<a name="aurora_3x_updates"></a>
+ [Aurora MySQL database engine updates 2026-02-17 (version 3.12.0, compatible with MySQL 8.0.44)](AuroraMySQL.Updates.3120.md)
+ [Aurora MySQL database engine updates 2025-12-16 (version 3.11.1, compatible with MySQL 8.0.43)](AuroraMySQL.Updates.3111.md)
+ [Aurora MySQL database engine updates 2025-11-13 (version 3.11.0, compatible with MySQL 8.0.43)](AuroraMySQL.Updates.3110.md)
+ [Aurora MySQL database engine updates 2026-03-30 (version 3.10.4, compatible with MySQL 8.0.42)](AuroraMySQL.Updates.3104.md)
+ [Aurora MySQL database engine updates 2026-01-02 (version 3.10.3, compatible with MySQL 8.0.42)](AuroraMySQL.Updates.3103.md)
+ [Aurora MySQL database engine updates 2025-11-20 (version 3.10.2, compatible with MySQL 8.0.42)](AuroraMySQL.Updates.3102.md)
+ [Aurora MySQL database engine updates 2025-09-30 (version 3.10.1, compatible with MySQL 8.0.42)](AuroraMySQL.Updates.3101.md)
+ [Aurora MySQL database engine updates 2025-07-31 (version 3.10.0, compatible with MySQL 8.0.42)](AuroraMySQL.Updates.3100.md)
+ [Aurora MySQL database engine updates 2025-05-14 (version 3.09.0, compatible with MySQL 8.0.40)](AuroraMySQL.Updates.3090.md)
+ [Aurora MySQL database engine updates 2025-04-07 (version 3.08.2, compatible with MySQL 8.0.39)](AuroraMySQL.Updates.3082.md)
+ [Aurora MySQL database engine updates 2025-02-17 (version 3.08.1, compatible with MySQL 8.0.39)](AuroraMySQL.Updates.3081.md)
+ [Aurora MySQL database engine updates 2024-11-18 (version 3.08.0, compatible with MySQL 8.0.39)](AuroraMySQL.Updates.3080.md)
+ [Aurora MySQL database engine updates 2024-07-23 (version 3.07.1) (Deprecated)](AuroraMySQL.Updates.3071.md)
+ [Aurora MySQL database engine updates 2024-06-04 (version 3.07.0) (Deprecated)](AuroraMySQL.Updates.3070.md)
+ [Aurora MySQL database engine updates 2024-06-26 (version 3.06.1) (Deprecated)](AuroraMySQL.Updates.3061.md)
+ [Aurora MySQL database engine updates 2024-03-07 (version 3.06.0) (Deprecated)](AuroraMySQL.Updates.3060.md)
+ [Aurora MySQL database engine updates 2024-01-31 (version 3.05.2) (Deprecated)](AuroraMySQL.Updates.3052.md)
+ [Aurora MySQL database engine updates 2023-11-21 (version 3.05.1) (Deprecated)](AuroraMySQL.Updates.3051.md)
+ [Aurora MySQL database engine updates 2023-10-30 (version 3.05.0.1) (Deprecated)](AuroraMySQL.Updates.30501.md)
+ [Aurora MySQL database engine updates 2023-10-25 (version 3.05.0) (Deprecated)](AuroraMySQL.Updates.3050.md)
+ [Aurora MySQL database engine updates 2026-01-02 (version 3.04.6, compatible with MySQL 8.0.28)](AuroraMySQL.Updates.3046.md)
+ [Aurora MySQL database engine updates 2025-05-05 (version 3.04.4, compatible with MySQL 8.0.28)](AuroraMySQL.Updates.3044.md)
+ [Aurora MySQL database engine updates 2024-06-26 (version 3.04.3, compatible with MySQL 8.0.28)](AuroraMySQL.Updates.3043.md)
+ [Aurora MySQL database engine updates 2024-03-15 (version 3.04.2, compatible with MySQL 8.0.28)](AuroraMySQL.Updates.3042.md)
+ [Aurora MySQL database engine updates 2023-11-13 (version 3.04.1, compatible with MySQL 8.0.28)](AuroraMySQL.Updates.3041.md)
+ [Aurora MySQL database engine updates 2023-07-31 (version 3.04.0) , compatible with MySQL 8.0.28)](AuroraMySQL.Updates.3040.md)
+ [Aurora MySQL database engine updates 2023-12-08 (version 3.03.3) (Deprecated)](AuroraMySQL.Updates.3033.md)
+ [Aurora MySQL database engine updates 2023-08-29 (version 3.03.2) (Deprecated)](AuroraMySQL.Updates.3032.md)
+ [Aurora MySQL database engine updates 2023-05-11 (version 3.03.1) (Deprecated)](AuroraMySQL.Updates.3031.md)
+ [Aurora MySQL database engine updates 2023-03-01 (version 3.03.0) (Deprecated)](AuroraMySQL.Updates.3030.md)
+ [Aurora MySQL database engine updates 2023-04-17 (version 3.02.3) (Deprecated)](AuroraMySQL.Updates.3023.md)
+ [Aurora MySQL database engine updates 2022-11-18 (version 3.02.2) (Deprecated)](AuroraMySQL.Updates.3022.md)
+ [Aurora MySQL database engine updates 2022-09-07 (version 3.02.1) (Deprecated)](AuroraMySQL.Updates.3021.md)
+ [Aurora MySQL database engine updates 2022-04-20 (version 3.02.0) (Deprecated)](AuroraMySQL.Updates.3020.md)
+ [Aurora MySQL database engine updates 2022-04-15 (version 3.01.1) (Deprecated)](AuroraMySQL.Updates.3011.md)
+ [Aurora MySQL database engine updates 2021-11-18 (version 3.01.0) (Deprecated)](AuroraMySQL.Updates.3010.md)

# Aurora MySQL database engine updates 2026-02-17 (version 3.12.0, compatible with MySQL 8.0.44)
<a name="AuroraMySQL.Updates.3120"></a><a name="3.12.0"></a>

**Version:** 3.12.0

Aurora MySQL 3.12.0 is generally available. Aurora MySQL 3.12 versions are compatible with MySQL 8.0.44. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

You can perform an in-place upgrade [leveraging Zero Downtime Patching (ZDP)](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.ZDP.html), restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.12.0 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3120.Improvements"></a>

**Security fixes**
+ Fixed an issue which can cause some SQL statements to not get logged in the audit log.
+ Fixed caching\$1sha2\$1password plugin to ensure Aurora MySQL reader and writer instances validate updated passwords consistently.

**Medium CVEs:**
+ [CVE-2025-53040](https://www.cve.org/CVERecord?id=CVE-2025-53040)
+ [CVE-2025-53042](https://www.cve.org/CVERecord?id=CVE-2025-53042)
+ [CVE-2025-53044](https://www.cve.org/CVERecord?id=CVE-2025-53044)
+ [CVE-2025-53045](https://www.cve.org/CVERecord?id=CVE-2025-53045)
+ [CVE-2025-53053](https://www.cve.org/CVERecord?id=CVE-2025-53053)
+ [CVE-2025-53054](https://www.cve.org/CVERecord?id=CVE-2025-53054)
+ [CVE-2025-53062](https://www.cve.org/CVERecord?id=CVE-2025-53062)
+ [CVE-2025-53069](https://www.cve.org/CVERecord?id=CVE-2025-53069)

**Availability improvements:**
+ Fixed an issue which can cause a database instance restart when the lock table is full during semi-consistent read.
+ Fixed an issue in binlog recovery that could cause binlog replica instance to restart when using `aurora_in_memory_relaylog` with multi-threaded replication.
+ Fixed an issue which could cause the writer instance to restart when global write forwarding or local write forwarding is being disabled.
+ Fixed an issue where excessively large thread\$1stack configurations could prevent Aurora MySQL server bootup during restarts or upgrades. Aurora MySQL server now automatically resets thread\$1stack to the engine default value(1 MB) when it exceeds system memory, preventing startup failures.
+ Fixed an issue which, could cause an engine restart when running `KILL` after running `EXPLAIN FOR CONNECTION` on a running parallel query.
+ Fixed issue that can force parallel query on a random query and causes engine restart if this query is forcibly terminated.
+ Fixed an issue which prevented users with CONNECTION\$1ADMIN or SUPER privileges from performing an additional connection beyond max\$1connections limit, as supported in MySQL Community Edition.
+ Fixed an issue that can cause a restart on a binary log (binlog) replica when processing a large number of relay log files during [relay log recovery](https://dev.mysql.com/doc/refman/8.0/en/replication-solutions-unexpected-replica-halt.html).
+ Fixed an issue that causes the writer DB instance to restart when running a parallel query on a reader DB instance.
+ Fixed an issue that, in rare conditions, can disable binary logging when an error occurs during commit of a large transaction.
+ Fixed an issue that can cause read replicas to restart in the event of certain rare transaction commit orders on the writer DB instance.
+ Fixed an issue that can lead to a database restart when [scheduled events](https://dev.mysql.com/doc/refman/8.4/en/events-overview.html) are aborted during execution on instances that have enhanced binlog enabled.
+ Fixed an issue where database instances using multi TiB storage sizes, may experience increased downtime during restart due to InnoDB bufferpool validation failures.

**General improvements:**
+ Excluded a community change introduced in MySQL 8.0.44 where failed connection attempts unexpectedly added rows to performance\$1schema tables causing excessive memory consumption. Ref community [Bug\$1119766](https://bugs.mysql.com/bug.php?id=119766)
+ Fixed an issue affecting Aurora specific replication stored procedures when configuring binlog replication on instances with custom collation settings.
+ Fixed an issue to reduce CPU overhead while establishing Encryption in Transit between the database engine and the storage layer.
+ Improved write IOPS performance when system variable innodb\$1flush\$1log\$1at\$1trx\$1commit is set to 0.
+ Automatically disable aurora\$1oom\$1response actions (except print, if configured) when aurora\$1oom\$1response fails to resolve memory pressure after a threshold time (in the order of few mins).
+ Resolved a race condition that could cause incorrect page reads from the buffer pool during Aurora Serverless scale-down operations or during page eviction from the buffer pool. Ref community [Bug\$1116305](https://bugs.mysql.com/bug.php?id=116305).
+ Fixed an out-of-memory (OOM) issue that could cause reader restarts when executing privilege-related commands on the writer.
+ The following privileges have been added to the `rds_superuser_role`: `FLUSH_OPTIMIZER_COSTS, FLUSH_STATUS, FLUSH_TABLES, FLUSH_USER_RESOURCES`. For information about the `rds_superuser_role`, please see the [Amazon Master User Accounts with Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.MasterAccounts.html) documentation. For more information on these dynamic privileges, please see the [MySQL](https://dev.mysql.com/doc/refman/8.0/en/flush.html) documentation.
+ Fixed an issue causing inaccurate tracking of parallel query requests while running `EXPLAIN ANALYZE` statements where `Aurora_pq_request_in_progress` counter was not updated accurately.
+ Fixed an issue where a preserved connection is handled incorrectly during zero-downtime patching (ZDP)/zero-downtime restart (ZDR) which can lead to the client waiting indefinitely for a query to complete.
+ Fix the issue where the row becomes unreadable through the spatial index during an update.
+ Fixed an issue where a query containing an optimizer hint which was aborted during a zero-downtime restart (ZDR) or zero-downtime patching (ZDP) operation may be incorrectly handled.
+ Fix the issue where the commit latency is not measured when innodb\$1flush\$1log\$1at\$1trx\$1commit is set to 0.
+ Introduced optimizations to reduce memory usage during logical [data dictionary](https://dev.mysql.com/doc/refman/8.0/en/data-dictionary.html) recovery when there are a large number of tables.
+ Fixed an issue that caused the `SHOW BINARY LOGS` command to take longer to execute on a cluster where Enhanced Binlog is enabled or was previously enabled. This issue could also cause increased commit latency if multiple `SHOW BINARY LOGS` commands were running concurrently.
+ Fix the memory issue associated with the default roles of the view definer.
+ Fixed an issue that can cause failure in completing the process of disabling the "write forwarding" feature.
+ Fixed an issue which can cause a writer database instance to restart when a reader instance using write forwarding executes a DML statement that contains a timestamp value and the time\$1zone database parameter is set to "UTC".
+ Fixed an issue, which in rare cases, caused intermittent unavailability of an Aurora Read Replica or table definition inconsistencies with error 'Table does not exist' on the replica due to concurrent read queries on the replica and DDL operations on the writer.
+ Fixed an issue which may cause an incomplete result set when executing queries involving LEFT- or RIGHT-JOIN operations using the hash-join algorithm with parallel query.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3120.Patches"></a>

This release includes all community bug fixes up to and including 8.0.44. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](AuroraMySQL.Updates.MySQLBugs.md#AuroraMySQL.Updates.MySQLBugs.v3).
+ Fixed an issue where a query of the form `SELECT 1 FROM t WHERE CAST(a AS UNSIGNED INTEGER) = 1 AND a = (SELECT 1 FROM t)` leads to an assertion failure in `item_func.cc`. (Community Bug Fix \$136128964)
+ Fixed an issue that resolves the deadlock when FLUSH STATUS, COM\$1CHANGE\$1USER and SHOW PROCESS LIST are executed concurrently. (Bug\$135218030)

# Aurora MySQL database engine updates 2025-12-16 (version 3.11.1, compatible with MySQL 8.0.43)
<a name="AuroraMySQL.Updates.3111"></a><a name="3111"></a><a name="3.11.1"></a>

**Version:** 3.11.1

Aurora MySQL 3.11.1 is generally available. Aurora MySQL 3.11 versions are compatible with MySQL 8.0.43. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

You can perform an in-place upgrade [leveraging Zero Downtime Patching (ZDP)](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.ZDP.html), restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.11.1 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, Support is available on the community forums and through [Support](https://aws.amazon.com/support). For more information, see [Maintaining an Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3111.Improvements"></a>

**General improvements**
+ Fixed an issue which can cause database cluster creates or restores to take a long time to complete.
+ Reduced CPU usage overhead while establishing Encryption in Transit between the database instance and the storage layer.
+ Fixed an issue which can cause some SQL statements to not get logged in the audit log.

# Aurora MySQL database engine updates 2025-11-13 (version 3.11.0, compatible with MySQL 8.0.43)
<a name="AuroraMySQL.Updates.3110"></a><a name="3110"></a><a name="3.11.0"></a>

**Version:** 3.11.0

Aurora MySQL 3.11.0 is generally available. Aurora MySQL 3.11 versions are compatible with MySQL 8.0.43. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

You can perform an in-place upgrade leveraging zero-downtime patching (ZDP), restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.11.0 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, Support is available on the community forums and through [Support](https://aws.amazon.com/support). For more information, see [Maintaining an Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3110.Improvements"></a>

**Fixed security issues and CVEs**

**Medium CVEs:**
+ [CVE-2025-50077](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50077)
+ [CVE-2025-50078](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50078)
+ [CVE-2025-50079](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50079)
+ [CVE-2025-50080](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50080)
+ [CVE-2025-50082](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50082)
+ [CVE-2025-50083](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50083)
+ [CVE-2025-50084](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50084)
+ [CVE-2025-50085](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50085)
+ [CVE-2025-50086](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50086)
+ [CVE-2025-50087](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50087)
+ [CVE-2025-50088](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50088)
+ [CVE-2025-50091](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50091)
+ [CVE-2025-50092](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50092)
+ [CVE-2025-50093](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50093)
+ [CVE-2025-50094](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50094)
+ [CVE-2025-50096](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50096)
+ [CVE-2025-50097](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50097)
+ [CVE-2025-50099](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50099)
+ [CVE-2025-50101](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50101)
+ [CVE-2025-50102](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50102)
+ [CVE-2025-53023](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-53023)

**Low CVEs:**
+ [CVE-2025-50098](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50098)
+ [CVE-2025-50100](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50100)
+ [CVE-2025-50104](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-50104)

**Availability improvements**
+ Fixed an issue in logical recovery with `aurora_enhanced_binlog` enabled that could prevent database restarts in case of aborted transactions.
+ Fixed an issue that could cause the writer instance to restart when global write forwarding or local write forwarding is being disabled.
+ Fixed an issue that could cause writer to become unresponsive when write forwarding is being disabled while two or more replicas are forwarding requests.
+ Fixed an issue that could cause an engine restart when running `KILL <query-id>` after running `EXPLAIN FOR CONNECTION <query-id>` on a running parallel query.
+ Fixed an issue where out-of-memory (OOM) avoidance wasn't persisting the configured `aurora_oom_response` DB parameter value after database restart.
+ Fixed an issue that prevented users with `CONNECTION_ADMIN` or `SUPER` privileges from performing an additional connection beyond `max_connections` limit, as supported in MySQL Community Edition.
+ Fixed an issue with Aurora Serverless V2 scaling that resulted in DB instance restarts by preventing critical memory pages from being swapped out.
+ Fixed an issue that could cause Aurora MySQL Serverless v2 instances to restart when the `innodb_purge_threads` parameter was manually configured to a value different from the default. The `innodb_purge_threads` parameter is now automatically managed for Aurora Serverless v2 instances and can't be modified.
+ Fixed an issue that could cause a reader instance's restart to fail when the writer is running a large number of DDL operations.
+ Fixed an issue that could cause the writer instance to become unresponsive if reader instances restart while using Global Write Forwarding or Local Write Forwarding.
+ Fixed an issue that could cause engine restart during zero-downtime patching (ZDP)/zero-downtime restart (ZDR), when preserving SSL/TLS connections with active transactions.
+ Fixed an issue that, under rare conditions, could cause changes on the writer instance to be sent to the reader instance in an order that's incompatible with the query-processing threads. This can lead to a deadlock between query-processing thread and replication-apply thread, which in turn can cause the reader instance to restart.
+ Fixed an issue to prevent unnecessary database server restarts that were occurring due to the monitoring agent's incorrect health assessment.

**General improvements**
+ Fixed an issue where writes to the database may stall while executing a long running transaction leading to a database restart or a major version upgrade to fail.
+ Fixed an issue with replicas incorrectly being restarted when joining the writer.
+ Optimized database performance for database instances with large Aurora Storage volumes.
+ Fixed an issue in the range optimizer where constant expressions weren't recognized when calculating range bounds. (Community Bug \$1112737)
+ Fixed an issue where exporting a DB snapshot to Amazon S3 performs slower when exporting tables containing JSON columns with null values.
+ Fixed an issue where temporary binary log files weren't being properly cleaned up after transaction rollbacks when using binary logging. This fix prevents storage consumption from retained temporary files and in certain cases can also prevent anomalies in the binary log files.
+ Improved write IOPS performance when system variable `innodb_flush_log_at_trx_commit` is set to `0`.
+ Fixed an issue where zero downtime patching (ZDP) / zero downtime restart (ZDR) could result in DB instance restart while restoring warnings with invalid error codes.
+ Automatically disable `aurora_oom_response` actions (except print, if configured) when `aurora_oom_response` fails to resolve memory pressure after a threshold time (in the order of few mins).
+ Fixed an issue where a column with partial JSON updates fails parallel export causing internal fallback to a much slower Amazon RDS export.
+ Fixed an issue that can cause memory management issues when parallel query operations on the table with the blob fields.
+ Fixed an issue that could cause the `Previous_gtids` binlog event to exclude certain GTIDs with Enhanced Binlog enabled and `gtid_mode` set to `ON` or `ON_PERMISSIVE`.
+ Fixed an issue that causes unexpected "Internal write forwarding error" on reader instances when write forwarding is enabled.
+ Resolved a race condition that could cause incorrect page reads from the buffer pool during Aurora Serverless scale-down operations or during page eviction from the buffer pool. Ref community [Bug\$1116305](https://bugs.mysql.com/bug.php?id=116305).
+ Fixed an issue where exporting a DB snapshot to Amazon S3 will be slower when exporting tables containing secondary indices with generated expressions.
+ Fixed an issue causing inaccurate `AbortedClients` metrics when multiple connections terminate unexpectedly.
+ Added a new global variable `aurora_lambda_request_timeout` to allow users configure AWS Lambda request timeouts (default: 10 seconds). For more information on invoking a Lambda function from an Aurora MySQL DB cluster see [Invoking a Lambda function from an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html).
+ Fixed an issue where local write forwarding stops working after the database instance restarted with zero-downtime restart.
+ Fixed an issue that could cause a database instance restart operation to fail if `max_user_connections` is set to a low value.
+ Improved parallel export performance by optimizing the bootstrap process for large volumes (>64 TB), reducing overall export operation time.
+ Fixed an issue that could cause the writer instance to restart when performing `ALTER TABLE` in parallel with read queries.
+ Fixed an issue that can cause DB cluster exports to take significantly longer than expected when there are tables larger than 14 TB.
+ Fixed an issue that caused inaccurate tracking of parallel query requests while running `EXPLAIN ANALYZE` statements where `Aurora_pq_request_in_progress` counter wasn't updated accurately.
+ Fixed an issue that, under uncommon conditions, can cause the database instance to restart when the database volume is close to its maximum allowed size.
+ Fixed an issue that can cause a database instance restart when restoring connections during zero-downtime restart and zero-downtime patching.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3110.Patches"></a>

This release includes all community bug fixes up to and including 8.0.43. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](AuroraMySQL.Updates.MySQLBugs.md#AuroraMySQL.Updates.MySQLBugs.v3).
+ Fixed an issue where a query of the form `SELECT 1 FROM t WHERE CAST(a AS UNSIGNED INTEGER) = 1 AND a = (SELECT 1 FROM t)` leads to an assertion failure in `item_func.cc`. (Community Bug Fix \$136128964)
+ A query of the form `SELECT 1 FROM t WHERE CAST(a AS UNSIGNED INTEGER) = 1 AND a = (SELECT 1 FROM t)` led to an assertion in `item_func.cc`. (Bug \$136128964)

For more information on community changes, see [MySQL 8.0.43 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-43.html).

# Aurora MySQL database engine updates 2026-03-30 (version 3.10.4, compatible with MySQL 8.0.42)
<a name="AuroraMySQL.Updates.3104"></a><a name="3104"></a><a name="3.10.4"></a>

**Version:** 3.10.4

Aurora MySQL 3.10.4 is generally available. Aurora MySQL 3.10 versions are compatible with MySQL 8.0.42. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

You can perform an in-place upgrade leveraging [Zero Downtime Patching (ZDP)](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.ZDP.html), restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.10.4 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, Support is available on the community forums and through [Support](https://aws.amazon.com/support). For more information, see [Maintaining an Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3104.Improvements"></a>

 **General improvements:** 
+ Fixed an issue where the first Zero-downtime restart (ZDR) after enabling Global Write Forwarding could fail to preserve existing connections on the writer. 

 **Availability improvements:** 
+ Fixed an issue which can cause a database instance restart when the lock table is full during semi-consistent read. 
+ Fixed an issue in binlog recovery that could cause binlog replica instance to restart when using `aurora\$1in\$1memory\$1relaylog` with multi-threaded replication. 
+ Fixed an issue which could cause the writer to restart when a reader restarts while local or global write forwarding is enabled. 
+ Fixed an issue with improper handling of empty responses during connection loss with storage nodes. 

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3104.BugFixes"></a>

 This release includes all community bug fixes up to and including 8.0.42. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](AuroraMySQL.Updates.MySQLBugs.md#AuroraMySQL.Updates.MySQLBugs.v3). 
+ InnoDB: Fixed an issue relating to DELETE operations. (Bug \$137478594)

# Aurora MySQL database engine updates 2026-01-02 (version 3.10.3, compatible with MySQL 8.0.42)
<a name="AuroraMySQL.Updates.3103"></a><a name="3103"></a><a name="3.10.3"></a>

**Version:** 3.10.3

Aurora MySQL 3.10.3 is generally available. Aurora MySQL 3.10 versions are compatible with MySQL 8.0.42. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

You can perform an in-place upgrade leveraging [Zero Downtime Patching (ZDP)](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.ZDP.html), restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.10.3 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, Support is available on the community forums and through [Support](https://aws.amazon.com/support). For more information, see [Maintaining an Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3103.Improvements"></a>

 **General improvements:** 
+ Reduced CPU usage overhead while establishing Encryption in Transit between the database instance and the storage layer.
+ Fixed an issue which can cause some SQL statements to not get logged in the audit log.

# Aurora MySQL database engine updates 2025-11-20 (version 3.10.2, compatible with MySQL 8.0.42)
<a name="AuroraMySQL.Updates.3102"></a><a name="3102"></a><a name="3.10.2"></a>

**Version:** 3.10.2

Aurora MySQL 3.10.2 is generally available. Aurora MySQL 3.10 versions are compatible with MySQL 8.0.42. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

You can perform an in-place upgrade leveraging [Zero Downtime Patching (ZDP)](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.ZDP.html), restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.10.2 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, Support is available on the community forums and through [Support](https://aws.amazon.com/support). For more information, see [Maintaining an Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3102.Improvements"></a>

 **Availability improvements:** 
+ Fixed an issue which can cause engine restart during Zero-downtime patching (ZDP)/Zero-downtime restart (ZDR), when preserving SSL/TLS connections with active transactions.
+ Fixed an issue which, can cause an engine restart when running `KILL <query-id>` after running `EXPLAIN FOR CONNECTION <query-id>` on a running Parallel Query.
+ Fixed an issue which could cause writer to become unresponsive when write forwarding is being disabled while two or more replicas are forwarding requests.
+ Fixed an issue which could cause the writer instance to restart when global write forwarding or local write forwarding is being disabled.

 **General improvements:** 
+ Fixed an issue causing inaccurate tracking of Parallel Query requests while running `EXPLAIN ANALYZE` statements where `Aurora_pq_request_in_progress` counter was not updated accurately.
+ Automatically disable `aurora_oom_response` actions (except print, if configured) when `aurora_oom_response` fails to resolve memory pressure after a threshold time (in the order of few mins).
+ Improved write IOPS performance when system variable `innodb_flush_log_at_trx_commit` is set to `0`.
+ Fixed an issue with replicas incorrectly being restarted when joining the writer.
+ Fixed an issue where writes to the database may stall while executing a long running transaction leading to a database restart or a major version upgrade to fail.

# Aurora MySQL database engine updates 2025-09-30 (version 3.10.1, compatible with MySQL 8.0.42)
<a name="AuroraMySQL.Updates.3101"></a><a name="3.10.1"></a><a name="3.10.1"></a>

**Version:** 3.10.1

Aurora MySQL 3.10.1 is generally available. Aurora MySQL 3.10 versions are compatible with MySQL 8.0.42. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

You can perform an in-place upgrade [leveraging Zero Downtime Patching (ZDP)](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.ZDP.html), restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.10.1 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Upgrading.Troubleshooting.html) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3101.Improvements"></a>

**Availability improvements:**
+ Fixed an issue with the page latching order sent to reader instances. It can cause the reader instance to restart due to a deadlatch when running SELECT queries over tables being updated by its writer.
+ Fixed an issue that could cause a reader instance's restart to fail when the writer is running a large number of DDL operations.
+ Fixed an issue which could cause Aurora MySQL Serverless v2 instances to restart when the innodb\$1purge\$1threads parameter was manually configured to a value different from the default. The innodb\$1purge\$1threads parameter is now automatically managed for Aurora Serverless v2 instances and cannot be modified.
+ Fixed an issue with Aurora Serverless V2 scaling that resulted in DB instance restarts by preventing critical memory pages from being swapped out.
+ Fixed an issue where Aurora out of memory (OOM) avoidance wasn't persisting the configured aurora\$1oom\$1response DB parameter value after database restart.
+ Fixed a race condition which could cause availability issue after a failover in Multi-AZ clusters.
+ Fixed an issue in logical recovery with aurora\$1enhanced\$1binlog enabled that could prevent database restarts in case of aborted transactions.
+ Resolved an issue where database instances could become unresponsive during Parallel Query (PQ) workloads.
+ Fixed an issue which prevented users with CONNECTION\$1ADMIN or SUPER privileges from performing an additional connection beyond max\$1connections limit, as supported in MySQL Community Edition.

**General improvements:**
+ Fixed an issue that can cause continuous database server restarts when the volume was allowed to grow to its maximum size due to certain types of queries being mistakenly allowed after the volume was greater than a certain threshold.
+ Fixed an issue that can cause the writer instance to become irresponsive if reader instances restart while using Global Write Forwarding or Local Write Forwarding.
+ Fixed an issue that could cause the writer instance to restart when performing ALTER TABLE in parallel with read queries.
+ Fixed an issue to improve availability with large volume (> 64 TB) bootstrapping during the parallel export operation.
+ Fixed an issue that could cause a database instance restart operation to fail if max\$1user\$1connections is set to a low value.
+ Fixed an issue causing inaccurate AbortedClients metrics when multiple connections terminate unexpectedly.
+ Resolved a race condition that could cause incorrect page reads from the buffer pool during Aurora Serverless scale-down operations or during page eviction from the buffer pool. Ref [community Bug\$1116305](https://bugs.mysql.com/bug.php?id=116305).
+ Fixed an issue that causes unexpected "Internal write forwarding error" on reader instances when write forwarding is enabled.
+ Fixed an issue which could cause the Previous\$1gtids binlog event to exclude certain GTIDs with Enhanced Binlog enabled and gtid\$1mode set to ON or ON\$1PERMISSIVE.
+ Fixed an issue which can cause memory management issue when parallel query operations on the table with the blob fields.
+ Fixed issue where a column with partial JSON updates will fail Parallel Export causing internal fallback to a much slower RDS Export.
+ Fixed an issue that can cause unexpected instance restarts when there is high concurrent write forwarding workload.
+ Fixed an issue where Zero Downtime Patching (ZDP) / Zero Downtime Restart (ZDR) could result in DB instance restart while restoring warnings with invalid error codes.
+ Fixed an issue where temporary binary log files were not being properly cleaned up after transaction rollbacks when using binary logging. This fix prevents unnecessary storage consumption from retained temporary files and in certain cases could also prevent anomalies in the binary log files.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3101.Patches"></a>

This release includes all community bug fixes up to and including 8.0.42. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](AuroraMySQL.Updates.MySQLBugs.md#AuroraMySQL.Updates.MySQLBugs.v3).
+ A query of the form SELECT 1 FROM t WHERE CAST(a AS UNSIGNED INTEGER) = 1 AND a = (SELECT 1 FROM t) led to an assertion in item\$1func.cc. (Bug \$136128964)

# Aurora MySQL database engine updates 2025-07-31 (version 3.10.0, compatible with MySQL 8.0.42)
<a name="AuroraMySQL.Updates.3100"></a><a name="3.10.0"></a><a name="3.10.0"></a>

**Version:** 3.10.0

Aurora MySQL 3.10.0 is generally available. Aurora MySQL 3.10 versions are compatible with MySQL 8.0.42. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

**Note**  <a name="lts_notice_3100"></a>
This version is designated as a long-term support (LTS) release. For more information, see [Aurora MySQL long-term support (LTS) releases](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Update.SpecialVersions.html#AuroraMySQL.Updates.LTS) 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 the next target version for Automatic Minor Version Upgrade campaign, which may not be an LTS version.

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

You can perform an in-place upgrade [leveraging Zero Downtime Patching (ZDP)](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.ZDP.html), restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.10.0 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## New features
<a name="AuroraMySQL.Updates.3100.NewFeatures"></a>
+ Aurora MySQL version 3.10 extends the in-memory relay log cache support for binary log replicas. This feature, first introduced in [version 3.05](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.3050.html), can improve binary log replication throughput by up to 40%. The in-memory relay log cache is enabled by default for single-threaded binary log replication, multi-threaded replication with [GTID auto-positioning](https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-auto-positioning.html) enabled, and starting with version 3.10, it’s also enabled for multi-threaded replication with [https://dev.mysql.com/doc/refman/8.0/en/replication-options-replica.html#sysvar_replica_preserve_commit_order](https://dev.mysql.com/doc/refman/8.0/en/replication-options-replica.html#sysvar_replica_preserve_commit_order) (even without GTIDs). You can control this feature using a new parameter in 3.10, [https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html). For more information, see [Binary log optimizations in Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/binlog-optimization.html).
+ Amazon Aurora has doubled its maximum storage capacity from 128 TiB to 256 TiB, enabling larger workloads in a single database cluster. To use the increased storage limit with Aurora MySQL, upgrade your cluster to version 3.10 (compatible with MySQL 8.0.42) or higher. After upgrade, Aurora storage automatically scales up to 256 TiB based on the amount of data in your cluster volume.

## Improvements
<a name="AuroraMySQL.Updates.3100.Improvements"></a>

**Security fixes**

Medium CVEs:
+ [CVE-2025-21501](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21501)
+ [CVE-2025-21500](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21500)
+ [CVE-2025-21543](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21543)
+ [CVE-2025-21540](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21540)
+ [CVE-2025-21491](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21491)
+ [CVE-2025-21490](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21490)
+ [CVE-2025-21559](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21559)
+ [CVE-2025-21555](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21555)
+ [CVE-2025-21497](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21497)
+ [CVE-2025-21519](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21519)
+ [CVE-2025-21529](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21529)
+ [CVE-2025-21505](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21505)
+ [CVE-2025-21531](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21531)
+ [CVE-2025-21523](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21523)
+ [CVE-2025-21503](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21503)
+ [CVE-2025-21522](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21522)
+ [CVE-2025-21518](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21518)
+ [CVE-2025-21577](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21577)
+ [CVE-2025-30682](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30682)
+ [CVE-2025-30687](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30687)
+ [CVE-2025-30688](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30688)
+ [CVE-2025-21574](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21574)
+ [CVE-2025-21575](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21575)
+ [CVE-2025-30693](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30693)
+ [CVE-2025-30695](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30695)
+ [CVE-2025-30715](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30715)
+ [CVE-2025-21584](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21584)
+ [CVE-2025-21580](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21580)
+ [CVE-2025-21581](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21581)
+ [CVE-2025-21585](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21585)
+ [CVE-2025-30689](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30689)
+ [CVE-2025-21579](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21579)
+ [CVE-2025-30696](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30696)
+ [CVE-2025-30705](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30705)
+ [CVE-2025-30683](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30683)
+ [CVE-2025-30684](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30684)
+ [CVE-2025-30685](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30685)
+ [CVE-2025-30699](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30699)
+ [CVE-2025-30704](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30704)
+ [CVE-2025-30721](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30721)

Low CVEs:
+ [CVE-2025-21520](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21520)
+ [CVE-2025-21546](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21546)
+ [CVE-2025-30703](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30703)
+ [CVE-2025-30681](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30681)

**Availability improvements:**
+ Fixed an issue that causes unnecessary database server restarts that were occurring because of an incorrect assessment of recovery progress.

**General improvements:**
+ Reduced commit latency when I/O optimized is enabled.
+ Fixed an issue that causes reader instances to not generate error logs when write forwarding is enabled and parameter `aurora_replica_read_consistency` is modified.
+ Fixed an issue that can cause a reader instance to restart due to the interaction between the replication thread and a query accessing tables that are not present in the buffer cache.
+ Fixed an issue where local write forwarding stops working after the database instance restarted with zero-downtime restart.
+ Fixed an issue in write forwarding where forwarded queries may behave incorrectly for statements containing set options.
+ Fixed a stability issue where inserting metadata for an undo tablespace would trigger an unexpected database restart.
+ Fixed an issue which can cause DB cluster exports to take significantly longer than expected when there are tables larger than 14 TB.
+ Fixed an issue which can cause incorrect reporting of `Innodb_buffer_pool_pages_misc` status variable.
+ Added support for preserving `LAST_INSERT_ID` during zero-downtime patching (ZDP) or zero-downtime restart (ZDR).
+ Aurora MySQL uses 8-bit values for virtual index IDs to prevent MySQL undo format issues, as exceeding this limit could cause cluster unavailability. When approaching this limit, the system now writes warning messages to the MySQL error log. If the limit is reached, attempts to add a new index return an error. For more information about virtual index best practices, see [Virtual index ID overflow errors](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.Performance.html#AuroraMySQL.BestPractices.Performance.VirtualIndexIDOverflow) in the Aurora MySQL documentation.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3100.Patches"></a>

This release includes all community bug fixes up to and including 8.0.42. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](AuroraMySQL.Updates.MySQLBugs.md#AuroraMySQL.Updates.MySQLBugs.v3).
+ A server exit could result from simultaneous attempts by multiple threads to register and deregister metadata Performance Schema objects, or to acquire and release metadata locks. (Bug \$126502135)

# Aurora MySQL database engine updates 2025-05-14 (version 3.09.0, compatible with MySQL 8.0.40)
<a name="AuroraMySQL.Updates.3090"></a><a name="3.09.0"></a><a name="3.09.0"></a>

**Version:** 3.09.0

Aurora MySQL 3.09.0 is generally available. Aurora MySQL 3.09 versions are compatible with MySQL 8.0.40. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

You can perform an in-place upgrade that leverages a [zero-downtime-patch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.ZDP.html), restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.09.0 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the * Amazon Aurora User Guide*.

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Release highlights
<a name="AuroraMySQL.Updates.3090.Highlights"></a>
+ Enhanced Aurora MySQL global databases to allow secondary reader instances to complete startup and serve read requests during unplanned events (hardware failures, network disruptions). Previously, secondary reader instances could not restart during such events. For more information, see [Cross-Region resiliency for Global Database secondary clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-secondary-availability.html) in the *Amazon Aurora User Guide*.
+ Reduced writer downtime during Aurora MySQL Global Database cross-region switchovers to typically under one minute, minimizing downtime during planned regional switches.

## Improvements
<a name="AuroraMySQL.Updates.3090.Improvements"></a>

**Security fixes**

Critical CVEs:
+ [CVE-2024-11053](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-11053)
+ [CVE-2024-37371](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-37371)

Medium CVEs:
+ [CVE-2024-7264](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-7264)
+ [CVE-2024-21193](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21193)
+ [CVE-2024-21194](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21194)
+ [CVE-2024-21196](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21196)
+ [CVE-2024-21197](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21197)
+ [CVE-2024-21198](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21198)
+ [CVE-2024-21199](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21199)
+ [CVE-2024-21201](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21201)
+ [CVE-2024-21203](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21203)
+ [CVE-2024-21207](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21207)
+ [CVE-2024-21212](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21212)
+ [CVE-2024-21213](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21213)
+ [CVE-2024-21218](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21218)
+ [CVE-2024-21219](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21219)
+ [CVE-2024-21230](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21230)
+ [CVE-2024-21236](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21236)
+ [CVE-2024-21238](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21238)
+ [CVE-2024-21239](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21239)
+ [CVE-2024-21241](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21241)
+ [CVE-2025-21494](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21494)
+ [CVE-2025-21504](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21504)
+ [CVE-2025-21525](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21525)
+ [CVE-2025-21534](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21534)
+ [CVE-2025-21536](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21536)

**Availability improvements:**
+ Fixed an issue where multi-statement queries forwarded from reader to writer instances could hang when `innodb_flush_log_at_trx_commit` is set to `0` on the writer and non-zero on the reader, preventing potential write forwarding failures.
+ Fixed a deadlock issue with Enhanced Binlog enabled that could cause database reboots when running `SHOW BINARY LOGS` concurrent with either committing transactions to [BLACKHOLE](https://dev.mysql.com/doc/refman/8.0/en/blackhole-storage-engine.html) engines or executing `XA PREPARE` statements, preventing potential stuck writes and instance availability issues.
+ Fixed race conditions in write forwarding that could cause Aurora writer instance restarts by preventing new requests from being accepted before previous requests are fully completed, improving the stability of write forwarding operations.
+ Fixed an issue on the replica where a network interruption may not correctly re-establish connection with the writer causing replication to be stuck and potential instance restarts.
+ Aurora MySQL Out of Memory (OOM) response now implements phased buffer pool resizing that gradually reduces memory usage based on system memory state (LOW/RESERVED) when enabled through `aurora_oom_response` DB parameter, providing better memory management during memory pressure situations.
+ Improved the Binlog file recovery time during database restarts by optimizing the recovery process to take constant time regardless of Binlog file size. Previously, in some cases, recovery time would be proportional to the size of the last Binlog file.
+ Fixed an issue that could cause unexpected MySQL server restarts when executing concurrent InnoDB table truncation operations while querying `performance_schema.data_lock_waits`.
+ Fixed an issue that can cause a database instance to restart when committing large binlog events during low storage conditions.
+ Fixed an issue where buffer pool resize operations triggered during Out of Memory (OOM) avoidance could become unresponsive during high-workload scenarios, leading to a possible database restart.
+ Fixed an issue that can cause a database restart loop when creating a trigger. The issue can also occur when a new Binlog or a Relaylog file is added or these files rotate.
+ Fixed an issue that could cause Aurora reader instance restarts when using write forwarding with multi-statement or implicit commit queries.

**General improvements:**
+ Fixed an issue where `ALTER TABLE ... REBUILD / OPTIMIZE TABLE` operations could consume excessive memory by allocating `innodb_ddl_buffer_size` bytes per DDL thread instead of dividing the buffer size among threads, preventing potential memory over utilization during DDL operations.
+ Changed the default value for `aurora_oom_response`, on all DB instance classes that have more than 4 GiB of memory, from print to print,decline,kill\$1connect. For more information, see [Amazon Aurora MySQL out-of-memory issues](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-troubleshooting-workload.html#AuroraMySQLOOM) in the *Amazon Aurora User Guide*.
+ The following privileges have been added to the `rds_superuser_role`: `FLUSH_OPTIMIZER_COSTS`, `FLUSH_STATUS`, `FLUSH_TABLES`, `FLUSH_USER_RESOURCES`. For information about the `rds_superuser_role`, see the [Amazon Master User Accounts with Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.MasterAccounts.html) documentation. For more information on these dynamic privileges, please see the [MySQL](https://dev.mysql.com/doc/refman/8.0/en/flush.html) documentation.
+ Starting with this Aurora MySQL version, fast insert optimization is no longer enabled. For more information, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance) in the *Amazon Aurora User Guide*.
+ Fixed an issue with an incorrect breach of the `max_user_connections` threshold, resulting in connection errors for some users. This occurs in some edge cases, such as when connections are created and killed almost immediately.
+ Fixed an audit logging issue that caused high CPU utilization, leading to an unresponsive database server instance.
+ Fixed a memory management issue when using XA transactions, preventing possible instance restarts when Enhanced Binlog is enabled.
+ Fixed an issue where query performance would degrade when the optimizer made incorrect cost estimations due to the Bufferpool Index Statistics being updated incorrectly post database server restart.
+ Fixed an issue that prevented customers from turning off local write-forwarding functionality because of a stuck worker thread.
+ Fixed an issue that caused the `SHOW BINARY LOGS` command to take longer to execute on a cluster where Enhanced Binlog is enabled or was previously enabled. This issue could also cause increased commit latency if multiple `SHOW BINARY LOGS` commands were running concurrently.

**Upgrades and migrations:**
+ Fixed an issue where Zero Downtime Patching (ZDP) could be unsuccessful while attempting to preserve connection, belonging to a user which had been dropped. More information on the `DROP USER` command, and its affect on active connections can be found in the [MySQL documentation](https://dev.mysql.com/doc/refman/8.0/en/flush.html).

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3090.Patches"></a>

This release includes all community bug fixes up to and including 8.0.40. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](AuroraMySQL.Updates.MySQLBugs.md#AuroraMySQL.Updates.MySQLBugs.v3).
+ While large transactions were being received and applied, and a request to stop the replication channel was made using `STOP REPLICA`, MySQL did not do so properly, and subsequently did not process any channel commands. In addition, the server shutdown process did not complete gracefully, and required either the MySQL process to be killed or the host system to be restarted. (Bug \$1115966, Bug \$137008345)

# Aurora MySQL database engine updates 2025-04-07 (version 3.08.2, compatible with MySQL 8.0.39)
<a name="AuroraMySQL.Updates.3082"></a><a name="3.08.2"></a><a name="3.08.2"></a>

 **Version:** 3.08.2

Aurora MySQL 3.08.2 is generally available. Aurora MySQL 3.08 versions are compatible with MySQL 8.0.39. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/). 

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*. 

Currently supported Aurora MySQL releases are 2.11.\$1, 2.12.\$1, 3.04.\$1, 3.05.\$1, 3.06.\$1, 3.07.\$1, and 3.08.\$1.

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.08.2 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*. 

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3081.Improvements"></a>

 **Security fixes:** 
+  [CVE-2024-11053](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-11053) 

 **Availability improvements:** 
+ Fixed an issue on the replica where a network interruption may not correctly re-establish connection with the writer.
+ Fixed an issue where a forwarded multi-statement query can fail if `innodb_flush_log_at_trx_commit` is set to `0` at writer instance.
+ Fixed an issue that can cause an Aurora writer DB instance to restart when write forwarding is enabled.
+ Fixed an issue that can cause an Aurora reader DB instance to restart when using write forwarding with multi-statement or implicit commit queries.

 **General improvements** 
+ Starting with this Aurora MySQL version, fast insert optimization is no longer enabled. For more information, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance) in the *Amazon Aurora User Guide*. 
+ Fixed an issue with an incorrect breach of the `max_user_connections` threshold, resulting in connection errors for some users. This occurs in some edge cases, such as when connections are created and killed almost immediately.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3081.Patches"></a>

This release includes all community bug fixes up to and including 8.0.39, in addition to the following. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3). 
+ While large transactions were being received and applied, and a request to stop the replication channel was made using `STOP REPLICA`, MySQL did not do so properly, and subsequently did not process any channel commands. In addition, the server shutdown process did not complete gracefully, and required either the MySQL process to be killed or the host system to be restarted. (Community Bug Fix \$1115966 and \$137008345)

# Aurora MySQL database engine updates 2025-02-17 (version 3.08.1, compatible with MySQL 8.0.39)
<a name="AuroraMySQL.Updates.3081"></a><a name="3.08.1"></a><a name="3.08.1"></a>

**Version:** 3.08.1

Aurora MySQL 3.08.1 is generally available. Aurora MySQL 3.08 versions are compatible with MySQL 8.0.39. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

Currently supported Aurora MySQL releases are 2.11.\$1, 2.12.\$1, 3.04.\$1, 3.05.\$1, 3.06.\$1, 3.07.\$1, and 3.08.\$1.

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.08.1 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3081.Improvements"></a>

**Availability improvements:**
+ Made improvements that reduce the DB instance restart time during database restarts, patch or minor version upgrades, and failovers.

**Upgrades and migrations**
+ Fixed an issue that can cause the failure of Zero Downtime Patching (ZDP) while attempting to restore the roles and grants of dropped users. For more information about the `DROP USER` operation, see [DROP USER Statement](https://dev.mysql.com/doc/refman/8.0/en/drop-user.html) in the MySQL documentation.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3081.Patches"></a>

This release includes all community bug fixes up to and including 8.0.39, in addition to the following. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).

# Aurora MySQL database engine updates 2024-11-18 (version 3.08.0, compatible with MySQL 8.0.39)
<a name="AuroraMySQL.Updates.3080"></a><a name="3.08.0"></a><a name="3.08.0"></a>

 **Version:** 3.08.0

Aurora MySQL 3.08.0 is generally available. Aurora MySQL 3.08 versions are compatible with MySQL 8.0.39. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/). 

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*. 

Currently supported Aurora MySQL releases are 2.11.\$1, 2.12.\$1, 3.04.\$1, 3.05.\$1, 3.06.\$1, 3.07.\$1, and 3.08.\$1.

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.08.0 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*. 

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## New features
<a name="AuroraMySQL.Updates.3080.New"></a>
+ Added three new Amazon CloudWatch metrics to allow users to monitor the InnoDB purge process:
  +  `PurgeBoundary` 
  +  `PurgeFinishedPoint` 
  +  `TruncateFinishedPoint` 

  For more information, see [Amazon CloudWatch metrics for Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMonitoring.Metrics.html) in the *Amazon Aurora User Guide*. 
+ Added a new CloudWatch metric `TransactionAgeMaximum` to allow users to identify long-running transactions that might be holding back the purge boundary. For more information, see [Amazon CloudWatch metrics for Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMonitoring.Metrics.html) in the *Amazon Aurora User Guide*. 
+ Added three new CloudWatch metrics for out-of-memory (OOM) avoidance:
  +  `AuroraMillisecondsSpentInOomRecovery` 
  +  `AuroraNumOomRecoverySuccessful` 
  +  `AuroraNumOomRecoveryTriggered` 

  For more information, see [Amazon CloudWatch metrics for Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMonitoring.Metrics.html) in the *Amazon Aurora User Guide*. 
+ Changed three CloudWatch metrics for out-of-memory (OOM) avoidance from running totals to incremental counters:
  +  `AuroraMemoryNumDeclinedSqlTotal` 
  +  `AuroraMemoryNumKillConnTotal` 
  +  `AuroraMemoryNumKillQueryTotal` 

  For more information, see [Amazon CloudWatch metrics for Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMonitoring.Metrics.html) in the *Amazon Aurora User Guide*. 
+ Added two global status variables to show the amount of memory used by [internal temporary tables](https://dev.mysql.com/doc/refman/8.0/en/internal-temporary-tables.html): `aurora_temptable_ram_allocation` and `aurora_temptable_max_ram_allocation`. These global status variables increase observability and help diagnose issues related to internal temporary table memory usage.

  For more information, see [Aurora MySQL global status variables](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html#AuroraMySQL.Reference.GlobalStatusVars) in the *Amazon Aurora User Guide*. 
+ Introduced the new system variable `aurora_optimizer_trace_print_before_purge` to print [optimizer traces](https://dev.mysql.com/doc/dev/mysql-server/latest/PAGE_OPT_TRACE.html) to the error log before the server purges the traces from memory. A purge can be triggered based on the thresholds set by the system variables [optimizer\$1trace\$1offset](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_optimizer_trace_offset) and [optimizer\$1trace\$1limit](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_optimizer_trace_limit). 
+ Added support for the following DB instance classes:
  + db.r7i
  + db.r8g

  For more information, see [Supported DB engines for DB instance classes](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Concepts.DBInstanceClass.SupportAurora.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3080.Improvements"></a>

 **Fixed security issues and CVEs:** 
+ Introduced a new user for binary log (binlog) replication, `rdsrepladmin_priv_checks_user`. For more information, see [Privilege checks user for binary log replication](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html#AuroraMySQL.privilege-model.binlog) in the *Amazon Aurora User Guide*. 
+ Fixed an issue where input parameters to [Aurora MySQL stored procedures](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.StoredProcs.html) might be handled incorrectly.

This release includes all community CVE fixes up to and including MySQL 8.0.39. The following CVE fixes are included:
+  [CVE-2023-44487](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-44487) 
+  [CVE-2024-0853](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-0853) 
+  [CVE-2024-20996](https://nvd.nist.gov/vuln/detail/CVE-2024-20996) 
+  [CVE-2024-21000](https://nvd.nist.gov/vuln/detail/CVE-2024-21000) 
+  [CVE-2024-21013](https://nvd.nist.gov/vuln/detail/CVE-2024-21013) 
+  [CVE-2024-21125](https://nvd.nist.gov/vuln/detail/CVE-2024-21125) 
+  [CVE-2024-21127](https://nvd.nist.gov/vuln/detail/CVE-2024-21127) 
+  [CVE-2024-21129](https://nvd.nist.gov/vuln/detail/CVE-2024-21129) 
+  [CVE-2024-21130](https://nvd.nist.gov/vuln/detail/CVE-2024-21130) 
+  [CVE-2024-21134](https://nvd.nist.gov/vuln/detail/CVE-2024-21134) 
+  [CVE-2024-21135](https://nvd.nist.gov/vuln/detail/CVE-2024-21135) 
+  [CVE-2024-21137](https://nvd.nist.gov/vuln/detail/CVE-2024-21137) 
+  [CVE-2024-21142](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21142) 
+  [CVE-2024-21157](https://nvd.nist.gov/vuln/detail/CVE-2024-21157) 
+  [CVE-2024-21159](https://nvd.nist.gov/vuln/detail/CVE-2024-21159) 
+  [CVE-2024-21160](https://nvd.nist.gov/vuln/detail/CVE-2024-21160) 
+  [CVE-2024-21162](https://nvd.nist.gov/vuln/detail/CVE-2024-21162) 
+  [CVE-2024-21163](https://nvd.nist.gov/vuln/detail/CVE-2024-21163) 
+  [CVE-2024-21165](https://nvd.nist.gov/vuln/detail/CVE-2024-21165) 
+  [CVE-2024-21166](https://nvd.nist.gov/vuln/detail/CVE-2024-21166) 
+  [CVE-2024-21173](https://nvd.nist.gov/vuln/detail/CVE-2024-21173) 
+  [CVE-2024-21177](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21177) 
+  [CVE-2024-21179](https://nvd.nist.gov/vuln/detail/CVE-2024-21179) 
+  [CVE-2024-21185](https://nvd.nist.gov/vuln/detail/CVE-2024-21185) 
+  [CVE-2024-25062](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-25062) 
+  [CVE-2024-37371](https://nvd.nist.gov/vuln/detail/cve-2024-37371) 
+  [CVE-2025-21492](https://nvd.nist.gov/vuln/detail/CVE-2025-21492) 

 **Availability improvements:** 
+ Fixed a defect that can cause the server to restart unexpectedly after running Data Manipulation Language (DML) commands on a table that already has instantly dropped columns, such that the count of dropped and nondropped columns is greater than 1017.
+ Fixed an issue that can lead to database log files not being rotated correctly, resulting in increased [local storage space usage](https://aws.amazon.com/blogs/database/understanding-amazon-aurora-mysql-storage-space-utilization) on a DB instance.
+ Fixed an issue that could cause the DB instance to stop closing connections under low-memory conditions when [aurora\$1oom\$1response](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-troubleshooting-workload.html#AuroraMySQLOOM) is enabled, leading to an out-of-memory reboot that could otherwise be avoided.
+ Fixed an issue that can cause a reader DB instance to restart when freeing memory used for log application.
+ Fixed an issue in computing internal metrics for full-text search (FTS) indexes that can cause database restarts.
+ Fixed a community issue that can sometimes produce incorrect query results when a `LIMIT` clause is used in subqueries along with index condition pushdown.
+ Fixed an issue that caused a memory access violation leading to releasing a mutex object no longer owned by the thread.
+ Fixed an issue that can cause a restart on a binary log (binlog) replica when processing a large number of relay log files during [relay log recovery](https://dev.mysql.com/doc/refman/8.0/en/replication-solutions-unexpected-replica-halt.html). 
+ Fixed an issue that can cause an Aurora reader DB instance to restart when write forwarding is enabled.
+ Fixed an issue where a query containing multiple `UNION` clauses could allocate a large amount of memory, leading to a DB instance restart.
+ Fixed an issue that causes the writer DB instance to restart when running a parallel query on a reader DB instance.
+ Fixed an issue where binlog replication would stall on the replica due to a deadlock encountered on the replica's I/O thread when the `FLUSH RELAY LOGS` command was run.
+ Fixed an issue that causes a DB instance restart when handling large GTID sets on a DB cluster with enhanced binlog enabled.
+ Fixed an issue that can cause a restart on a binlog replica when the in-memory relay log cache is enabled. The in-memory relay log cache is enabled on Aurora MySQL managed binlog replicas when using either single-threaded binary log replication, or multithreaded replication with [GTID auto-positioning](https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-auto-positioning.html) enabled.
+ Fixed an issue that can cause a binlog replica instance to restart when applying Data Control Language (DCL) statements during database engine startup.
+ Fixed an issue that, in rare conditions, can cause a reader DB instance to restart due to a deadlatch when running `SELECT` queries on tables being updated by its writer DB instance.
+ Fixed an issue that can cause an Aurora Global Database reader instance to restart with an active write forwarding session.
+ Fixed an issue that can cause Aurora read replicas to restart in the event of certain rare transaction commit orders on the writer DB instance.
+ Fixed an issue that can cause a database to restart when [scheduled events](https://dev.mysql.com/doc/refman/8.0/en/events-overview.html) are canceled while running on DB instances that have enhanced binlog enabled.

 **General improvements:** 
+ Fixed an issue where a client connection can become stuck during zero-downtime patching (ZDP) or zero-downtime restart (ZDR).
+ Fixed an issue that, in rare cases, cause a database instance restart due to a memory management issue that can occur while handling an open table failure.
+ Fixed an issue that can cause SQL statements to experience unexpected primary key violation errors or warnings on some rows when performing concurrent `INSERT` statements on a table that has an `AUTO_INCREMENT` primary key column and a unique key column, and when an `INSERT` statement has unique key violations on different rows.
+ The Performance Schema instrument `memory/sql/sp_head::main_mem_root` is now a controlled instrument. Consequently, memory allocated for parsing and representation of stored programs now contributes toward per-connection memory limits.
+ Fixed an issue where a row becomes unreadable through the spatial index during an update.
+  Fixed an issue that prevented users from disabling local write forwarding.
+ Fixed an issue where a `SELECT COUNT` query can return the wrong result while using write forwarding.
+ Fixed an issue that can lead to incorrect query results when ZDP incorrectly restores session variables set as hints in queries.
+ Fixed an issue with automatic truncation of undo tablespaces when they're larger than the threshold [innodb\$1max\$1undo\$1log\$1size](https://dev.mysql.com/doc/refman/8.0/en/innodb-parameters.html#sysvar_innodb_max_undo_log_size) in upgrade scenarios.
+ Fixed an issue where the commit latency and commit throughput aren't measured when `innodb_flush_log_at_trx_commit` is set to `0`. 
+ Fixed an issue that can cause Aurora replica lag to be reported incorrectly .
+ Fixed an issue that provided an incorrect value for the `threads_running` variable when using Aurora Global Database.
+ Fixed an issue where an Aurora MySQL binlog replica with [parallel secondary index optimization](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.MySQL.html#binlog-optimization) enabled would experience a restart when applying replication changes on tables with foreign keys.
+ Fixed a restart issue caused by prolonged resizing of the lock hash table during scaling up or scaling down events.
+ Fixed an issue that can cause a DB instance restart after disabling binary logging, when enhanced binlog was previously enabled.
+ Introduced optimizations to reduce memory usage during logical [data dictionary](https://dev.mysql.com/doc/refman/8.0/en/data-dictionary.html) recovery when there is a large number of tables.
+ Fixed an issue where a user might experience an `ERROR 1377 (HY000): Fatal error during log purge` error while running the [mysql.rds\$1set\$1external\$1source](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html#mysql_rds_set_external_source) stored procedure on a binlog replica, when binary log replication is already configured.
+ Fixed a defect that prevented the persistence of user role privileges after [ZDR](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.Availability.html). 
+ Fixed a memory issue associated with the default roles of the view definer.
+ Fixed an issue that can cause a DB instance to restart when `SHOW VOLUME STATUS` is run.
+ Fixed a restart issue caused by prolonged buffer pool resizing during scaling up or scaling down events.
+ Fixed a restart issue caused by logical read ahead (LRA) accessing freed pages due to buffer resizing during a scaling down event.
+ Fixed an issue that addresses `SELECT` queries returning incorrect results when the query uses `LEFT OUTER JOIN` with [semijoin transformation](https://dev.mysql.com/doc/refman/8.0/en/semijoins.html) that uses materialization as a strategy.
+ Fixed an issue that can cause failure in completing the process of disabling write forwarding.
+ Fixed an issue where the `ActiveTransactions` and `BlockedTransactions` CloudWatch metrics were reporting lower values than expected.
+ Fixed an issue where binlog replication breaks when the replica processes a multitable `DELETE` statement that explicitly deletes from both a parent and a child table.
+ Fixed an issue that can lead to a DB instance restart when processing a trigger with user-defined functions that return an `enum` type.
+ Fixed an issue where the `DMLLatency` CloudWatch metric would show incorrect values for a binary log replica instance when replicating using `binlog_format` set to `row`. 
+ Fixed an issue where slow `INSERT`, `DELETE`, and `UPDATE` queries run by the MySQL [Event Scheduler](https://dev.mysql.com/doc/refman/8.0/en/event-scheduler.html) weren't recorded in the slow query log unless preceded by a slow `SELECT` query.
+  Fixed an issue that, in rare cases, caused either intermittent unavailability of an Aurora read replica or table definition inconsistencies, sometimes with the error `Table does not exist`, on the replica. This is due to concurrent read queries on the replica and Data Definition Language (DDL) operations on the writer DB instance.
+ Fixed an issue that caused the `SHOW BINARY LOGS` command to take longer to run on a DB cluster where enhanced binlog is enabled or was previously enabled. This issue could also cause increased commit latency if multiple `SHOW BINARY LOGS` commands were running concurrently.

 **Upgrades and migrations:** 
+ Improved the performance of major version upgrade from Aurora MySQL version 2 to version 3 for DB clusters with large numbers of database objects (such as tables, triggers, and routines).

  For larger DB instance classes, the database upgrade process upgrades traditional MySQL object metadata to the new, atomic MySQL 8.0 data dictionary in parallel using multiple threads.
+ Fixed an issue that causes upgrades or migrations to fail when the target Aurora MySQL DB engine version is 3.04.0 or higher. This occurs when the `lower_case_table_names` DB cluster parameter is set to `1`, and MySQL database collation is incompatible with lowercase table names.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3080.Patches"></a>

This release includes all community bug fixes up to and including 8.0.39, in addition to the following. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3). 
+ Fixed an issue that caused `NULL` values to be incorrectly omitted from the result set for certain queries that have both `JOIN` and `UNION` operations. (Community Bug Fix \$1114301)

# Aurora MySQL database engine updates 2024-07-23 (version 3.07.1) (Deprecated)
<a name="AuroraMySQL.Updates.3071"></a><a name="3.07.1"></a><a name="3.07.1"></a>

**Version:** 3.07.1

Aurora MySQL 3.07.1 is generally available. Aurora MySQL 3.07 versions are compatible with MySQL 8.0.36. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

Currently supported Aurora MySQL releases are 2.11.\$1, 2.12.\$1, 3.03.\$1, 3.04.\$1, 3.05.\$1, 3.06.\$1, and 3.07.\$1.

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.07.1 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3071.Improvements"></a>

**Fixed security issues and CVEs:**
+ Introduced a new user for binary log (binlog) replication, `rdsrepladmin_priv_checks_user`. For more information, see [Privilege checks user for binary log replication](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html#AuroraMySQL.privilege-model.binlog) in the *Amazon Aurora User Guide*.

This release includes all community CVE fixes up to and including MySQL 8.0.36.

**Availability improvements:**
+ Fixed an issue that can cause a reader DB instance to restart when freeing memory used for log application.
+ Fixed an issue in computing internal metrics for full-text search (FTS) indexes that can cause database restarts.
+ Fixed an issue that can disable binary logging when an error occurs while committing a large transaction.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3071.Patches"></a>

This release includes all community bug fixes up to and including 8.0.36. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](AuroraMySQL.Updates.MySQLBugs.md#AuroraMySQL.Updates.MySQLBugs.v3).

# Aurora MySQL database engine updates 2024-06-04 (version 3.07.0) (Deprecated)
<a name="AuroraMySQL.Updates.3070"></a><a name="3.07.0"></a><a name="3.07.0"></a>

**Version:** 3.07.0

Aurora MySQL 3.07.0 is generally available. Aurora MySQL 3.07 versions are compatible with MySQL 8.0.36. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

Currently supported Aurora MySQL releases are 2.07.9, 2.07.10, 2.11.\$1, 2.12.\$1, 3.03.\$1, 3.04.\$1, 3.05.\$1, 3.06.\$1, and 3.07.\$1.

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3070.Improvements"></a>

**Fixed security issues and CVEs:**
+ Enabled support for FIPS-validated cryptography, a fully owned AWS implementation. For more information, see [AWS-LC is now FIPS 140-3 certified](https://aws.amazon.com/blogs/security/aws-lc-is-now-fips-140-3-certified/) on [AWS Security Blog](https://aws.amazon.com/blogs/security/).

This release includes all community CVE fixes up to and including MySQL 8.0.36. The following CVE fixes are included:
+ [CVE-2020-11104](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11104)
+ [CVE-2020-11105](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11105)
+ [CVE-2023-38545](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38545)
+ [CVE-2023-38546](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38546)
+ [CVE-2023-39975](https://nvd.nist.gov/vuln/detail/CVE-2023-39975)

**Availability improvements:**
+ Fixed an issue that can cause a reader DB instance to restart when reading a table that is being altered or dropped on the writer DB instance.
+ Fixed an issue that can cause an Aurora MySQL writer DB instance to restart when a write forwarding session is closed while running a forwarded query.
+ Fixed an issue that causes a DB instance to restart when handling large GTID sets on a binary log–enabled instance.
+ Fixed an issue when processing `INSERT` queries on InnoDB partitioned tables that can cause a gradual decline of free memory in the instance.
+ Fixed an issue that, in rare conditions, can cause the reader DB instances to restart.
+ Fixed an issue that can cause a database instance to restart when running [SHOW STATUS](https://dev.mysql.com/doc/refman/8.0/en/show-status.html) and [PURGE BINARY LOGS](https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html) statements concurrently. `PURGE BINARY LOGS` is a managed statement that is run to honor the user-configured binlog retention period.
+ Fixed an issue that can cause the server to unexpectedly close after running Data Manipulation Language (DML) statements on a table whose nonvirtual columns were reordered with a `MODIFY COLUMN` or `CHANGE COLUMN` statement.
+ Fixed an issue that, during the restart of a database instance, can cause an additional restart.
+ Fixed an issue that can cause a reader DB instance that uses write forwarding to restart when a forwarded [implicit commit statement](https://dev.mysql.com/doc/refman/8.0/en/implicit-commit.html) encounters an error.
+ Fixed an issue that, in rare conditions, can cause a reader instance to restart when performing `SELECT` queries on tables with a foreign key constraint.
+ Fixed an issue where DB instances using multi-TB Aurora cluster volumes can experience increased downtime during restart due to InnoDB buffer pool validation failures.
+ Fixed an issue that can cause a database to restart when a cascading `UPDATE` or `DELETE` foreign key constraint is defined on a table where a virtual column is involved either as a column in the foreign key constraint, or as a member of the referenced table.
+ Fixed an issue that can interrupt database recovery during startup if the restart occurred while running heavy insert operations involving `AUTO_INCREMENT` columns.
+ Fixed an issue in Aurora Serverless v2 that can lead to a database restart while scaling up.

**General improvements:**
+ Reduced I/O usage and improved performance for a subset of primary key range scan queries that employ parallel query.
+ [Aurora MySQL version 3.06.0](AuroraMySQL.Updates.3060.md) added support for Amazon Bedrock integration. As part of this, new reserved keywords (`accept`, `aws_bedrock_invoke_model`, `aws_sagemaker_invoke_endpoint`, `content_type`, and `timeout_ms`) were added. In Aurora MySQL version 3.07.0, these keywords have been changed to nonreserved keywords, which are permitted as identifiers without quoting. For more information on how MySQL handles reserved and nonreserved keywords, see [Keywords and reserved words](https://dev.mysql.com/doc/refman/8.0/en/keywords.html) in the MySQL documentation.
+ Fixed an issue that didn't clearly return an error message to the client when invoking the Amazon Bedrock service from an Aurora MySQL DB cluster in an AWS Region where Amazon Bedrock isn't yet available.
+ Fixed an issue that can cause excessive memory consumption when querying `BLOB` columns using Aurora parallel query.
+ Added support for the `connection_memory_limit` and `connection_memory_chunk_size` parameters to be set at the session level to behave the same as in MySQL Community Edition. The `connection_memory_limit` is used to set the maximum amount of memory that can be used by a single user connection. The `connection_memory_chunk_size` parameter can be used to set the chunking size for updates to the [global memory usage counter](https://dev.mysql.com/doc/refman/8.0/en/server-status-variables.html#statvar_Global_connection_memory).
+ 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\$1import\$1binlog\$1ssl\$1material](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html#mysql_rds_import_binlog_ssl_material)) could fail when the replication instance is undergoing a host replacement.
+ Added the `Aurora_fts_cache_memory_used` global status variable to track memory usage for the full-text search system across all tables. For more information, see [Aurora MySQL global status variables](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html#AuroraMySQL.Reference.GlobalStatusVars) in the *Amazon Aurora User Guide*.
+ Fixed an issue where an Amazon Redshift cluster configured as a zero-ETL destination might experience a temporary increase in [IntegrationLag](https://docs.aws.amazon.com/redshift/latest/mgmt/zero-etl-using.monitoring.html) when an Amazon Aurora MySQL DB cluster is configured as a binary log replica, with Enhanced Binlog and zero-ETL integration enabled.
+ 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 the [wait/io/redo\$1log\$1flush](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/ams-waits.io-auredologflush.html) event wasn't shown in the Performance Schema [wait event summary tables](https://dev.mysql.com/doc/refman/8.0/en/performance-schema-wait-summary-tables.html).
+ 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 a writer DB instance to restart when a reader DB instance using write forwarding runs a Data Manipulation Language (DML) statement that contains a timestamp value and the ` time_zone` database parameter is set to `UTC`.
+ Fixed an issue where a `SELECT` query on an Aurora reader instance might fail with the error table doesn't exist when the table has at least one full-text search (FTS) index and a `TRUNCATE` statement is being run on the Aurora writer DB instance.
+ Fixed an issue that, in rare cases, causes zero-downtime patching (ZDP) to fail.
+ Fixed an issue that can cause an incomplete result set when running queries involving `LEFT JOIN` or `RIGHT JOIN` operations using the hash join algorithm with parallel query.

**Upgrades and migrations:**
+ Fixed an issue that can cause upgrade failures from Aurora MySQL version 2 to Aurora MySQL version 3 when there is a user-defined `FTS_DOC_ID` column present in the table schema.
+ Fixed an issue that can cause upgrade failures from Aurora MySQL version 2 to Aurora MySQL version 3 due to a synchronization issue while processing InnoDB tablespaces.
+ 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.
+ Fixed an issue where the [SERVER\$1ID](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ISTables.html#AuroraMySQL.Reference.ISTables.replica_host_status) value wasn't updated after an Amazon RDS Blue/Green Deployment switchover. This led to issues where smart drivers such as the [Amazon Web Services (AWS) JDBC Driver](https://github.com/awslabs/aws-advanced-jdbc-wrapper) were unable to discover the DB cluster topology after a blue/green switchover. With this fix, Aurora DB clusters renamed as part of an RDS Blue/Green Deployment, that are running on Aurora MySQL version 3.07 and higher, will have the `SERVER_ID` value updated as part of the switchover. For earlier versions, the DB instances in the blue and green clusters can be rebooted to update the `SERVER_ID` value.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3070.Patches"></a>

This release includes all community bug fixes up to and including 8.0.36, in addition to the following. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+ Fixed an issue where cache line value can be calculated incorrectly, causing a failure during database restart on Graviton-based instances. (Community Bug Fix \$135479763)
+ Fixed an issue where some instances of subqueries within stored routines were not handled correctly. (Community Bug Fix \$135377192)
+ Fixed an issue that can cause higher CPU usage due to background TLS certificate rotation (Community Bug Fix \$134284186).
+ Fixed an issue where InnoDB allowed the addition of `INSTANT` columns to tables in the MySQL system schema in Aurora MySQL versions lower than 3.05, which could lead to the server unexpectedly closing (database instance restarting) after upgrading to Aurora MySQL version 3.05.0. (Community Bug Fix \$135625510).

# Aurora MySQL database engine updates 2024-06-26 (version 3.06.1) (Deprecated)
<a name="AuroraMySQL.Updates.3061"></a><a name="3.06.1"></a><a name="3.06.1"></a>

**Version:** 3.06.1

Aurora MySQL 3.06.1 is generally available. Aurora MySQL 3.06 versions are compatible with MySQL 8.0.34. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

Currently supported Aurora MySQL releases are 2.07.9, 2.07.10, 2.11.\$1, 2.12.\$1, 3.03.\$1, 3.04.\$1, 3.05.\$1, 3.06.\$1, and 3.07.\$1.

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.06.1 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3060.Improvements"></a>

**Fixed security issues and CVEs:**

This release includes all community CVE fixes up to and including MySQL 8.0.34. The following CVE fixes are included:
+ [CVE-2023-44487](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-44487)
+ [CVE-2024-0853](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-0853)

**Availability improvements:**
+ Fixed an issue that causes an Aurora MySQL DB instance to restart when running a parallel query.
+ Fixed an issue that can cause a reader DB instance to restart when reading a table that is being altered or dropped on the writer DB instance.
+ Fixed an issue that caused a memory access violation leading to releasing a mutex object no longer owned by the thread.
+ Fixed an issue that can cause an Aurora MySQL writer DB instance to restart when a write forwarding session is closed while running a forwarded query.
+ Fixed an issue that causes a DB instance restart when handling large GTID sets on a binary log–enabled instance.
+ Fixed an issue that, in rare conditions, can cause a reader instance to restart when performing `SELECT` queries on tables with a foreign key constraint.
+ Fixed an issue that causes a DB instance to restart when attempting to recover the InnoDB data dictionary during database recovery.
+ Fixed an issue in Aurora Serverless v2 that can lead to a database restart while scaling up.

**General improvements:**
+ Fixed an issue in metrics publishing code where memory might be used after being freed.
+ Fixed an issue that caused repeated DB engine restarts due to a nonexistent undo tablespace object.
+ Fixed an issue with automatic truncation of undo tablespaces when they're larger than the threshold [innodb\$1max\$1undo\$1log\$1size](https://dev.mysql.com/doc/refman/8.4/en/innodb-parameters.html#sysvar_innodb_max_undo_log_size) in upgrade scenarios.
+ Fixed an issue that provided an incorrect value for the `threads_running` status variable when using Aurora Global Database.
+ Fixed an issue where an Aurora MySQL binary log (binlog) read replica with [parallel secondary index optimization](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.MySQL.html#binlog-optimization) enabled would experience a restart when applying replication changes on tables with foreign keys.
+ [Aurora MySQL version 3.06.0](AuroraMySQL.Updates.3060.md) added support for Amazon Bedrock integration. As part of this, new reserved keywords (`accept`, `aws_bedrock_invoke_model`, `aws_sagemaker_invoke_endpoint`, `content_type`, and `timeout_ms`) were added. In Aurora MySQL version 3.06.1, these keywords have been changed to nonreserved keywords, which are permitted as identifiers without quoting. For more information on how MySQL handles reserved and nonreserved keywords, see [Keywords and reserved words](https://dev.mysql.com/doc/refman/8.0/en/keywords.html) in the MySQL documentation.
+ Fixed an issue that didn't clearly return an error message to the client when invoking the Amazon Bedrock service from an Aurora MySQL DB cluster in an AWS Region where Amazon Bedrock isn't yet available.
+ Fixed an issue that causes a DB instance to restart because of inaccurate lock holder information in `rw_lock` when using parallel reads.
+ Fixed an issue that can cause a DB instance to restart when `SHOW VOLUME STATUS` is run.
+ Fixed a memory management issue that led to a decrease in freeable memory over time when running `SELECT ... INTO OUTFILE ...` queries.
+ Added support for the `connection_memory_limit` and `connection_memory_chunk_size` parameters to be set at the session level to behave similar to corresponding functionality in MySQL Community Edition. The `connection_memory_limit` parameter sets the maximum amount of memory that can be used by a single user connection. The `connection_memory_chunk_size` parameter sets the chunking size for updates to the [global memory usage counter](https://dev.mysql.com/doc/refman/8.0/en/server-status-variables.html#statvar_Global_connection_memory).
+ Fixed an issue that can cause a DB instance to restart when the local storage on the DB instance reaches full capacity.
+ Fixed an issue where the Performance Schema wasn't enabled when Performance Insights automated management was turned on for db.t4g.medium and db.t4g.large DB instances.
+ Fixed an issue that can cause a writer DB instance to restart when a reader DB instance using write forwarding runs a Data Manipulation Language (DML) statement that contains a timestamp value and the ` time_zone` database parameter is set to `UTC`.
+ Fixed an issue during zero-downtime patching (ZDP) that prevents a DB instance from closing client connections upon reaching the customer-configured minimum value of either `wait_timeout` or` interactive_timeout`.

**Upgrades and migrations:**
+ Fixed an issue that causes upgrades or migrations to fail when the target Aurora MySQL DB engine version is 3.04.0 or higher. This occurs when the `lower_case_table_names` DB cluster parameter is set to `1`, and MySQL database collation is incompatible with lowercase table names.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3060.Patches"></a>

This release includes all community bug fixes up to and including 8.0.34. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).

# Aurora MySQL database engine updates 2024-03-07 (version 3.06.0) (Deprecated)
<a name="AuroraMySQL.Updates.3060"></a><a name="3.06.0"></a><a name="3.06.0"></a>

**Version:** 3.06.0

Aurora MySQL 3.06.0 is generally available. Aurora MySQL 3.06 versions are compatible with MySQL 8.0.34. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

Currently supported Aurora MySQL releases are 2.07.9, 2.07.10, 2.11.\$1, 2.12.\$1, 3.03.\$1, 3.04.\$1, 3.05.\$1, and 3.06.\$1.

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.06.0 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## New features
<a name="AuroraMySQL.Updates.3060.New"></a>
+ Aurora MySQL version 3.06.0 supports Amazon Bedrock integration and introduces the new reserved keywords `accept`, `aws_bedrock_invoke_model`, `aws_sagemaker_invoke_endpoint`, `content_type`, and `timeout_ms`. Check the object definitions for the usage of the new reserved keywords before upgrading to version 3.06.0. To mitigate the conflict with the new reserved keywords, quote the reserved keywords used in the object definitions. For more information on the Amazon Bedrock integration and handling the reserved keywords, see [What is Amazon Bedrock?](https://docs.aws.amazon.com/bedrock/latest/userguide/what-is-bedrock.html) in the *Amazon Aurora User Guide*. For additional information, see [Keywords and Reserved Words](https://dev.mysql.com/doc/refman/8.0/en/keywords.html), [The INFORMATION\$1SCHEMA KEYWORDS Table](https://dev.mysql.com/doc/refman/8.0/en/information-schema-keywords-table.html), and [Schema Object Names](https://dev.mysql.com/doc/refman/8.0/en/identifiers.html) in the MySQL documentation.
+ Improved performance for binary log replicas when replicating transactions for large tables with more than one secondary index. This feature introduces a thread pool to apply secondary index changes in parallel on a binlog replica. The feature is controlled by the `aurora_binlog_replication_sec_index_parallel_workers` DB cluster parameter, which controls the total number of parallel threads available to apply the secondary index changes. For more information, see [Optimizing binary log replication](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.MySQL.html#binlog-optimization) in the *Amazon Aurora User Guide*.
+ Added a new stored procedure `mysql.rds_set_read_only` that allows changing the value of the global system variable `read_only` on database instances in your Aurora MySQL cluster. For more information, see [Replicating](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html) in the *Amazon Aurora User Guide*.
+ Added a new stored procedure `mysql.rds_set_binlog_source_ssl` that allows setting the encryption on a binary log replica by specifying a value for `SOURCE_SSL`. For more information, see [Replicating](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html) in the *Amazon Aurora User Guide*.
+ [Amazon Aurora Machine Learning](https://aws.amazon.com/rds/aurora/machine-learning) is an optimized integration between the Aurora MySQL database and AWS machine learning (ML) services. [Amazon Bedrock](https://docs.aws.amazon.com/bedrock/latest/userguide/what-is-bedrock.html) is now supported, allowing you to invoke machine learning models in Amazon Bedrock directly from your Aurora MySQL DB cluster using SQL. For more information on using Amazon Bedrock with your Aurora MySQL DB cluster, see [Using Amazon Aurora machine learning with Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-ml.html) in the *Amazon Aurora User Guide*.
+ Aurora MySQL version 3.06 adds support for [automated undo tablespace truncation](https://dev.mysql.com/doc/refman/8.0/en/innodb-undo-tablespaces.html#truncate-undo-tablespace). This optimization allows you to reclaim unused space in undo tablespaces after the undo logs have been purged.

## Improvements
<a name="AuroraMySQL.Updates.3060.Improvements"></a>

**Fixed security issues and CVEs:**

The following CVE fixes are included in this release:
+ [CVE-2020-11104](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11104)
+ [CVE-2020-11105](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11105)
+ [CVE-2023-38545](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38545)
+ [CVE-2023-38546](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38546)
+ [CVE-2023-39975](https://nvd.nist.gov/vuln/detail/CVE-2023-39975)

**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 communication 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 of the Aurora storage instance.
+ Fixed an issue when processing `INSERT` queries on InnoDB partitioned tables that can cause a gradual decline of free memory in the instance.
+ Fixed an issue that can cause an Aurora MySQL DB instance to restart or fail over due to a decrease in freeable memory when hash join is used while running queries.
+ Fixed an issue that can cause a database instance restart when running [SHOW STATUS](https://dev.mysql.com/doc/refman/8.0/en/show-status.html) and [PURGE BINARY LOGS](https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html) statements concurrently. `PURGE BINARY LOGS` is a managed statement that is run to honor the user-configured binlog retention period.
+ Fixed an issue that can cause the server to unexpectedly close after running Data Manipulation Language (DML) statements on a table whose nonvirtual columns were reordered with a `MODIFY COLUMN` or `CHANGE COLUMN` statement.
+ Fixed an issue that, during the restart of a database instance, can cause an additional restart.
+ Fixed an issue that can cause a database restart when a cascading `UPDATE` or `DELETE` foreign key constraint is defined on a table where a virtual column is involved either as a column in the foreign key constraint, or as a member of the referenced table.
+ In Aurora MySQL 2.10, we added support for rebooting an Aurora DB cluster with read availability. This feature allows reader DB instances to stay online while a writer DB instance is rebooted. This feature is now supported on secondary AWS Regions in Aurora MySQL global databases, ensuring that you can still serve read requests during a writer instance restart on the primary cluster. Previously, when a writer instance restarted, all reader instances in an Aurora MySQL secondary cluster also restarted. With this release, secondary cluster reader instances continue to serve read requests during a writer instance restart, improving read availability in the cluster. For more information, see [Rebooting an Aurora cluster with read availability](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_RebootCluster.html#aurora-mysql-survivable-replicas).
+ Fixed an issue that can interrupt database recovery during startup if the restart occurred while running heavy insert operations involving `AUTO_INCREMENT` columns.

**General improvements:**
+ Fixed an issue that can cause a parallel query to fail due to transient network issues while reading data from the Aurora 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\$1import\$1binlog\$1ssl\$1material](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html#mysql_rds_import_binlog_ssl_material)) could fail when the replication instance is undergoing a host replacement.
+ Small DB instances with less than or equal to 4 GiB of memory now close the top memory-consuming connections when the DB instance is under memory pressure. You can also tune the buffer pool to decrease its size. For more information, see [Amazon Aurora MySQL out-of-memory issues](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-troubleshooting-workload.html#AuroraMySQLOOM) in the *Amazon Aurora User Guide*.
+ Changed the default response for `aurora_oom_response`, on all DB instance classes that have more than 4 GiB of memory, from empty to `print`. For more information, see [Amazon Aurora MySQL out-of-memory issues](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-troubleshooting-workload.html#AuroraMySQLOOM) in the *Amazon Aurora User Guide*.
+ 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 the [wait/io/redo\$1log\$1flush](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/ams-waits.io-auredologflush.html) event wasn't shown in the Performance Schema [wait event summary tables](https://dev.mysql.com/doc/refman/8.0/en/performance-schema-wait-summary-tables.html).
+ Added the `Aurora_lockmgr_memory_used` and `Aurora_lockmgr_buffer_pool_memory_used` metrics to track the lock manager's memory usage. For more information, see [Aurora MySQL global status variables](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html#AuroraMySQL.Reference.GlobalStatusVars) in the *Amazon Aurora User Guide*.
+ Fixed an issue where small read replica instances can experience increased replication lag after upgrading from Aurora MySQL versions lower than 2.11.\$1.
+ 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 where a `SELECT` query on an Aurora reader instance might fail with the error table doesn't exist when the table has at least one full-text search (FTS) index and a `TRUNCATE` statement is being run on the Aurora writer DB instance.
+ Fixed an issue that can cause an incomplete result set when running queries involving `LEFT JOIN` or `RIGHT JOIN` operations using the hash join algorithm with parallel query.

**Upgrades and migrations:**
+ Fixed an issue that can cause major version upgrades to fail if there is a user-defined `FTS_DOC_ID` column present in the table schema.
+ Fixed an issue that can cause upgrade failures from Aurora MySQLversion 2 to Aurora MySQL version 3 due to a synchronization issue while processing InnoDB tablespaces.
+ 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
<a name="AuroraMySQL.Updates.3060.Patches"></a>

This release includes all community bug fixes up to and including 8.0.34, in addition to the following. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+ Fixed an issue where cache line value can be calculated incorrectly, causing a failure during database restart on Graviton-based instances. (Community Bug Fix \$135479763)
+ Fixed an issue where some instances of subqueries within stored routines were not always handled correctly. (Community Bug Fix \$135377192)
+ Fixed an issue that can cause higher CPU usage due to background TLS certificate rotation (Community Bug Fix \$134284186).
+ Fixed an issue where InnoDB allowed the addition of `INSTANT` columns to tables in the MySQL system schema in Aurora MySQL versions lower than 3.05, which could lead to the server unexpectedly closing (database instance restarting) after upgrading to Aurora MySQL version 3.05.0. (Community Bug Fix \$135625510).

# Aurora MySQL database engine updates 2024-01-31 (version 3.05.2) (Deprecated)
<a name="AuroraMySQL.Updates.3052"></a><a name="3.05.2"></a>

**Version:** 3.05.2

Aurora MySQL 3.05.2 is generally available. Aurora MySQL 3.05 versions are compatible with MySQL 8.0.32. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*.

Currently supported Aurora MySQL releases are 2.07.9, 2.07.10, 2.11.\$1, 2.12.\$1, 3.03.\$1, 3.04.\$1, and 3.05.\$1.

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.05.2 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3052.Improvements"></a>

**Fixed security issues and CVEs:**

The following CVE fixes are included in this release:
+ [CVE-2020-11104](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11104)
+ [CVE-2020-11105](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11105)
+ [CVE-2023-38545](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38545)
+ [CVE-2023-39975](https://nvd.nist.gov/vuln/detail/CVE-2023-39975)

**Availability improvements:**
+ Fixed an issue where processing `INSERT` queries on InnoDB partitioned tables can cause a gradual decline of free memory in the instance.
+ Fixed an issue that can cause a database instance restart when running [SHOW STATUS](https://dev.mysql.com/doc/refman/8.0/en/show-status.html) and [PURGE BINARY LOGS](https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html) statements concurrently. `PURGE BINARY LOGS` is a managed statement that is run to honor the user-configured binlog retention period.
+ Fixed an issue that can cause the server to unexpectedly close after running Data Manipulation Language (DML) statements on a table whose nonvirtual columns were reordered with a `MODIFY COLUMN` or `CHANGE COLUMN` statement.
+ Fixed an issue that, during the restart of a database instance, can cause an additional restart.

**General improvements:**
+ 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 setup using custom SSL certificates ([mysql.rds\$1import\$1binlog\$1ssl\$1material](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html#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.
+ In Aurora MySQL versions lower than 3.05.2, users are unable to retrieve the output of `SHOW ENGINE INNODB STATUS` on Aurora MySQL reader DB instances. This is due to the [default InnoDB behavior](https://dev.mysql.com/doc/refman/8.0/en/innodb-read-only-instance.html) when `innodb_read_only` is enabled.

  In Aurora MySQL version 3.05.2 and higher, when `SHOW ENGINE INNODB STATUS` is run on a reader instance, the output is written to the MySQL error log, allowing for easier troubleshooting.

  For more information on working with MySQL error logs, see [Aurora MySQL error logs](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_LogAccess.MySQL.LogFileSize.html#USER_LogAccess.MySQL.Errorlog). For more information on `SHOW ENGINE INNODB STATUS`, see [SHOW ENGINE statement](https://dev.mysql.com/doc/refman/8.0/en/show-engine.html) in the MySQL documentation.

**Upgrades and migrations:**
+ Fixed an issue that can cause upgrade failures from Aurora MySQL version 2 to Aurora MySQL version 3 when there is a user-defined `FTS_DOC_ID` column present in the table schema.
+ Fixed an issue that can cause upgrade failures from Aurora MySQL version 2 to Aurora MySQL version 3 due to a synchronization issue while processing InnoDB tablespaces.
+ 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
<a name="AuroraMySQL.Updates.3052.Patches"></a>

This release includes all community bug fixes up to and including 8.0.32, in addition to the following. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+ Fixed an issue where `records_in_range` performed an excessive number of disk reads for `INSERT` operations, leading to a gradual decline in performance. (Community Bug Fix \$134976138)

# Aurora MySQL database engine updates 2023-11-21 (version 3.05.1) (Deprecated)
<a name="AuroraMySQL.Updates.3051"></a><a name="3051"></a><a name="3.05.0.1"></a>

 **Version:** 3.05.1 

 Aurora MySQL 3.05.1 is generally available. Aurora MySQL 3.05 versions are compatible with MySQL 8.0.32. For more information, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/). 

 Currently supported Aurora MySQL releases are 2.07.\$1, 2.11.\$1, 2.12.\$1, 3.01.\$1, 3.02.\$1, 3.03.\$1, 3.04.\$1, and 3.05.\$1. 

 You can upgrade an existing Aurora MySQL 3.\$1 database cluster to Aurora MySQL 3.05.1. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 3.05.1. 

 If you upgrade an Aurora MySQL global database to version 3.05.\$1, you must upgrade your primary and secondary DB clusters to the exact same version, including the patch level. For more information on upgrading the minor version of an Aurora global database, see [Minor version upgrades](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-upgrade.html#aurora-global-database-upgrade.minor). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3051.Improvements"></a>

**Fixed security issues and CVEs listed below:**

This release includes all community CVEs fixes up to and including MySQL 8.0.32.
+ [CVE-2023-38545](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38545)

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3051.Patches"></a>

This release includes all community bug fixes up to and including 8.0.32, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+ Fixed an issue in InnoDB when, if a MySQL table in a system schema had an `INSTANT ADD` column added between Aurora MySQL versions 3.01 through Aurora MySQL versions 3.04, and after Aurora MySQL was upgraded to version 3.05.0, DMLs on these tables would result in the server unexpectedly closing. (Community Bug Fix \$135625510)

# Aurora MySQL database engine updates 2023-10-30 (version 3.05.0.1) (Deprecated)
<a name="AuroraMySQL.Updates.30501"></a><a name="30501"></a><a name="3.05.0.1"></a>

 **Version:** 3.05.0.1 

 Aurora MySQL 3.05.0.1 is generally available in the following regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), AWS GovCloud (US-East), and AWS GovCloud (US-West). This is an early, security fix–only release. These fixes will be deployed more broadly across all Regions with the next patch release, 3.05.1. Aurora MySQL 3.05 versions are compatible with MySQL 8.0.32. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/). 

 Currently supported Aurora MySQL releases are 2.07.\$1, 2.11.\$1, 2.12.\$1, 3.01.\$1, 3.02.\$1, 3.03.\$1, 3.04.\$1, and 3.05.\$1. 

 You can upgrade an existing Aurora MySQL 3.\$1 database cluster to Aurora MySQL 3.05.0.1. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 3.05.0.1. 

 If you upgrade an Aurora MySQL global database to version 3.05.\$1, you must upgrade your primary and secondary DB clusters to the exact same version, including the patch level. For more information on upgrading the minor version of an Aurora global database, see [Minor version upgrades](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-upgrade.html#aurora-global-database-upgrade.minor). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.30501.Improvements"></a>

**Fixed security issues and CVEs listed below:**

This release includes all community CVEs fixes up to and including MySQL 8.0.32.
+ [CVE-2023-38545](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38545)

# Aurora MySQL database engine updates 2023-10-25 (version 3.05.0) (Deprecated)
<a name="AuroraMySQL.Updates.3050"></a><a name="3.05.0"></a><a name="3.05.0"></a>

 **Version:** 3.05.0 

 Aurora MySQL 3.05.0 is generally available. Aurora MySQL 3.05 versions are compatible with MySQL 8.0.32. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

 For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html). 

 Currently supported Aurora MySQL releases are 2.07.9, 2.07.10, 2.11.\$1, 2.12.\$1, 3.03.\$1, 3.04.\$1, and 3.05.\$1. 

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.05.0 cluster. 

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3050.Improvements"></a>

 **New features:** 
+ Added support for saving data from an Aurora MySQL database cluster into text files in an Amazon S3 bucket encrypted with a KMS key (SSE-KMS). For more information, see [Saving data from an Amazon Aurora MySQL DB cluster into text files in an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.SaveIntoS3.html). 
+ Introduced a new global status variable `aurora_tmz_version` to denote the current version of the time zone (TZ) information used by the engine. The values follow the IANA time zone database version and are formatted as "YYYYsuffix", for example, 2022a and 2023c. For more information, see [Aurora MySQL global status variables](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html#AuroraMySQL.Reference.GlobalStatusVars). 

**Fixed security issues and CVEs listed below:**

Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes are below:
+ [CVE-2022-37434](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37434)

 **Availability improvements:** 
+ Fixed an issue where Aurora MySQL database instances using parallel query may experience a database restart when running a high number of concurrent parallel queries. 
+  Fixed an issue with lock contention caused by an audit logging thread eventually leading to high CPU utilization and client application timeouts. 
+ Fixed an issue which can cause the executed GTID set to be recovered incorrectly on a binary log (binlog) replica cluster with enhanced binlog enabled when any binlog source has `gtid_mode` set to `ON` or `ON_PERMISSIVE`. This issue may cause the replica cluster's writer instance to restart an additional time during recovery, or lead to incorrect results when querying the executed GTID set. 
+ Fixed a memory management issue that can cause an Aurora MySQL database instance restart or a failover due to a decrease in freeable memory when enhanced binary log is enabled. 
+ Fixed an issue which can cause a database instance restart when attempting to read a database page that belongs to a dropped table. 
+ Fixed an issue which can cause the reader instance to restart when the writer instance grows the database volume to a multiple of 160GB. 
+ Fixed an issue where an Aurora MySQL database instance with the enhanced binary log feature enabled might get stuck during the database instance startup as the binary log recovery process is being executed. 
+ Fixed an issue where an Aurora MySQL database instance may experience multiple restarts during instance startup while large rollback segments are initialized. 
+ Fixed an issue during zero downtime patching which causes an instance restart that leads to database connections being unexpectedly closed. 
+ Fixed an issue which can cause a database instance restart due to a deadlatch when running [SHOW STATUS](https://dev.mysql.com/doc/refman/8.0/en/show-status.html) and [PURGE BINARY LOGS](https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html) statements concurrently. The purge binary logs is a managed statement that is executed to honor the user configured binlog retention period. 
+ Fixed an issue which can cause database cluster unavailability if the writer instance restarts while the database is creating or dropping triggers on internal system tables. 
+ Fixed an issue which can cause a database instance restart due to a long semaphore wait when using the enhanced binlog feature on a cluster with an Aurora replica. 
+ Fixed an issue which can cause a database instance to restart while executing a query which references an aggregate function. 
+ Fixed an issue which, in rare conditions, can cause the database instance to restart when Aurora Serverless v2 incorrectly attempts to update the table cache while scaling. 
+ Fixed an issue where unsupported index scan access methods were considered for common table expressions (CTE) while materializing intermediate temporary tables, which can lead to undesired behavior including database restarts or incorrect query results. We fixed this issue by avoiding the use of such unsupported index scan access methods on tables using the TempTable storage engine.

 **General improvements:** 
+ Fixed an issue which can cause database unavailability when enhanced binlog is enabled on an Aurora Serverless v2 database cluster running on Aurora MySQL 3.04.0.
+ Removed unused storage metadata before writing to Aurora storage when the enhanced binlog feature is enabled. This avoids certain scenarios when a database restart or failover may occur because of increased write latency due to increased bytes transmitted over the network. 
+ With the addition of the `malloc_stats` and `malloc_stats_totals` tables in the `performance_schema`, three advanced system variables were added to control the behavior of Jemalloc, an internal memory allocator:
  + `aurora_jemalloc_background_thread`.
  + `aurora_jemalloc_dirty_decay_ms`.
  + `aurora_jemalloc_tcache_enabled`.
+ Fixed an issue where Aurora specific performance schema tables were not created upon an upgrade or migration. 
+ Added a new system variable, `aurora_use_vector_instructions`. When this parameter is enabled, Aurora MySQL uses optimized vector processing instructions to improve performance on I/O heavy workloads. This setting is turned `ON` by default in Aurora MySQL 3.05 and higher. For more details, see [Aurora MySQL configuration parameters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html#AuroraMySQL.Reference.Parameters.Instance).
+ Fixed an issue which can cause the `NumBinaryLogFiles` metrics on CloudWatch to display incorrect results when enhanced binlog is enabled. 
+ The request timeout for [Aurora MySQL Machine Learning](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-ml.html) operations to Amazon Sagemaker has been increased from 3 to 30 seconds. This helps resolve an issue where customers may see an increased number of retries or failures for requests to Amazon Sagemaker from Aurora MySQL Machine Learning when using larger batch sizes. 
+ Added support for `malloc_stats` and `malloc_stats_totals` tables in the performance\$1schema database. 
+ Updated the `FROM` keyword in the `LOAD DATA FROM S3` command to be optional. For more information, see [Loading data into an Amazon Aurora MySQL DB cluster from text files in an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.LoadFromS3.html). 
+ Added support for the parameter `innodb_aurora_instant_alter_column_allowed`, which controls whether the `INSTANT` algorithm can be used for `ALTER COLUMN` operations. For more information see [Cluster-level parameters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html#AuroraMySQL.Reference.Parameters.Cluster). 
+ Fixed an issue which can prevent new client connections from being established to the database when write forwarding is enabled. 
+ Fixed an issue which can cause the modification of the `table_open_cache` database parameter to not take effect until the database instance is restarted. 
+ Fixed an issue which can cause duplicate key errors for `AUTO_INCREMENT` columns using descending indices after a snapshot restore, backtrack, or database clone operation. 
+ Fixed an issue involving index scans where an inaccurate result might be returned when executing a `SELECT` query with the `GROUP BY` clause and the `aurora_parallel_query`parameter turned `ON`. 
+ Fixed an issue which may cause the depletion of available memory when executing queries against the `INFORMATION_SCHEMA INNODB_TABLESPACES` table. 
+ Fixed an issue where the reader instance is unable to open a table, with ERROR 1146. This issue occurs when executing certain types of online Data Definition Language (DDL) while the `INPLACE` algorithm is being used on the writer 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 which can cause a database restart when connected binary log (binlog) consumers are using duplicate binlog replication server IDs. 
+ Introduced an in-memory [relay log](https://dev.mysql.com/doc/refman/8.0/en/replica-logs-relaylog.html) cache for Aurora MySQL managed binary log replicas. This improvement can help achieve up to a 40% increase in binary log replication throughput. This enhancement is enabled automatically when using single-threaded binary log replication or when using multi-threaded replication with [GTID auto-positioning](https://dev.mysql.com/doc/refman/8.0/en/replication-gtids-auto-positioning.html) enabled.

 **Upgrades and migrations:** 
+ Upgrading from MySQL 5.7 to MySQL 8.0 with a very large number of tables in a single database caused the server to consume excessive memory. It was found that, during the process of checking whether tables could be upgraded, we fetched all the data dictionary `Table` objects upfront, processing each and fetching its name, then performed [Checking Version Compatibility](https://dev.mysql.com/doc/refman/8.0/en/check-table.html#check-table-version-compatibility) on the list. Fetching all objects beforehand was not necessary in this case, and contributed greatly to memory consumption. To correct this problem, we now fetch one `Table` object at a time in such cases, performing any required checks, fetching its name, and releasing the object, before proceeding with the next one. (Bug \$134526001) 
+ Improved the performance of major version upgrades from Aurora MySQL version 2 to version 3 by executing tablespace checks in parallel using all available vCPUs on the database instance.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3050.Patches"></a>

This release includes all community bug fixes up to and including 8.0.32, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+  Fixed an issue which can cause higher CPU utilization due to background TLS certificate rotation. (Community Bug Fix \$134284186) 

# Aurora MySQL database engine updates 2026-01-02 (version 3.04.6, compatible with MySQL 8.0.28)
<a name="AuroraMySQL.Updates.3046"></a><a name="3.04.6"></a><a name="3.04.6"></a>

 **Version:** 3.04.6

Aurora MySQL 3.04.6 is generally available. Aurora MySQL 3.04 versions are compatible with MySQL 8.0.28. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/). 

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.30Updates.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*. 

You can perform an in-place upgrade that leverages a [zero-downtime-patch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.ZDP.html), restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.04.6 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*. 

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3046.Improvements"></a>

 **Availability improvements** 
+ Fixed an issue which, could cause an engine restart when running `KILL <query-id>` after running `EXPLAIN FOR CONNECTION <query-id>` on a running parallel query.
+ Fixed issues that could cause the writer instance to become unavailable if write forwarding is disabled or reader instances are restarted when using Global Write Forwarding or Local Write Forwarding

 **General improvements** 
+ Fixed an issue that causes reader instances to not generate error logs when write forwarding is enabled and parameter "aurora\$1replica\$1read\$1consistency" is modified.
+ Fixed an issue which can cause some SQL statements to not get logged in the audit log.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3046.Patches"></a>

This release includes all community bug fixes up to and including 8.0.28. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](AuroraMySQL.Updates.MySQLBugs.md#AuroraMySQL.Updates.MySQLBugs.v3) .

# Aurora MySQL database engine updates 2025-05-05 (version 3.04.4, compatible with MySQL 8.0.28)
<a name="AuroraMySQL.Updates.3044"></a><a name="3.04.4"></a><a name="3.04.4"></a>

 **Version:** 3.04.4

Aurora MySQL 3.04.4 is generally available. Aurora MySQL 3.04 versions are compatible with MySQL 8.0.28. For more information on the community changes that have occurred, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/). 

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparison of Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html) in the *Amazon Aurora User Guide*. 

**Note**  <a name="lts_notice_3044"></a>
This version is designated as a long-term support (LTS) release. For more information, see [Aurora MySQL long-term support (LTS) releases](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Update.SpecialVersions.html#AuroraMySQL.Updates.LTS) 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 the next target version for Automatic Minor Version Upgrade campaign, which may not be an LTS version.

You can perform an in-place upgrade that leverages a [zero-downtime-patch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.ZDP.html), restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.04.4 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*. 

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3044.Improvements"></a>

 **Security fixes** 

Critical CVEs:
+  [CVE-2024-11053](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-11053) 
+  [CVE-2024-37371](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-37371) 

 **Availability improvements** 
+ Fixed an issue on the replica where a network interruption may not correctly re-establish connection with the writer.
+ Fixed an issue that can cause a restart on a binary log (binlog) replica when processing a large number of relay log files during [relay log recovery](https://dev.mysql.com/doc/refman/8.0/en/replication-solutions-unexpected-replica-halt.html). 
+ Fixed an issue that causes a database reader instance restart when executing a query using the Parallel Query feature.
+ Fixed an issue that, in rare conditions, can disable binary logging when an error occurs during commit of a large transaction.
+ Fixed an issue that can cause Aurora read replicas to restart in the event of certain rare transaction commit orders on the writer DB instance.
+ Fixed an issue that can lead to a database restart when [scheduled events](https://dev.mysql.com/doc/refman/8.0/en/events-overview.html) are aborted during execution on instances that have Enhanced Binlog enabled.
+ Fixed an issue where database instances using multi TB Aurora cluster volumes, may experience increased downtime during restart due to InnoDB bufferpool validation failures.

 **General improvements** 
+ The following privileges have been added to the `rds_superuser_role`: `FLUSH_OPTIMIZER_COSTS`, `FLUSH_STATUS`, `FLUSH_TABLES`, and `FLUSH_USER_RESOURCES`. For information about the `rds_superuser_role`, see [Amazon Master User Accounts with Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/UsingWithRDS.MasterAccounts.html) in the *Amazon Aurora User Guide*. For more information on these dynamic privileges, please see the [MySQL documentation](https://dev.mysql.com/doc/refman/8.0/en/flush.html). 
+ Fixed an issue where a preserved connection is handled incorrectly during Zero-downtime patching (ZDP)/Zero-downtime restart (ZDR) that can lead to the client waiting indefinitely for a query to complete.
+ Fixed an issue where the row becomes unreadable through the spatial index during an update.
+ Fixed an issue where a query containing an optimizer hint that was aborted during a Zero-downtime restart or Zero-downtime patching operation may be incorrectly handled.
+ Fixed an issue where the commit latency is not measured when `innodb_flush_log_at_trx_commit` is set to `0`. 
+ Introduced optimizations to reduce memory usage during logical [data dictionary](https://dev.mysql.com/doc/refman/8.0/en/data-dictionary.html) recovery when there are a large number of tables.
+ Fixed an issue that caused the `SHOW BINARY LOGS` command to take longer to execute on a cluster where Enhanced Binlog is enabled or was previously enabled. This issue could also cause increased commit latency if multiple `SHOW BINARY LOGS` commands were running concurrently.
+ Fixed a memory issue associated with the default roles of the view definer.
+ Fixed an issue that can cause failure in completing the process of disabling the write forwarding feature.
+ Fixed an issue that can prevent new client connections from being established to the database when write forwarding is enabled.
+ Fixed an issue that can cause a writer database instance to restart when a reader instance using write forwarding executes a DML statement that contains a `timestamp` value and the `time_zone` database parameter is set to "UTC".
+ Fixed an issue that caused intermittent unavailability of an Aurora Read Replica or table definition inconsistencies with error `'Table does not exist'` on the replica due to concurrent read queries on the replica and DDL operations on the writer.
+ Fixed an issue that may cause an incomplete result set when executing queries involving `LEFT-` or `RIGHT-JOIN` operations using the hash-join algorithm with Parallel Query.
+ Starting with this Aurora MySQL version, fast insert optimization is no longer enabled. For more information, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance) in the *Amazon Aurora User Guide*.

 **Upgrades and migrations** 
+ Removed the default roles that were unnecessarily created during the upgrade from AMS2 to AMS3.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3044.Patches"></a>

This release includes all community bug fixes up to and including 8.0.28. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](AuroraMySQL.Updates.MySQLBugs.md#AuroraMySQL.Updates.MySQLBugs.v3) .
+ Fixed an issue that resolves the deadlock when `FLUSH STATUS`, `COM_CHANGE_USER`, and `SHOW PROCESS LIST` are executed concurrently. (Bug\$135218030)

# Aurora MySQL database engine updates 2024-06-26 (version 3.04.3, compatible with MySQL 8.0.28)
<a name="AuroraMySQL.Updates.3043"></a><a name="3.04.3"></a><a name="3.04.3"></a>

**Version:** 3.04.3

Aurora MySQL 3.04.3 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](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html).

**Note**  <a name="lts_notice_3043"></a>
This version is designated as a long-term support (LTS) release. For more information, see [Aurora MySQL long-term support (LTS) releases](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Update.SpecialVersions.html#AuroraMySQL.Updates.LTS) 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 the next target version for Automatic Minor Version Upgrade campaign, which may not be an LTS version.

Currently supported Aurora MySQL releases are 2.07.9, 2.7.10, 2.11.\$1, 2.12.\$1, 3.03.\$1, 3.04.\$1, 3.05.\$1, 3.06.\$1, and 3.07.\$1.

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently available Aurora MySQL version 2 cluster into an Aurora MySQL version 3.04.3 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [Planning a major version upgrade for an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Planning). For general information about Aurora MySQL upgrades, see [Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [Troubleshooting for Aurora MySQL in-place upgrade](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Upgrading.Troubleshooting) in the *Amazon Aurora User Guide*.

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3043.Improvements"></a>

**Fixed security issues and CVEs:**

This release includes all community CVE fixes up to and including MySQL 8.0.28. The following CVE fixes are included:
+ [CVE-2024-0853](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-0853)

**Availability improvements:**
+ Fixed an issue that causes an Aurora MySQL DB instance to restart when running a parallel query.
+ Fixed an issue that can cause a reader DB instance to restart when reading a table that is being altered or dropped on the writer DB instance.
+ Fixed an issue that caused a memory access violation leading to releasing a mutex object no longer owned by the thread.
+ Fixed an issue that can cause an Aurora MySQL writer DB instance to restart when a write forwarding session is closed while running a forwarded query.
+ Fixed an issue that causes a DB instance to restart when handling large GTID sets on a binary log–enabled instance.
+ Fixed an issue when processing `INSERT` queries on InnoDB partitioned tables that can cause a gradual decline of free memory in the DB instance.
+ Fixed an issue that, in rare conditions, can cause a reader instance to restart when performing `SELECT` queries on tables with a foreign key constraint.
+ Fixed an issue that can cause a database to restart when InnoDB data dictionary recovery takes a long time during database recovery.
+ Fixed an issue that can cause a database to restart when a cascading `UPDATE` or `DELETE` foreign key constraint is defined on a table where a virtual column is involved either as a column in the foreign key constraint, or as a member of the referenced table.
+ Fixed an issue in Aurora Serverless v2 that can lead to a database restart while scaling up.

**General improvements:**
+ Fixed an issue that provided an incorrect value for the `threads_running` status variable when using Aurora Global Database.
+ Fixed an issue that causes a DB instance to restart because of inaccurate lock holder information in `rw_lock` when using parallel reads.
+ Fixed a memory management issue that led to a decrease in freeable memory over time when running `SELECT ... INTO OUTFILE ...` queries.
+ Fixed an issue that can cause a DB instance to restart when the local storage on the DB instance reaches full capacity.
+ Fixed an issue where the Performance Schema wasn't enabled when Performance Insights automated management was turned on for db.t4g.medium and db.t4g.large DB instances.
+ Fixed an issue during zero-downtime patching (ZDP) that prevents a DB instance from closing client connections upon reaching the customer-configured of either `wait_timeout` or `interactive_timeout`.
+ Fixed an issue where a `SELECT` query on an Aurora reader instance might fail with the error table doesn't exist when the table has at least one full-text search (FTS) index and a `TRUNCATE` statement is being run on the Aurora writer DB instance.

**Upgrades and migrations:**
+ Fixed an issue that causes upgrades or migrations to fail when the target Aurora MySQL DB engine version is 3.04.0 or higher. This occurs when the `lower_case_table_names` DB cluster parameter is set to `1`, and MySQL database collation is incompatible with lowercase table names.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3043.Patches"></a>

This release includes all community bug fixes up to and including 8.0.28. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](AuroraMySQL.Updates.MySQLBugs.md#AuroraMySQL.Updates.MySQLBugs.v3).

# Aurora MySQL database engine updates 2024-03-15 (version 3.04.2, compatible with MySQL 8.0.28)
<a name="AuroraMySQL.Updates.3042"></a><a name="3.04.2"></a><a name="3.04.2"></a>

**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](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Compare-80-v3.html).

**Note**  <a name="lts_notice_3042"></a>
This version is designated as a long-term support (LTS) release. For more information, see [Aurora MySQL long-term support (LTS) releases](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Update.SpecialVersions.html#AuroraMySQL.Updates.LTS) 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 the next target version for Automatic Minor Version Upgrade campaign, which may not be an LTS version.

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

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) 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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting).

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3042.Improvements"></a>

**Fixed security issues and CVEs:**

The following CVE fixes are included in this release:
+ [CVE-2020-11104](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11104)
+ [CVE-2020-11105](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11105)
+ [CVE-2023-38545](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38545)
+ [CVE-2023-38546](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38546)
+ [CVE-2023-39975](https://nvd.nist.gov/vuln/detail/CVE-2023-39975)

**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](https://dev.mysql.com/doc/refman/8.0/en/show-status.html) and [PURGE BINARY LOGS](https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html) 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\$1import\$1binlog\$1ssl\$1material](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html#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.\$1.
+ 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
<a name="AuroraMySQL.Updates.3042.Patches"></a>

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](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+ Fixed an issue where cache line value can be calculated incorrectly, causing a failure during database restart on Graviton-based instances. (Community Bug Fix \$135479763)
+ 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 \$133852530)

# Aurora MySQL database engine updates 2023-11-13 (version 3.04.1, compatible with MySQL 8.0.28)
<a name="AuroraMySQL.Updates.3041"></a><a name="3.04.1"></a><a name="3.04.1"></a>

**Version:** 3.04.1

Aurora MySQL 3.04.1 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](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

**Note**  <a name="lts_notice_3041"></a>
This version is designated as a long-term support (LTS) release. For more information, see [Aurora MySQL long-term support (LTS) releases](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Update.SpecialVersions.html#AuroraMySQL.Updates.LTS) 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 the next target version for Automatic Minor Version Upgrade campaign, which may not be an LTS version.

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html).

Currently supported Aurora MySQL releases are 2.07.9, 2.7.10, 2.11.\$1, 2.12.\$1, 3.01.\$1, 3.02.\$1, 3.03.\$1, 3.04.\$1, and 3.05.\$1.

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently available Aurora MySQL version 2 cluster into an Aurora MySQL version 3.04.1 cluster.

For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*.

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting).

If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*.

## Improvements
<a name="AuroraMySQL.Updates.3041.Improvements"></a>

 **Availability improvements:** 
+ Fixed an issue where Aurora MySQL database instances using parallel query may experience a database restart when running a high number of concurrent parallel queries. 
+ Fixed an issue which can cause the executed GTID set to be recovered incorrectly on a binary log (binlog) replica cluster with enhanced binlog enabled when any binlog source has set `gtid_mode` to `ON` or `ON_PERMISSIVE`. This issue may cause the replica cluster's writer instance to restart an additional time during recovery, or lead to incorrect results when querying the executed GTID set. 
+ Fixed a memory management issue that can cause an Aurora MySQL database instance restart or a failover due to a decrease in freeable memory when enhanced binary log is enabled. 
+ Fixed an issue which can cause the reader instance to restart when the writer instance grows the database volume to a multiple of 160GB. 
+ Fixed an issue where an Aurora MySQL database instance with the enhanced binary log feature enabled might get stuck during the database instance startup as the binary log recovery process is being executed. 
+ Fixed an issue which can cause a database instance restart due to a deadlatch when running [https://dev.mysql.com/doc/refman/8.0/en/show-status.html](https://dev.mysql.com/doc/refman/8.0/en/show-status.html) and [https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html](https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html) statements concurrently. The purge binary logs is a managed statement that is executed to honor the user configured binlog retention period. 
+ Fixed an issue which can cause database cluster unavailability if the writer instance restarts while the database is creating or dropping triggers on internal system tables. 
+ Fixed an issue which can cause a database instance restart due to a long semaphore wait when using the enhanced binlog feature on a cluster with an Aurora replica. 

 **General improvements:** 
+ Fixed an issue which can cause database unavailability when enhanced binlog is enabled on an Aurora Serverless v2 database cluster running on Aurora MySQL 3.04.0. 
+ Removed unused storage metadata before writing to Aurora Storage when the enhanced binlog feature is enabled. This avoids certain scenarios when a database restart or failover may occur because of increased write latency due to increased bytes transmitted over the network. 
+ Fixed an issue where Aurora specific performance schema tables were not created upon an upgrade or migration. 
+ Fixed an issue which can cause the `NumBinaryLogFiles` metrics on CloudWatch to display incorrect results when enhanced binlog is enabled. 

 **Upgrades and migrations:** 
+ Upgrading from MySQL 5.7 to MySQL 8.0 with a very large number of tables in a single database caused the server to consume excessive memory. It was found that, during the process of checking whether tables could be upgraded, we fetched all the data dictionary `Table` objects upfront, processing each and fetching its name, then performed [https://dev.mysql.com/doc/refman/8.0/en/check-table.html#check-table-version-compatibility](https://dev.mysql.com/doc/refman/8.0/en/check-table.html#check-table-version-compatibility) on the list. Fetching all objects beforehand was not necessary in this case, and contributed greatly to memory consumption. To correct this problem, we now fetch one `Table` object at a time in such cases, performing any required checks, fetching its name, and releasing the object, before proceeding with the next one. (Bug \$134526001)

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3041.Patches"></a>

This release includes all community bug fixes up to and including 8.0.28, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+ Fixed an issue which can cause higher CPU utilization due to background TLS certificate rotation (Community Bug Fix \$134284186) 

# Aurora MySQL database engine updates 2023-07-31 (version 3.04.0) , compatible with MySQL 8.0.28)
<a name="AuroraMySQL.Updates.3040"></a><a name="3.04.0"></a><a name="3.04.0"></a>

 **Version:** 3.04.0 

Aurora MySQL 3.04.0 is generally available. Aurora MySQL 3.04 versions are compatible with MySQL 8.0.28, Aurora MySQL 3.03 versions are compatible with MySQL 8.0.26, and Aurora MySQL 3.02 versions are compatible with MySQL 8.0.23. For more information on community changes that have occurred from 8.0.23 to 8.0.28, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

**Note**  <a name="lts_notice_3040"></a>
This version is designated as a long-term support (LTS) release. For more information, see [Aurora MySQL long-term support (LTS) releases](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Update.SpecialVersions.html#AuroraMySQL.Updates.LTS) 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 the next target version for Automatic Minor Version Upgrade campaign, which may not be an LTS version.

For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html).

 Currently supported Aurora MySQL releases are 2.07.9, 2.11.1, 2.11.2, 3.01.\$1, 3.02.\$1, 3.03.\$1, and 3.04.0. 

You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.04.0 cluster. 

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

**Note**  
Aurora MySQL enhanced binary log (binlog) is currently not supported for the Aurora Serverless v2 database instance on Aurora MySQL version 3.04.0. Enabling this feature may lead to database unavailability. If you require the use of enhanced binary log on Aurora MySQL version 3.04.0, we recommend using a [non-serverless database instance class](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Concepts.DBInstanceClass.html#Concepts.DBInstanceClass.Types) or setting the minimum and maximum ACU of the Serverless v2 database instance to the same value.  
More information on enhanced binary logging in Aurora MySQL is available in the [Aurora User Guide](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.MySQL.html#AuroraMySQL.Enhanced.binlog).

## Improvements
<a name="AuroraMySQL.Updates.3040.Improvements"></a>

**New features:**
+ Improved the performance of queries using InnoDB full-text indices to search phrases in [natural language mode](https://dev.mysql.com/doc/refman/8.0/en/fulltext-natural-language.html). For more information on full text searches in MySQL, refer to [Full-Text Search Functions](https://dev.mysql.com/doc/refman/8.0/en/fulltext-search.html). 
+ Amazon Aurora MySQL supports local (in-cluster) write forwarding. You can now forward write operations from a reader DB instance to a writer DB instance within an Aurora MySQL DB cluster. For more information, see [Using local write forwarding in an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-write-forwarding.html). 
+ Added the capability to change the value of the `aurora_replica_read_consistency` parameter for the [Using write forwarding in an Amazon Aurora global database](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-write-forwarding.html) feature in sessions which have `autocommit` disabled. For more information, see [Configuration parameters for write forwarding](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-write-forwarding.html#aurora-global-database-write-forwarding-params). 
+ Starting with Aurora MySQL 3.04, for the [global database write forwarding](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-write-forwarding.html#aurora-global-database-write-forwarding-params) feature, you can now set the value of the `aurora_replica_read_consistency` parameter via the database cluster and database instance parameter groups. Prior to Aurora MySQL version 3.04, this parameter's value could only be configured at the session level. 

**Fixed security issues and CVEs:**
+ Changed the SSL/TLS provider from OpenSSL to [AWS-LC](https://github.com/aws/aws-lc). This brings a number of changes including, but not limited to the following:
  + Database connections using SSL can now be restored by Zero Downtime Restart and Zero Downtime Patching when upgrading from Aurora MySQL version 3.04.0 to a higher version.
  + Support for TLSv1.3 which includes support for TLS\$1AES\$1128\$1GCM\$1SHA256, TLS\$1AES\$1256\$1GCM\$1SHA384 and TLS\$1CHACHA20\$1POLY1305\$1SHA256 SSL ciphers.
  + Removal of support for less secure DHE-RSA-\$1 ciphers.

  For more information, see [Using TLS with Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Security.html#AuroraMySQL.Security.SSL)
+ Added the dynamic privilege `SHOW_ROUTINE` to the `rds_superuser_role` which enables access to definitions and properties of all stored routines, such as stored procedures and functions. For more details, see [SHOW\$1ROUTINE](https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html#priv_show-routine).
+ Fixed an issue which may cause the audit log to miss events during audit log file rotation.
+ Enabled support for secure and performant Transport Layer Security (TLS) 1.3 protocol while maintaining compatibility with TLS 1.2 version.
+ TLS versions TLSv1 and TLSv1.1 were deprecated in community MySQL 8.0.26 and correspondingly in Aurora MySQL 3.03. These protocols have now been removed in community MySQL 8.0.28 and correspondingly in Aurora MySQL 3.04. By default, any secure client that cannot communicate over TLS 1.2 or higher will be rejected. For more information on connecting to your database instances using TLS, please see [Security with Amazon Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Security.html).

The following CVE fixes are included in this release:
+ [CVE-2023-21963](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21963)
+ [CVE-2023-21912](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21912)
+ [CVE-2023-0215](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0215)
+ [CVE-2022-43551](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-43551)
+ [CVE-2022-37434](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37434)
+ [CVE-2022-21635](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21635)
+ [CVE-2022-21556](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21556)
+ [CVE-2022-21352](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21352)
+ [CVE-2021-35630](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35630)
+ [CVE-2021-35624](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35624)

**Availability improvements:**
+ Fixed an issue that can cause database restarts during long transaction recovery.
+ Fixed an issue within database activity streams event encryption that can cause database restarts.
+ Fixed a memory management issue due to out of memory errors when the InnoDB buffer pool is being initialized during startup or while scaling in Aurora Serverless v2. This issue might have caused database instance restarts or performance degradation including throughput reduction or increased latency.
+ Fixed an issue that can cause an Aurora MySQL reader instance to restart while executing a query which utilizes an Aurora MySQL parallel query execution plan.
+ Fixed an issue that, in certain situations, can cause Aurora reader instances to restart during a range estimation.
+ Fixed an issue that can interrupt database recovery during startup if the restart occurred while executing heavy insert operations involving auto-increment columns.
+ Fixed an issue with Aurora advanced auditing that causes excess logging of informational messages to the Aurora MySQL error log when the server variable `server_audit_events` is set to `ALL` or `QUERY`. This issue might cause a database instance restart.
+ Fixed an issue that can cause a database restart during the rollback of an `INSERT` statement when parallel query is enabled.
+ Fixed an issue that can cause the database instance to restart when running the `EXPLAIN ANALYZE` profiling tool on a query which returned the output `all select tables were optimized away` within the `EXTRA` information column. For more information, see the MySQL documentation on [`EXPLAIN` Output Format](https://dev.mysql.com/doc/refman/8.0/en/explain-output.html).
+ Fixed an issue that can cause an Aurora global database secondary Region reader instance using global write forwarding to restart when a forwarded [implicit commit statement](https://dev.mysql.com/doc/refman/8.0/en/implicit-commit.html) encounters an error.
+ Fixed an issue that can cause the writer instance in an Aurora global database primary Region to restart when a `SELECT FOR UPDATE` query is executed using global write forwarding from an Aurora global database secondary Region.

 **General improvements:** 
+ Added a new stored procedure, `mysql.rds_gtid_purged`, to allow customers to set the `GTID_PURGED` system variable. For more information, see [mysql.rds\$1gtid\$1purged](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html#mysql_rds_gtid_purged). 
+ Added two new stored procedures, `mysql.rds_start_replication_until` and `mysql.rds_start_replication_until_gtid`, which allow customers to configure a location to stop binary log replication. For more information on configuring a stop location for binary log replication in Aurora MySQL, see [mysql.rds\$1start\$1replication\$1until](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/mysql-stored-proc-replicating.html#mysql_rds_start_replication_until). 
+ Fixed an issue that would prevent [Aurora MySQL replication control stored procedures](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html) from modifying the [https://dev.mysql.com/doc/refman/8.0/en/set-sql-log-bin.html](https://dev.mysql.com/doc/refman/8.0/en/set-sql-log-bin.html) variable, when called from a session with autocommit mode disabled. 
+ Added logical replication support for the following Data Control Language (DCL) statements: `GRANT/REVOKE` and `CREATE/DROP/ALTER/RENAME USER`. 
+ Fixed an issue to prevent InnoDB statistics from getting stale, which can sometimes generate a sub-optimal query execution plan that may lead to an increase in the query execution time. 
+ Added two new system views, `information_schema.aurora_global_db_instance_status` and `information_schema.aurora_global_db_status`. These views can be used to display the status and topology of primary and secondary resources in an Aurora MySQL global database cluster. The details of the two system views can be found here, [Aurora MySQL–specific information\$1schema tables](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ISTables.html). 
+ Fixed an issue where a user is unable to access the database with a wildcard character in the database name after executing the `SET ROLE` statement with an escaped wildcard character. 
+ Fixed an issue where events that were reported while processing audit log rotations might not be written to the audit log. 
+ Fixed an issue where creating an internal temporary table, via a `TRIGGER` execution, can cause a writer database instance to restart. 
+ Added a new system variable, `innodb_aurora_max_partitions_for_range`. In some cases where persisted stats are not available, this parameter can be used to improve the execution time of row count estimations on partitioned tables. More information can be found in the documentation, [Aurora MySQL configuration parameters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html). 
+ Fixed an issue which incorrectly allows customers to set `ROW_FORMAT` as `COMPRESSED` when creating partitioned tables. Tables will be implicitly converted to `COMPACT` format with a warning to inform that Aurora MySQL doesn't support compressed tables. 
+ Fixed an issue that can cause multithreaded binary log replication to stop when the `replica_parallel_type` variable is set to `LOGICAL_CLOCK` and the `replica_preserve_commit_order` variable is turned `ON`. This issue can occur when a transaction larger than 500 MB is run on the source.
+ Fixed an issue when the [global database write forwarding](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-write-forwarding.html) feature is enabled that can cause changes to the `performance_schema` configuration on the reader instances in the secondary Regions to be unintentionally forwarded to the writer instance in the primary Region. 
+ Fixed an issue where the server status variable `innodb_buffer_pool_reads` may not be updated after a data page is read from the Aurora storage file system. 
+ Aurora MySQL parallel query is not supported when choosing the Aurora I/O-Optimized cluster configuration. For more information, see [Amazon Aurora MySQL parallel query limitations](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-parallel-query.html#aurora-mysql-parallel-query-limitations). 
+ Fixed an issue, when parallel query is enabled, that causes the query plan optimizer to pick an inefficient execution plan for certain `SELECT` queries that benefit from a primary or secondary index. 
+ Upgraded the time zone definitions to the IANA 2023c version.
+ Introduced file management performance optimizations on binlog replicas to help reduce contention when writing to relay log files.
+ Fixed an issue where the `RPO_LAG_IN_MILLISECONDS` column in the `information_schema.aurora_global_db_status` table and `AuroraGlobalDBRPOLag` CloudWatch metric always displayed zero regardless of the user workload.
+ Introduced a new parameter `aurora_tmptable_enable_per_table_limit`. When this parameter is enabled, the `tmp_table_size` variable defines the maximum size of the individual in-memory internal temporary table created by the TempTable storage engine. For additional details, see [Storage engine for internal (implicit) temporary tables](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/ams3-temptable-behavior.html#ams3-temptable-behavior-engine).
+ Fixed an issue where an additional connection is created when the [global database write forwarding](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-write-forwarding.html) feature is enabled. The issue occurs when read-only transactions on a reader instance incorrectly forward an implicit commit to the writer.
+ Fixed an issue where the `PROCESSLIST_USER` and `PROCESSLIST_HOST` fields in the `performance_schema.threads` table were not populated on the writer in the primary Region for connections using the [global database write forwarding](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-write-forwarding.html) feature. More information about this table and Performance Schema can be found in the MySQL Reference Manual, [The threads Table](https://dev.mysql.com/doc/refman/8.0/en/performance-schema-threads-table.html), and the Amazon Aurora User Guide [Overview of the Performance Schema](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_PerfInsights.EnableMySQL.html#USER_PerfInsights.EnableMySQL.overview).
+ Fixed an issue where the `CommitLatency` Cloudwatch metric displayed incorrect values for reader instances in secondary Regions when the [global database write forwarding](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-write-forwarding.html) feature is used. To monitor the forwarded DML statement latency on secondary database clusters, it is recommended to use the `ForwardingReplicaDMLLatency` and `ForwardingWriterDMLLatency` metrics. Commit latency can also be observed using the `CommitLatency` metric on the primary Region's writer instance. More information is available in the Aurora User Guide, [Amazon CloudWatch metrics for write forwarding](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-write-forwarding.html#aurora-global-database-write-forwarding-cloudwatch).
+ Fixed an issue where the [Aurora MySQL replication control stored procedures](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html) used to manage and configure binary log replication incorrectly report errors when multi-threaded binary log replication is configured by setting the [https://dev.mysql.com/doc/refman/8.0/en/replication-options-replica.html#sysvar_replica_parallel_workers](https://dev.mysql.com/doc/refman/8.0/en/replication-options-replica.html#sysvar_replica_parallel_workers) variable's value greater than 0.
+ Fixed an issue that can cause high CPU consumption when multiple sessions are trying to access a page that doesn't exist in memory.

 **Upgrades and migrations:** 
+ To perform a minor version upgrade for an Aurora global database from Aurora MySQL version 3.01, 3.02 or 3.03 to Aurora MySQL version 3.04 or higher, refer to [Upgrading Aurora MySQL by modifying the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html#AuroraMySQL.Updates.Patching.ModifyEngineVersion). 
+ Fixed an issue that can cause upgrade precheck failures due to schema inconsistency errors reported for the `mysql.general_log_backup`, `mysql.general_log`, `mysql.slow_log_backup` and `mysql.slow_log` tables when upgrading from Aurora MySQL 2 to Aurora MySQL 3. For more information about upgrade troubleshooting, see [Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting).
+ Fixed an issue which can cause major version upgrade failures when upgrading to Aurora MySQL 3 when a trigger definition contains a reserved keyword that is not within quotes.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3040.Patches"></a>

This release includes all community bug fixes up to and including 8.0.28, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+  Fixed an issue where a buffer block containing intrinsic temporary table page was relocated during page traversal, causing an assertion failure (Bug\$1 33715694) 
+ InnoDB: Prevent online DDL operations from accessing out-of-bounds memory (Bug\$1 34750489, Bug\$1 108925) 
+ Fixed an issue which can sometimes produce incorrect query results while processing complex SQL statements consisting of multiple nested Common Table Expressions (CTEs) (Bug\$1 34572040, Bug\$1 34634469, Bug\$1 33856374) 

# Aurora MySQL database engine updates 2023-12-08 (version 3.03.3) (Deprecated)
<a name="AuroraMySQL.Updates.3033"></a><a name="3.03.3"></a><a name="3.03.3"></a>

 **Version:** 3.03.3 

 Aurora MySQL 3.03.3 is generally available. Aurora MySQL 3.03 versions are compatible with MySQL 8.0.26. For more information on community changes that have occurred from 8.0.23 to 8.0.28, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

 For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html). 

 Currently available Aurora MySQL releases are 2.07.9, 2.07.10, 2.11.\$1, 2.12.\$1, 3.01.\$1, 3.02.\$1, 3.03.\$1, 3.04.\$1, and 3.05.\$1. 

 You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently available Aurora MySQL version 2 cluster into an Aurora MySQL version 3.03.3 cluster. 

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3033.Improvements"></a>

**Fixed security issues and CVEs listed below:**

Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes are below:
+ [CVE-2023-38545](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38545)

 **Availability improvements:** 
+ Fixed an issue where Aurora MySQL database instances using parallel query may experience a database restart when running a high number of concurrent parallel queries.
+ Fixed an issue which can cause the executed GTID set to be recovered incorrectly on a binary log (binlog) replica cluster with enhanced binlog enabled when any binlog source has `gtid_mode` set to `ON` or `ON_PERMISSIVE`. This issue may cause the replica cluster's writer instance to restart an additional time during recovery, or lead to incorrect results when querying the executed GTID set.
+ Fixed a memory management issue that can cause an Aurora MySQL database instance restart or a failover due to a decrease in the freeable memory when enhanced binary log is enabled.
+ Fixed an issue which can cause the reader instance to restart when the writer instance grows the database volume to a multiple of 160GB.
+ Fixed an issue where an Aurora MySQL database instance with the enhanced binary log feature enabled might get stuck during the database instance startup as the binary log recovery process is being executed.
+ Fixed an issue during zero downtime patching which causes an instance restart that leads to the database connections being unexpectedly closed.
+ Fixed an issue which can cause a database instance restart due to a deadlatch when running [https://dev.mysql.com/doc/refman/8.0/en/show-status.html](https://dev.mysql.com/doc/refman/8.0/en/show-status.html) and [https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html](https://dev.mysql.com/doc/refman/8.0/en/purge-binary-logs.html) statements concurrently. The purge binary logs is a managed statement that is executed to honor the user configured binlog retention period.
+ Fixed an issue which can cause a database instance restart due to a long semaphore wait when using the enhanced binlog feature on a cluster with an Aurora replica.

 **General improvements:** 
+ Removed unused storage metadata before writing to Aurora storage when the enhanced binlog feature is enabled. This avoids certain scenarios when a database restart or failover may occur because of increased write latency due to increased bytes transmitted over the network.
+ Fixed an issue which can cause the `NumBinaryLogFiles` metrics on CloudWatch to display incorrect results when enhanced binlog is enabled.
+ Fixed an issue which can cause the modification of the `table_open_cache` database parameter to not take effect until the database instance is restarted.
+ Fixed an issue which can cause a database restart when connected binary log (binlog) consumers are using duplicate binlog replication server IDs.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3033.Patches"></a>

This release includes all community bug fixes up to and including 8.0.26, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+  Fixed an issue which can cause higher CPU utilization due to background TLS certificate rotation (Community Bug Fix \$134284186) 

# Aurora MySQL database engine updates 2023-08-29 (version 3.03.2) (Deprecated)
<a name="AuroraMySQL.Updates.3032"></a><a name="3.03.2"></a><a name="3.03.2"></a>

 **Version:** 3.03.2 

 Aurora MySQL 3.03.2 is generally available. Aurora MySQL 3.04 versions are compatible with MySQL 8.0.28, Aurora MySQL 3.03 versions are compatible with MySQL 8.0.26, and Aurora MySQL 3.02 versions are compatible with MySQL 8.0.23. For more information on community changes that have occurred from 8.0.23 to 8.0.28, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

 For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html). 

 Currently available Aurora MySQL releases are 2.07.9, 2.07.10, 2.11.\$1, 3.01.\$1, 3.02.\$1, 3.03.\$1, and 3.04.\$1. 

 You can perform an in-place upgrade, restore a snapshot, or initiate a managed blue/green upgrade using [Amazon RDS Blue/Green Deployments](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/blue-green-deployments-overview.html) from any currently available Aurora MySQL version 2 cluster into an Aurora MySQL version 3.03.2 cluster. 

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3032.Improvements"></a>

**Fixed security issues and CVEs:**
+ Fixed an issue that might cause the audit log to miss events during audit log file rotation.

The following CVE fixes are included in this release:
+ [CVE-2023-21963](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21963)
+ [CVE-2023-21912](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21912)
+ [CVE-2023-0215](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-0215)
+ [CVE-2022-43551](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-43551)
+ [CVE-2022-37434](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37434)

 **Availability improvements:** 
+ Fixed an issue that can cause database restarts during long transaction recovery.
+ Fixed an issue that can cause the database cluster to become unavailable when the writer instance restarts while the database was creating or dropping triggers on internal system tables.
+ Fixed an issue that can cause a database instance to restart while executing a query which references an aggregate function.
+ Fixed an issue that can cause a database restart during the rollback of an `INSERT` statement when parallel query is enabled.
+ Fast insert is enabled only for regular InnoDB tables in Aurora MySQL version 3.03.2 and higher. This optimization doesn’t work for InnoDB temporary tables. For more information on the fast insert optimization, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance).

 **General improvements:** 
+ Fixed an issue where the reader instance is unable to open a table, with `ERROR 1146`. This issue occurs when executing certain types of online Data Definition Language (DDL) while the `INPLACE` algorithm is being used on the writer instance.
+ Introduced file management performance optimizations on binlog replicas to help reduce contention when writing to relay log files.
+ Fixed an issue when parallel query is enabled that causes the query plan optimizer to pick an inefficient execution plan for certain `SELECT` queries that benefit from a primary or secondary index.
+ Added logical replication support for the following Data Control Language (DCL) statements: `GRANT/REVOKE` and `CREATE/DROP/ALTER/RENAME USER`.
+ Parallel query for Amazon Aurora MySQL is not supported when choosing the Aurora I/O-Optimized cluster configuration. See [ Limitations of parallel query for Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-parallel-query.html#aurora-mysql-parallel-query-limitations) for more information.

 **Upgrades and migrations:** 
+ To perform a minor version upgrade for an Aurora global database from Aurora MySQL version 3.01 or 3.02 to Aurora MySQL version 3.03 or higher, refer to [Upgrading Aurora MySQL by modifying the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html#AuroraMySQL.Updates.Patching.ModifyEngineVersion).
+ Fixed an issue which can cause major version upgrade failures when upgrading to Aurora MySQL version 3 when a trigger definition contains a reserved keyword that is not enclosed in quotation marks.

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3032.Patches"></a>

This release includes all community bug fixes up to and including 8.0.26, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+  Fixed an issue which can sometimes produce incorrect query results while processing complex SQL statements consisting of multiple nested Common Table Expressions (CTEs). (Bug \$134572040, Bug \$134634469, Bug \$133856374) 
+  InnoDB: A race condition between threads attempting to deinitialize and initialize statistics for the same table raised an assertion failure. (Bug \$133135425) 
+  InnoDB: Prevent online DDL operations from accessing out-of-bounds memory. (Bug \$134750489, Bug \$1108925) 

# Aurora MySQL database engine updates 2023-05-11 (version 3.03.1) (Deprecated)
<a name="AuroraMySQL.Updates.3031"></a><a name="3.03.1"></a><a name="3.03.1"></a>

 **Version:** 3.03.1 

 Aurora MySQL 3.03.1 is generally available. Aurora MySQL 3.03 versions are compatible with MySQL 8.0.26, and Aurora MySQL 3.02 versions are compatible with MySQL 8.0.23. For more information on community changes that have occurred from 8.0.23 to 8.0.26, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

 For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html). 

 Currently supported Aurora MySQL releases are 2.07.9, 2.11.1, 2.11.2, 3.01.\$1, 3.02.\$1 and 3.03.\$1. 

You can perform an in-place upgrade or restore a snapshot from any currently supported Aurora MySQL version 2 cluster into Aurora MySQL 3.03.1.

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3031.Improvements"></a>

 **New features:** 
+ Aurora Optimized I/O storage configuration is available starting from version 3.03.1. For more information, see [Storage configurations for Amazon Aurora DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Overview.StorageReliability.html#aurora-storage-type). 
+ Added a new system variable, `innodb_aurora_max_partitions_for_range`. In some cases where persisted stats are not available, this parameter can be used to improve the execution time of row count estimations on partitioned tables. More information can be found in the documentation, [Aurora MySQL configuration parameters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.ParameterGroups.html). 

**Availability improvements:**
+ Fixed an issue which can cause the database instance to restart due to incorrectly accessing invalid memory when a connection is closed immediately after committing a transaction.
+ Fixed an issue with Aurora Advanced Auditing that causes excess logging of informational messages to the Aurora MySQL error log when the server variable `server_audit_events` is set to ALL or QUERY. This issue may cause a database instance restart.
+ Fixed an issue which, in certain situations, can cause Aurora reader instances to restart when attempting to read a page which is no longer accessible during a range estimation. 
+ Fixed an issue which can cause an Aurora MySQL reader instance to restart while executing a query which utilizes an Aurora parallel query execution plan.
+ Fixed an issue where database instances using binary log replication may experience an increase in CPU utilization and connection failures when multiple binary log replication consumers are attached.
+ Fixed an issue where unsupported index scan access methods were considered for common table expressions (CTE) while materializing intermediate temporary tables, which can lead to undesired behavior including database restarts or incorrect query results. We fix this issue by avoiding the use of such unsupported index scan access methods on tables using the TempTable storage engine.
+ Fast insert isn't enabled in this Aurora MySQL version, due to an issue that can cause inconsistencies when running queries such as `INSERT INTO`, `SELECT`, and `FROM`. For more information on the fast insert optimization, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance).

 **General improvements:** 
+ Fixed an issue which can cause higher than expected execution times for the SHOW BINARY LOGS statement. This could lead to a drop in commit throughput of the database.
+ Fixed an issue which can cause parallel export for user tables that have columns added using the Instant ADD COLUMN functionality to fail.
+ Fixed an issue where events that were reported while processing audit log rotations might not be written to the audit log.
+ Fixed an issue which may cause depletion of available memory when executing queries against the INFORMATION\$1SCHEMA INNODB\$1TABLESPACES table.
+ Fixed an issue which incorrectly allows customers to set ROW\$1FORMAT as COMPRESSED when creating partitioned tables. Tables will be implicitly converted to COMPACT format with a warning to inform that Aurora MySQL doesn’t support compressed tables.

 **Upgrades and migrations:** 
+ To perform a minor version upgrade for an Aurora global database from Aurora MySQL version 3.01 or 3.02 to Aurora MySQL version 3.03 or higher, refer to [Upgrading Aurora MySQL by modifying the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html#AuroraMySQL.Updates.Patching.ModifyEngineVersion). 
+ Fixed an issue that can cause upgrade precheck failures due to schema inconsistency errors reported for the `mysql.general_log_backup`, `mysql.general_log`, `mysql.slow_log_backup` and `mysql.slow_log` tables when upgrading from Aurora MySQL 2 to Aurora MySQL 3. For more information about upgrade troubleshooting, see [Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting).

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.3031.Patches"></a>

This release includes all community bug fixes up to and including 8.0.26, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+  Fixed an issue where a buffer block containing intrinsic temporary table page was relocated during page traversal, causing an assertion failure. (Bug \$133715694) 

# Aurora MySQL database engine updates 2023-03-01 (version 3.03.0) (Deprecated)
<a name="AuroraMySQL.Updates.3030"></a><a name="3.03.0"></a><a name="3.03.0"></a>

 **Version:** 3.03.0 

 Aurora MySQL 3.03.0 is generally available. Aurora MySQL 3.03 versions are compatible with MySQL 8.0.26, and Aurora MySQL 3.02 versions are compatible with MySQL 8.0.23. For more information on community changes that have occurred from 8.0.23 to 8.0.26, see [MySQL 8.0 Release Notes](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/).

 For details of the new features in Aurora MySQL version 3, see [Aurora MySQL version 3 compatible with MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html). For differences between Aurora MySQL version 3 and Aurora MySQL version 2, see the [Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-v2-v3.html). For a comparison of Aurora MySQL version 3 and MySQL 8.0 Community Edition, see [Comparing Aurora MySQL version 3 and MySQL 8.0 Community Edition](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Compare-80-v3.html). 

 Currently supported Aurora MySQL releases are 2.07.\$1, 2.11.\$1, 3.01.\$1, 3.02.\$1 and 3.03.\$1. 

You can perform an in-place upgrade or restore a snapshot from any currently supported Aurora MySQL version 2 cluster into Aurora MySQL 3.03.0.

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3030.Improvements"></a>

**Fixed security issues and CVEs listed below:**

Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes below:
+ [CVE-2022-32221](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32221)
+ [CVE-2022-21451](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21451)
+ [CVE-2022-21444](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21444)

**Availability improvements:**
+ Fixed an issue where larger DB instance classes may experience issues during restart due to the buffer pool initialization taking longer than expected.
+ Fixed an issue where the DB instance may restart during the database recovery process when binary logging is enabled.
+ Fixed an issue that can cause connection failures on reader instances while executing Data Control Language (DCL) statements, for example `GRANT` and `REVOKE`, or while establishing new connections on the writer instance.
+ Fixed an issue where parallel query was incorrectly used for Data Manipulation Language (DML) operations, such as the `DELETE` and `UPDATE` statements, which aren't currently supported, that led to a DB instance restart. For more information on operations supported in parallel query, see [Aurora MySQL parallel query limitations](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-parallel-query.html#aurora-mysql-parallel-query-limitations).
+ Fixed an issue which, in rare cases, can cause Aurora replicas to restart during the simultaneous execution of large update operations or Data Definition Language (DDL) workloads on the writer instance and read operations on the same set of tables on the Aurora replica.
+ Fixed an issue with the Aurora Serverless v2 reader instance scale down operation that can cause that reader instance to restart, and in some rare cases, cause data inconsistency.
+ Fixed an issue which can cause the DB instance to restart due to incorrectly accessing an invalid memory location when a connection to the DB instance is closed.
+ Fixed an issue which, in rare conditions, can cause the DB instance to restart while processing a query with a `GROUP BY` clause that truncates a decimal column to zero decimal places.
+ Fixed an issue that can cause a DB instance restart due to incorrectly accessing a record when executing a range query using spatial index.
+ Fixed an issue that can cause a DB instance restart on Aurora MySQL replica instances when internal temporary tables exceed the default or customer-configured memory or mmap values.
+ Fixed an issue where the Advanced Audit log rotation may cause memory management issues.
+ Fast insert isn't enabled in this Aurora MySQL version, due to an issue that can cause inconsistencies when running queries such as `INSERT INTO`, `SELECT`, and `FROM`. For more information on the fast insert optimization, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance).

**General improvements:**
+ Improved the read query latency of global database write forwarding sessions using the GLOBAL read consistency setting.
+ Fixed an issue where the `wait_timeout` parameter value wasn't being honored after a client session executed the `reset_connection` or `change_user` commands.
+ Fixed an issue where applications may experience increased latency while connecting to a DB instance when the instance is experiencing a sudden increase in incoming connections. Two new CloudWatch metrics, `AuroraSlowHandshakeCount` and `AuroraSlowConnectionHandleCount`, were introduced to help troubleshoot connection establishment delays for Aurora MySQL DB instances. More information on these metrics can be found in the Aurora CloudWatch metrics definitions documentation, [Amazon CloudWatch metrics for Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Monitoring.Metrics.html).
+  The `temptable_use_mmap` parameter has been deprecated, and support for it is expected to be removed in a future MySQL release. For more information, see [Storage engine for internal (implicit) temporary tables](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/ams3-temptable-behavior.html#ams3-temptable-behavior-engine).
+ Fixed an issue which can cause higher than expected execution times for the `SHOW BINARY LOGS` statement. This could lead to a drop in the commit throughput of the database.

 **Upgrades and migrations:** 
+ To perform a minor version upgrade for an Aurora global database from Aurora MySQL version 3.01 or 3.02 to Aurora MySQL version 3.03 or higher, refer to [Upgrading Aurora MySQL by modifying the engine version](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html#AuroraMySQL.Updates.Patching.ModifyEngineVersion).
+ Fixed an issue that can cause major version upgrades from Aurora MySQL version 2 to Aurora MySQL version 3 to fail when there are a large number of tables (over 750K) in the cluster.
+ Fixed an issue that can cause major version upgrades from Aurora MySQL version 2 to Aurora MySQL version 3 to fail because migrating the `mysql.innodb_table_stats` and `mysql.innodb_index_stats` tables took longer than expected. This issue mainly affected DB clusters with millions of tables.
+ Fixed an issue that can cause failures while upgrading from Aurora MySQL version 2 to Aurora MySQL version 3 due to schema inconsistency errors. These errors are reported by the upgrade pre-checker for the `mysql.general_log_template` and `mysql.slow_log_template` tables. For more information about upgrade troubleshooting, see [Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting).
+ Fixed an issue that can cause upgrade failures from Aurora MySQL version 2 to Aurora MySQL version 3 due to the `schemaInconsistencyCheck` error. This error is caused by schema inconsistencies within the `mysql.table_migration_index_info` table, as reported by the `upgrade-prechecks.log`. For more information about troubleshooting upgrades to Aurora MySQL version 3, see [Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.html#AuroraMySQL.mysql80-upgrade-troubleshooting).

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.2102.Patches"></a>

This release includes all community bug fixes up to and including 8.0.26, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+  Fixed an issue where sorts of some column types, including `JSON` and `TEXT`, sometimes exhausted the sort buffer if its size wasn't at least 15 times that of the largest row in the sort. Now the sort buffer need only be 15 times as large as the largest sort key. (Bug \$1103325, Bug \$1105532, Bug \$132738705, Bug \$133501541) 
+  Fixed an issue where InnoDB did't always handle some legal names for table partitions correctly. (Bug \$132208630) 
+  Fixed an issue which, in certain conditions, may return incorrect results due to an inaccurate calculation of the nullability property when executing a query with an `OR` condition. (Bug \$134060289) 
+  Fixed an issue which, in certain conditions, may return incorrect results when the following two conditions are met: 
  + a derived table is merged into the outer query block 
  + the query includes a left join and an `IN` subquery 

  (Bug \$134060289) 
+  Fixed an issue where incorrect `AUTO_INCREMENT` values were generated when the maximum integer column value was exceeded. The error was due to the maximum column value not being considered. The previous valid `AUTO_INCREMENT` value should have been returned in this case, causing a duplicate key error. (Bug \$187926, Bug \$126906787) 
+  Fixed an issue where it wasn't possible to revoke the `DROP` privilege on the Performance Schema. (Bug \$133578113) 
+  Fixed an issue where a stored procedure containing an `IF` statement using `EXISTS`, which acted on one or more tables that were deleted and recreated between executions, didn't execute correctly for the subsequent invocations following the first one. (Bug \$132855634). 
+  Fixed an issue where a query that references a view in a subquery and an outer query block can cause an unexpected restart. (Bug\$132324234) 

# Aurora MySQL database engine updates 2023-04-17 (version 3.02.3) (Deprecated)
<a name="AuroraMySQL.Updates.3023"></a><a name="3.02.3"></a><a name="3.02.3"></a>

 **Version:** 3.02.3 

 Aurora MySQL 3.02.3 is generally available. Aurora MySQL 3.02 versions are compatible with MySQL 8.0.23, and Aurora MySQL 2.x versions are compatible with MySQL 5.7. 

 For details of the new features in Aurora MySQL version 3, and differences between Aurora MySQL version 3 and Aurora MySQL version 2 or community MySQL 8.0, see [ Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.Compare-v2-v3) in the *Amazon Aurora User Guide*. 

 Currently supported Aurora MySQL releases are 2.07.\$1, 2.11.1, 2.11.2, 3.01.\$1, 3.02.\$1, and 3.03.\$1. 

You can perform an in-place upgrade or restore a snapshot from any currently supported Aurora MySQL version 2 cluster into Aurora MySQL 3.02.3.

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For the upgrade procedure itself, see [ Upgrading to Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-procedure) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3023.Improvements"></a>

**Availability improvements:**
+ Fixed an issue which can cause the database instance to restart due to incorrectly accessing invalid memory when a connection is closed immediately after committing a transaction.
+ Fast insert isn't enabled in this Aurora MySQL version, due to an issue that can cause inconsistencies when running queries such as `INSERT INTO`, `SELECT`, and `FROM`. For more information on the fast insert optimization, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance).

**General improvements:**
+ Fixed an issue where unsupported index scan access methods were considered for common table expressions (CTE) while materializing intermediate temporary tables, which can lead to undesired behavior including database restarts or incorrect query results. This issue was fixed by avoiding the use of such unsupported index scan access methods on tables using the TempTable storage engine.
+ Fixed an issue which, in rare cases, can cause an Aurora MySQL reader instance to restart when accessing a table which has large update or Data Definition Language (DDL) operations running concurrently on the Aurora MySQL writer instance.
+ Fixed an issue which, in certain situations, can cause Aurora MySQL reader instances to restart when attempting to read a page which is no longer accessible during a range estimation.
+ Fixed an issue where database instances using binary log replication may experience an increase in CPU utilization and connection failures when multiple binary log replication consumers are attached.
+ Fixed an issue which can cause an Aurora MySQL reader instance to restart while executing a query which utilizes an Aurora parallel query execution plan.

# Aurora MySQL database engine updates 2022-11-18 (version 3.02.2) (Deprecated)
<a name="AuroraMySQL.Updates.3022"></a><a name="3.02.2"></a><a name="3.02.2"></a>

 **Version:** 3.02.2 

 Aurora MySQL 3.02.2 is generally available. Aurora MySQL 3.02 versions are compatible with MySQL 8.0.23, Aurora MySQL 2.x versions are compatible with MySQL 5.7, and Aurora MySQL 1.x versions are compatible with MySQL 5.6. 

 For details of new features in Aurora MySQL version 3 and differences between Aurora MySQL version 3 and Aurora MySQL version 2 or community MySQL 8.0, see [ Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.Compare-v2-v3) in the *Amazon Aurora User Guide*. 

 Currently supported Aurora MySQL releases are 1.19.5, 1.19.6, 1.22.\$1, 1.23.\$1, 2.04.\$1, 2.07.\$1, 2.08.\$1, 2.09.\$1, 2.10.\$1, 3.01.\$1 and 3.02.\$1. 

You can restore a snapshot from any currently supported Aurora MySQL version 2 cluster into Aurora MySQL 3.02.2.

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For the upgrade procedure itself, see [ Upgrading to Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-procedure) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3022.Improvements"></a>

Aurora MySQL version 3.02.2 is generally available and generally compatible with community MySQL 8.0.23.

**Fixed security issues and CVEs listed below:**

Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes below:
+ [CVE-2022-21451](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21451)
+ [CVE-2021-36222](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36222)
+ [CVE-2021-22926](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22926)
+ [CVE-2022-21444](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21451)

**Availability improvements:**
+ Fixed an issue which can cause the database instance to restart due to incorrectly accessing the invalid memory when a connection to the database instance is closed explicitly or implicitly.
+ Fixed an issue which can cause the database startup to be interrupted repeatedly on larger instance classes due to buffer pool initialization taking longer than expected.
+ Fixed an issue which, in rare conditions, can cause the database instance to restart when Aurora Serverless v2 incorrectly attempts to update the table cache while scaling.
+ Fixed an issue which, in rare conditions, could cause the database to restart when processing a query with a GROUP BY clause that truncates a decimal column to zero decimal places. 
+ Fast insert isn't enabled in this Aurora MySQL version, due to an issue that can cause inconsistencies when running queries such as `INSERT INTO`, `SELECT`, and `FROM`. For more information on the fast insert optimization, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance).

**General improvements:**
+ Fixed an issue that can cause upgrade failures from Aurora MySQL version 2 (compatible with MySQL 5.7) to Aurora MySQL version 3 (compatible with MySQL 8.0) due to a metadata inconsistency in the mysql.host table.
+ Added performance improvements to reduce the upgrade time from Aurora MySQL version 2 (compatible with MySQL 5.7) to Aurora MySQL version 3 (compatible with MySQL 8.0). By parallelizing certain upgrade steps, the time is further shortened when using larger instance classes, such as db.r6g.16xlarge or db.r5.24xlarge.
+ Added support for displaying all errors when upgrading from Aurora MySQL version 2 (compatible with MySQL 5.7) to Aurora MySQL version 3 (compatible with MySQL 8.0) when previous versions were limited to displaying only 50 errors.
+ Fixed an issue, which in rare conditions, can cause the auto-increment counters to be incorrect after a major version upgrade from Aurora MySQL version 2 (compatible with MySQL 5.7) to Aurora MySQL version 3 (compatible with MySQL 8.0).
+ Fixed an issue that can cause major version upgrades from Aurora MySQL version 2 to Aurora MySQL version 3 to fail because migrating the `mysql.innodb\$1table\$1stats` and `mysql.innodb\$1index\$1stats` tables took longer than expected. This issue mainly affected database clusters with a large numbers of tables (>1.5 million).
+ Fixed an issue that can cause major version upgrades from Aurora MySQL version 2 to Aurora MySQL version 3 to fail due to a defect in AMS 8.0 engine upgrade workflow, which causes the log records to be accumulated on the Aurora storage cluster volume and stops normal write operations. This issue mainly affected database clusters with large numbers of tables, approximately >750k.
+ Fixed an issue that prevents Aurora MySQL Serverless v2 idle instances from scaling down to 0.5 ACUs because the MySQL purge threads were incorrectly kept active.
+ Fixed an issue where applications may experience increased latency while connecting to a database instance when the instance is experiencing a sudden increase in incoming connections.
+ Introduced two new Amazon CloudWatch metrics to help troubleshoot connection establishment delays for Aurora MySQL database instances. More information on AuroraSlowHandshakeCount and AuroraSlowConnectionHandleCount metrics can be found in the [Aurora CloudWatch metrics definitions](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Monitoring.Metrics.html).

## Integration of MySQL Community Edition bug fixes
<a name="AuroraMySQL.Updates.2102.Patches"></a>

This release includes all community bug fixes up to and including 8.0.23, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+ Fixed an issue which, in certain conditions, may return incorrect results due to an inaccurate calculation of the nullability property when executing a query with an OR condition. (Bug \$134060289) 
+ Fixed an issue which, in certain conditions, may return incorrect results when the following two conditions are met:
  + A derived table is merged into the outer query block.
  + The query includes a left join and an IN subquery. (Bug \$134060289)
+ Fixed an issue where it was not possible to revoke the DROP privilege on the Performance Schema. (Bug \$133578113)
+ Fixed an issue where a stored procedure containing an IF statement using EXISTS, which acted on one or more tables that were deleted and recreated between executions, did not execute correctly for subsequent invocations following the first one. (MySQL Bug \$132855634).
+ Incorrect AUTO\$1INCREMENT values were generated when the maximum integer column value was exceeded. The error was due to the maximum column value not being considered. The previous valid AUTO\$1INCREMENT value should have been returned in this case, causing a duplicate key error. (Bug \$187926, Bug \$126906787)
+ Fixed an issue which can lead to a failure while upgrading an Aurora MySQL version 1 (Compatible with MySQL 5.6) database cluster containing user-created table with certain table IDs. Assignment of these table IDs may result in conflicting data dictionary table IDs while upgrading from Aurora MySQL version 2 (Compatible with MySQL 5.7) to Aurora MySQL version 3 (Compatible with MySQL 8.0) (Bug \$133919635)

# Aurora MySQL database engine updates 2022-09-07 (version 3.02.1) (Deprecated)
<a name="AuroraMySQL.Updates.3021"></a><a name="3.02.1"></a><a name="3.02.1"></a>

 **Version:** 3.02.1 

 Aurora MySQL 3.02.1 is generally available. Aurora MySQL 3.02 versions are compatible with MySQL 8.0.23, Aurora MySQL 2.x versions are compatible with MySQL 5.7, and Aurora MySQL 1.x versions are compatible with MySQL 5.6. 

 For details of new features in Aurora MySQL version 3 and differences between Aurora MySQL version 3 and Aurora MySQL version 2 or community MySQL 8.0, see [ Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.Compare-v2-v3) in the *Amazon Aurora User Guide*. 

 Currently supported Aurora MySQL releases are 1.19.5, 1.19.6, 1.22.\$1, 1.23.\$1, 2.04.\$1, 2.07.\$1, 2.08.\$1, 2.09.\$1, 2.10.\$1, 3.01.\$1 and 3.02.\$1. 

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For the upgrade procedure itself, see [ Upgrading to Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-procedure) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3021.Improvements"></a>

Aurora MySQL version 3.02.1 is generally available and generally compatible with community MySQL 8.0.23.

**Fixed security issues and CVEs listed below:**

Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes below:
+ [CVE-2022-0778](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0778)

**Availability improvements:**
+ Fixed an issue which can cause connection failure and high latency when multiple MySQL binary log (binlog) replicas are attached to an Aurora writer node or when there are a large number of concurrent long running queries in conjunction with a surge in new connection requests. 
+  Fixed an issue that causes a database restart when advanced auditing for `CONNECT` events are turned on. 
+  Fixed an issue that can cause a database restart on Aurora MySQL read replica instances when internal temporary tables exhaust the allocated size in memory and mmap files set as a customer-configured or default value. 
+  Fixed an issue that can cause a read replica to repeatedly restart during concurrent DDL operations on stored procedures. 
+ Fast insert isn't enabled in this Aurora MySQL version, due to an issue that can cause inconsistencies when running queries such as `INSERT INTO`, `SELECT`, and `FROM`. For more information on the fast insert optimization, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance).

**General improvements:**
+ Added support for R6i instances.

**Additional Information:**
+ Aurora MySQL version 3.02.1 does not contain support for major version upgrades directly from Aurora MySQL version 2 (compatible with MySQL 5.7). To perform a major version upgrade to this version, first perform a major version upgrade to Aurora MySQL version 3.02.0, then perform an in-place minor version upgrade to Aurora MySQL version 3.02.1.

# Aurora MySQL database engine updates 2022-04-20 (version 3.02.0) (Deprecated)
<a name="AuroraMySQL.Updates.3020"></a><a name="3.02.0"></a><a name="3.02.0"></a>

 **Version:** 3.02.0 

 Aurora MySQL 3.02.0 is generally available. Aurora MySQL 3.02 versions are compatible with MySQL 8.0.23, Aurora MySQL 2.x versions are compatible with MySQL 5.7, and Aurora MySQL 1.x versions are compatible with MySQL 5.6. 

 For details of new features in Aurora MySQL version 3 and differences between Aurora MySQL version 3 and Aurora MySQL version 2 or community MySQL 8.0, see [ Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.Compare-v2-v3) in the *Amazon Aurora User Guide*. 

 Currently supported Aurora MySQL releases are 1.19.5, 1.19.6, 1.22.\$1, 1.23.\$1, 2.04.\$1, 2.07.\$1, 2.08.\$1, 2.09.\$1, 2.10.\$1, 3.01.\$1 and 3.02.\$1. 

 You can restore a snapshot from any currently supported Aurora MySQL version 2 cluster into Aurora MySQL 3.02.0. 

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For the upgrade procedure itself, see [ Upgrading to Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-procedure) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3020.Improvements"></a>

 Aurora MySQL version 3.02.0 is generally available and generally compatible with community MySQL 8.0.23. 

**Fixed security issues and CVEs listed below:**

Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes below:
+ [CVE-2021-22946](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22946)

 **New features:** 
+ Amazon Aurora Serverless v2 is generally available. For more information, see the [Amazon Aurora Serverless](https://aws.amazon.com/rds/aurora/serverless/) overview, [blog](https://aws.amazon.com/blogs/aws/amazon-aurora-serverless-v2-is-generally-available-instant-scaling-for-demanding-workloads/), and [Using Aurora Serverless v2](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.html) documentation. Get started today by creating an Aurora Serverless v2 database using only a few steps in the AWS Management Console.

**Availability improvements:**
+ Fixed an issue that can cause the server to potentially go into a restart loop and cause unavailability while deleting a record or dropping a table containing two or more variable-length columns (VARCHAR, VARBINARY, BLOB, and TEXT types). For more details about column types, see [innodb-row-format](https://dev.mysql.com/doc/refman/8.0/en/innodb-row-format.html).
+ Fixed an issue where existing connections timeout and new connections could not be established on a cluster with Binary Log turned on and has at least one Binary Log consumer attached that results in resource contention between the application and the consumer(s).
+ Freeable memory is indicated by the `FreeableMemory` CloudWatch metric. For more information, see [Amazon CloudWatch metrics for Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Monitoring.Metrics.html).
  + Fixed an issue that can cause a DB instance restart or a failover due to a decrease in freeable memory when binary log replication is enabled.
  + Fixed an issue that can cause a DB instance restart or a failover due to a decrease in freeable memory when setting session variables.
  + Fixed an issue that can cause a DB instance restart or a failover due to a decrease in freeable memory when the database process opens an existing file.
+ Fixed an issue which, in rare conditions, can cause a duplicate entry error when inserting new rows into a table containing an `AUTO_INCREMENT` column on a cluster restored from snapshot.
+ Fast insert isn't enabled in this Aurora MySQL version, due to an issue that can cause inconsistencies when running queries such as `INSERT INTO`, `SELECT`, and `FROM`. For more information on the fast insert optimization, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance).

**General improvements:**
+ Fixed an issue where the volume status was not shown when using the `SHOW VOLUME STATUS` command. For more information, see [AuroraMySQL.Managing.VolumeStatus](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.VolumeStatus.html).
+ Fixed an issue that caused calls to [mysql\$1rds\$1import\$1binlog\$1ssl\$1material](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/mysql_rds_import_binlog_ssl_material.html) to fail with [MySQL server ERROR 3512](https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html#error_er_sp_load_failed).
+ Fixed an issue where Aurora replica lag is incorrectly reported for deleted Aurora reader instances.

**Upgrades/Migration:**
+ Fixed an issue that can cause migration failures of MySQL 8.0.x databases to Aurora MySQL version 3 due to an issue in copying ibdata files and tablespaces to Aurora storage.
+ Fixed an issue which can cause upgrades of clusters from Aurora MySQL version 2 to Aurora MySQL version 3 to fail when database tables contained a large amount of data.
+ Fixed an issue that can cause failures when restoring clusters from Aurora MySQL version 2 to Aurora MySQL version 3 due to a failure in creating [serialized data dictionary information](https://dev.mysql.com/doc/refman/8.0/en/glossary.html#glos_serialized_dictionary_information) (SDI) for a table.
+ Fixed an issue that can cause upgrade failures from Aurora MySQL version 2 to Aurora MySQL version 3 due to schema inconsistency errors reported by upgrade prechecks for RDS system tables.
+ Fixed an issue that can cause failures when migrating or restoring from RDS for MySQL 8.0 or Aurora MySQL version 2 to Aurora MySQL version 3 databases due to invalid syntax in an RDS managed stored procedure.
+ Fixed an issue that can cause upgrade failures from Aurora MySQL 2 to Aurora MySQL 3 due to schema inconsistency errors reported by upgrade prechecks for the [general log](https://dev.mysql.com/doc/refman/5.7/en/query-log.html) and [slow log](https://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html) tables.

## Integration of MySQL community edition bug fixes
<a name="AuroraMySQL.Updates.3020.Patches"></a>

This release includes all community bug fixes up to and including 8.0.23, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+ Fixed the improper handling of temporary tables used for cursors within stored procedures that could result in unexpected server behavior, [mysqld-8-0-24-bug](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-24.html#mysqld-8-0-24-bug). (Bug \$132416811) 

# Aurora MySQL database engine updates 2022-04-15 (version 3.01.1) (Deprecated)
<a name="AuroraMySQL.Updates.3011"></a><a name="3011"></a><a name="3.01.1"></a>

 **Version:** 3.01.1 

 Aurora MySQL 3.01.1 is generally available. Aurora MySQL 3.01 versions are compatible with MySQL 8.0.23, Aurora MySQL 2.x versions are compatible with MySQL 5.7, and Aurora MySQL 1.x versions are compatible with MySQL 5.6. 

 For details of new features in Aurora MySQL version 3 and differences between Aurora MySQL version 3 and Aurora MySQL version 2 or community MySQL 8.0, see [ Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.Compare-v2-v3) in the *Amazon Aurora User Guide*. 

 Currently supported Aurora MySQL releases are 1.19.5, 1.19.6, 1.22.\$1, 1.23.\$1, 2.04.\$1, 2.07.\$1, 2.08.\$1, 2.09.\$1, 2.10.\$1, 3.01.\$1 and 3.02.\$1. 

 You can restore a snapshot from any currently supported Aurora MySQL version 2 cluster into Aurora MySQL 3.01.1. 

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For the upgrade procedure itself, see [ Upgrading to Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-procedure) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3011.Improvements"></a>

Aurora MySQL version 3.01.1 is generally available and generally compatible with community MySQL 8.0.23.

Aurora MySQL version 3.01.1 is recommended for upgrades and migrations to a MySQL 8.0 compatible Aurora database.

**Fixed security issues and CVEs listed below:**

Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes below:
+ [CVE-2021-36222](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36222)
+ [CVE-2021-22946](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22946)
+ [CVE-2021-22926](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22926)

**Availability improvements:**
+ Freeable memory is indicated by the `FreeableMemory` CloudWatch metric. For more information, see [Amazon CloudWatch metrics for Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Monitoring.Metrics.html). 
  + Fixed an issue that can cause a DB instance restart or a failover due to a decrease in freeable memory when binary log replication is enabled.
  + Fixed an issue that can cause a DB instance restart or a failover due to a decrease in freeable memory when setting session variables.
  + Fixed an issue that can cause a DB instance restart or a failover due to a decrease in freeable memory when the database process opens an existing file.
+ Fixed an issue which, in rare conditions, can cause a duplicate entry error when inserting new rows into a table containing an `AUTO_INCREMENT` column on a cluster restored from snapshot.
+ Fast insert isn't enabled in this Aurora MySQL version, due to an issue that can cause inconsistencies when running queries such as `INSERT INTO`, `SELECT`, and `FROM`. For more information on the fast insert optimization, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance).

**General improvements:**
+ Fixed an issue where the volume status was not shown when using the `SHOW VOLUME STATUS` command. For more information, see [AuroraMySQL.Managing.VolumeStatus](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.VolumeStatus.html).
+ Fixed an issue that caused calls to [mysql\$1rds\$1import\$1binlog\$1ssl\$1material](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/mysql_rds_import_binlog_ssl_material.html) to fail with [MySQL server ERROR 3512](https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html#error_er_sp_load_failed).
+ Fixed an issue where Aurora replica lag is incorrectly reported for deleted Aurora reader instances.

**Upgrades/Migration:**
+ Fixed an issue that can cause migration failures of MySQL 8.0.x databases to Aurora MySQL version 3 due to an issue in copying ibdata files and tablespaces to Aurora storage.
+ Fixed an issue which can cause upgrades of clusters from Aurora MySQL version 2 to Aurora MySQL version 3 to fail when database tables contained a large amount of data.
+ Fixed an issue that can cause failures when restoring clusters from Aurora MySQL version 2 to Aurora MySQL version 3 due to a failure in creating [serialized data dictionary information](https://dev.mysql.com/doc/refman/8.0/en/glossary.html#glos_serialized_dictionary_information) (SDI) for a table.
+ Fixed an issue that can cause upgrade failures from Aurora MySQL version 2 to Aurora MySQL version 3 due to schema inconsistency errors reported by upgrade prechecks for RDS system tables.
+ Fixed an issue that can cause failures when migrating or restoring from RDS for MySQL 8.0 or Aurora MySQL version 2 to Aurora MySQL version 3 databases due to invalid syntax in an RDS managed stored procedure.
+ Fixed an issue that can cause upgrade failures from Aurora MySQL 2 to Aurora MySQL 3 due to schema inconsistency errors reported by upgrade prechecks for the [general log](https://dev.mysql.com/doc/refman/5.7/en/query-log.html) and [slow log](https://dev.mysql.com/doc/refman/5.7/en/slow-query-log.html) tables.

## Integration of MySQL community edition bug fixes
<a name="AuroraMySQL.Updates.3011.Patches"></a>

This release includes all community bug fixes up to and including 8.0.23, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 3.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v3).
+ Fixed the improper handling of temporary tables used for cursors within stored procedures that could result in unexpected server behavior, [mysqld-8-0-24-bug](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-24.html#mysqld-8-0-24-bug). (Bug \$132416811) 

# Aurora MySQL database engine updates 2021-11-18 (version 3.01.0) (Deprecated)
<a name="AuroraMySQL.Updates.3010"></a><a name="3010"></a><a name="3.01.0"></a>

 **Version:** 3.01.0 

 Aurora MySQL 3.01.0 is generally available. Aurora MySQL 3.01 versions are compatible with MySQL 8.0.23, Aurora MySQL 2.x versions are compatible with MySQL 5.7, and Aurora MySQL 1.x versions are compatible with MySQL 5.6. 

 For details of new features in Aurora MySQL version 3 and differences between Aurora MySQL version 3 and Aurora MySQL version 2 or community MySQL 8.0, see [ Comparing Aurora MySQL version 2 and Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.Compare-v2-v3) in the *Amazon Aurora User Guide*. 

 Currently supported Aurora MySQL releases are 1.19.5, 1.19.6, 1.22.\$1, 1.23.\$1, 2.04.\$1, 2.07.\$1, 2.08.\$1, 2.09.\$1, 2.10.\$1, 3.01.\$1 and 3.02.\$1. 

 You can restore a snapshot from any currently supported Aurora MySQL version 2 cluster into Aurora MySQL 3.01.0. 

 For information on planning an upgrade to Aurora MySQL version 3, see [ Upgrade planning for Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-planning) in the *Amazon Aurora User Guide*. For the upgrade procedure itself, see [ Upgrading to Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-procedure) in the *Amazon Aurora User Guide*. For general information about Aurora MySQL upgrades, see [ Upgrading Amazon Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Upgrading.html) in the *Amazon Aurora User Guide*. 

For troubleshooting information, see [ Troubleshooting upgrade issues with Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.mysql80-upgrade-troubleshooting). 

 If you have any questions or concerns, AWS Support is available on the community forums and through [AWS Support](https://aws.amazon.com/support). For more information, see [ Maintaining an Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements
<a name="AuroraMySQL.Updates.3010.Improvements"></a>

Aurora MySQL version 3.01.0 is generally compatible with community MySQL 8.0.23. This version includes the security fixes for Common Vulnerabilities and Exposures (CVE) issues as of community MySQL 8.0.23.

Aurora MySQL version 3.01.0 contains all the Aurora-specific bug fixes through Aurora MySQL version 2.10.0.

For details of new features in Aurora MySQL version 3, see [ Features from community MySQL 8.0](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.8.0-features-community) and [ New parallel query optimizations](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.MySQL80.html#AuroraMySQL.8.0-features-pq) in the *Amazon Aurora User Guide*.

**Availability improvements:**
+ Fast insert isn't enabled in this Aurora MySQL version, due to an issue that can cause inconsistencies when running queries such as `INSERT INTO`, `SELECT`, and `FROM`. For more information on the fast insert optimization, see [Amazon Aurora MySQL performance enhancements](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.AuroraMySQL.Overview.html#Aurora.AuroraMySQL.Performance).