# Database engine updates for Amazon Aurora MySQL version 2
Aurora MySQL version 2

**Important**  
Aurora MySQL version 2 reached the end of standard support on October 31, 2024. For more information, see [Preparing for Amazon Aurora MySQL-Compatible Edition version 2 end of standard support](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.MySQL57.EOL.html).

The following are database engine updates for Amazon Aurora MySQL version 2.<a name="aurora_2x_updates"></a>
+ [Aurora MySQL database engine updates 2026-03-09 (version 2.12.6, compatible with MySQL 5.7.44) - RDS Extended Support version](AuroraMySQL.Updates.2126.md)
+ [Aurora MySQL database engine updates 2025-04-09 (version 2.12.5, compatible with MySQL 5.7.44) - RDS Extended Support version](AuroraMySQL.Updates.2125.md)
+ [Aurora MySQL database engine updates 2024-10-23 (version 2.12.4, compatible with MySQL 5.7.44) - RDS Extended Support version](AuroraMySQL.Updates.2124.md)
+ [Aurora MySQL database engine updates 2024-07-09 (version 2.12.3, compatible with MySQL 5.7.44) - RDS Extended Support version](AuroraMySQL.Updates.2123.md)
+ [Aurora MySQL database engine updates 2024-03-19 (version 2.12.2, compatible with MySQL 5.7.44) - RDS Extended Support version](AuroraMySQL.Updates.2122.md)
+ [Aurora MySQL database engine updates 2023-12-28 (version 2.12.1, compatible with MySQL 5.7.40) - RDS Extended Support version](AuroraMySQL.Updates.2121.md)
+ [Aurora MySQL database engine updates 2023-10-25 (version 2.12.0.1, compatible with MySQL 5.7.40) - RDS Extended Support version (Beta)](AuroraMySQL.Updates.21201.md)
+ [Aurora MySQL database engine updates 2023-07-25 (version 2.12.0, compatible with MySQL 5.7.40) - RDS Extended Support version](AuroraMySQL.Updates.2120.md)
+ [Aurora MySQL database engine updates 2024-07-19 (version 2.11.6, compatible with MySQL 5.7.12) - RDS Extended Support version](AuroraMySQL.Updates.2116.md)
+ [Aurora MySQL database engine updates 2024-03-26 (version 2.11.5, compatible with MySQL 5.7.12) - RDS Extended Support version (Default)](AuroraMySQL.Updates.2115.md)
+ [Aurora MySQL database engine updates 2023-10-17 (version 2.11.4, compatible with MySQL 5.7.12) - RDS Extended Support version](AuroraMySQL.Updates.2114.md)
+ [Aurora MySQL database engine updates 2023-06-09 (version 2.11.3, compatible with MySQL 5.7.12) - RDS Extended Support version](AuroraMySQL.Updates.2113.md)
+ [Aurora MySQL database engine updates 2023-03-24 (version 2.11.2, compatible with MySQL 5.7.12) - RDS Extended Support version](AuroraMySQL.Updates.2112.md)
+ [Aurora MySQL database engine updates 2023-02-14 (version 2.11.1, compatible with MySQL 5.7.12) - RDS Extended Support version](AuroraMySQL.Updates.2111.md)
+ [Aurora MySQL database engine updates 2022-10-25 (version 2.11.0, compatible with MySQL 5.7.12) - RDS Extended Support version](AuroraMySQL.Updates.2110.md)
+ [Aurora MySQL database engine updates 2022-11-01 (version 2.10.3) (Deprecated)](AuroraMySQL.Updates.2103.md)
+ [Aurora MySQL database engine updates 2022-01-26 (version 2.10.2) (Deprecated)](AuroraMySQL.Updates.2102.md)
+ [Aurora MySQL database engine updates 2021-10-21 (version 2.10.1) (Deprecated)](AuroraMySQL.Updates.2101.md)
+ [Aurora MySQL database engine updates 2021-05-25 (version 2.10.0) (Deprecated)](AuroraMySQL.Updates.2100.md)
+ [Aurora MySQL database engine updates 2021-11-12 (version 2.09.3) (Deprecated)](AuroraMySQL.Updates.2093.md)
+ [Aurora MySQL database engine updates 2021-02-26 (version 2.09.2) (Deprecated)](AuroraMySQL.Updates.2092.md)
+ [Aurora MySQL database engine updates 2020-12-11 (version 2.09.1) (Deprecated)](AuroraMySQL.Updates.2091.md)
+ [Aurora MySQL database engine updates 2020-09-17 (version 2.09.0) (Deprecated)](AuroraMySQL.Updates.2090.md)
+ [Aurora MySQL database engine updates 2022-01-06 (version 2.08.4) (Deprecated)](AuroraMySQL.Updates.2084.md)
+ [Aurora MySQL database engine updates 2020-11-12 (version 2.08.3) (Deprecated)](AuroraMySQL.Updates.2083.md)
+ [Aurora MySQL database engine updates 2020-08-28 (version 2.08.2) (Deprecated)](AuroraMySQL.Updates.2082.md)
+ [Aurora MySQL database engine updates 2020-06-18 (version 2.08.1) (Deprecated)](AuroraMySQL.Updates.2081.md)
+ [Aurora MySQL database engine updates 2020-06-02 (version 2.08.0) (Deprecated)](AuroraMySQL.Updates.2080.md)
+ [Aurora MySQL database engine updates 2023-08-15 (version 2.07.10) (Deprecated)](AuroraMySQL.Updates.20710.md)
+ [Aurora MySQL database engine updates 2023-05-04 (version 2.07.9) (Deprecated)](AuroraMySQL.Updates.2079.md)
+ [Aurora MySQL database engine updates 2022-06-16 (version 2.07.8) (Deprecated)](AuroraMySQL.Updates.2078.md)
+ [Aurora MySQL database engine updates 2021-11-24 (version 2.07.7) (Deprecated)](AuroraMySQL.Updates.2077.md)
+ [Aurora MySQL database engine updates 2021-09-02 (version 2.07.6) (Deprecated)](AuroraMySQL.Updates.2076.md)
+ [Aurora MySQL database engine updates 2021-07-06 (version 2.07.5) (Deprecated)](AuroraMySQL.Updates.2075.md)
+ [Aurora MySQL database engine updates 2021-03-04 (version 2.07.4) (Deprecated)](AuroraMySQL.Updates.2074.md)
+ [Aurora MySQL database engine updates 2020-11-10 (version 2.07.3) (Deprecated)](AuroraMySQL.Updates.2073.md)
+ [Aurora MySQL database engine updates 2020-04-17 (version 2.07.2) (Deprecated)](AuroraMySQL.Updates.2072.md)
+ [Aurora MySQL database engine updates 2019-12-23 (version 2.07.1) (Deprecated)](AuroraMySQL.Updates.2071.md)
+ [Aurora MySQL database engine updates 2019-11-25 (version 2.07.0) (Deprecated)](AuroraMySQL.Updates.2070.md)
+ [Aurora MySQL database engine updates 2019-11-22 (version 2.06.0) (Deprecated)](AuroraMySQL.Updates.2060.md)
+ [Aurora MySQL database engine updates 2019-11-11 (version 2.05.0) (Deprecated)](AuroraMySQL.Updates.2050.md)
+ [Aurora MySQL database engine updates 2020-08-14 (version 2.04.9) (Deprecated)](AuroraMySQL.Updates.2049.md)
+ [Aurora MySQL database engine updates 2019-11-20 (version 2.04.8) (Deprecated)](AuroraMySQL.Updates.2048.md)
+ [Aurora MySQL database engine updates 2019-11-14 (version 2.04.7) (Deprecated)](AuroraMySQL.Updates.2047.md)
+ [Aurora MySQL database engine updates 2019-09-19 (version 2.04.6) (Deprecated)](AuroraMySQL.Updates.2046.md)
+ [Aurora MySQL database engine updates 2019-07-08 (version 2.04.5) (Deprecated)](AuroraMySQL.Updates.2045.md)
+ [Aurora MySQL database engine updates 2019-05-29 (version 2.04.4) (Deprecated)](AuroraMySQL.Updates.2044.md)
+ [Aurora MySQL database engine updates 2019-05-09 (version 2.04.3) (Deprecated)](AuroraMySQL.Updates.2043.md)
+ [Aurora MySQL database engine updates 2019-05-02 (version 2.04.2) (Deprecated)](AuroraMySQL.Updates.2042.md)
+ [Aurora MySQL database engine updates 2019-03-25 (version 2.04.1) (Deprecated)](AuroraMySQL.Updates.2041.md)
+ [Aurora MySQL database engine updates 2019-03-25 (version 2.04.0) (Deprecated)](AuroraMySQL.Updates.204.md)
+ [Aurora MySQL database engine updates 2019-02-07 (version 2.03.4) (Deprecated)](AuroraMySQL.Updates.2034.md)
+ [Aurora MySQL database engine updates 2019-01-18 (version 2.03.3) (Deprecated)](AuroraMySQL.Updates.2033.md)
+ [Aurora MySQL database engine updates 2019-01-09 (version 2.03.2) (Deprecated)](AuroraMySQL.Updates.2032.md)
+ [Aurora MySQL database engine updates 2018-10-24 (version 2.03.1) (Deprecated)](AuroraMySQL.Updates.2031.md)
+ [Aurora MySQL database engine updates 2018-10-11 (version 2.03) (Deprecated)](AuroraMySQL.Updates.203.md)
+ [Aurora MySQL database engine updates 2018-10-08 (version 2.02.5) (Deprecated)](AuroraMySQL.Updates.2025.md)
+ [Aurora MySQL database engine updates 2018-09-21 (version 2.02.4) (Deprecated)](AuroraMySQL.Updates.2024.md)
+ [Aurora MySQL database engine updates 2018-08-23 (version 2.02.3) (Deprecated)](AuroraMySQL.Updates.2023.md)
+ [Aurora MySQL database engine updates 2018-06-04 (version 2.02.2) (Deprecated)](AuroraMySQL.Updates.2022.md)
+ [Aurora MySQL database engine updates 2018-05-03 (version 2.02) (Deprecated)](AuroraMySQL.Updates.202.md)
+ [Aurora MySQL database engine updates 2018-03-13 (version 2.01.1) (Deprecated)](AuroraMySQL.Updates.2011.md)
+ [Aurora MySQL database engine updates 2018-02-06 (version 2.01) (Deprecated)](AuroraMySQL.Updates.20180206.md)

# Aurora MySQL database engine updates 2026-03-09 (version 2.12.6, compatible with MySQL 5.7.44) - RDS Extended Support version
Aurora MySQL updates: 2026-03-09 (version 2.12.6, compatible with MySQL 5.7.44) - RDS Extended Support versionAurora MySQL version 2.12.6, compatible with MySQL 5.7.44

 Aurora MySQL version 2.12.6 is available. This version is compatible with MySQL 5.7.44. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html). <a name="2126"></a><a name="2.12.6"></a>

 **Version:** 2.12.6 

 Aurora MySQL 2.12.6 is generally available. Aurora MySQL 2.12 versions are compatible up to MySQL 5.7.44. For more information on community changes, see [Changes in MySQL 5.7.44 (2022-10-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html). 

 Currently supported Aurora MySQL releases are 2.11.\$1, 2.12.\$1, 3.04.\$1, 3.08.\$1, 3.09.\$1, 3.10.\$1, 3.11.\$1, and 3.12.\$1. 

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

 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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


 **Security fixes:** 
+  Fixed an issue which can cause some SQL statements to not get logged in the audit log. 

 **Medium CVEs:** 
+  [CVE-2025-53054](https://www.cve.org/CVERecord?id=CVE-2025-53054) 
+  [CVE-2025-53053](https://www.cve.org/CVERecord?id=CVE-2025-53053) 
+  [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-53062](https://www.cve.org/CVERecord?id=CVE-2025-53062) 
+  [CVE-2025-53069](https://www.cve.org/CVERecord?id=CVE-2025-53069) 
+  [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-50082](https://www.cve.org/CVERecord?id=CVE-2025-50082) 
+  [CVE-2025-50085](https://www.cve.org/CVERecord?id=CVE-2025-50085) 
+  [CVE-2025-53023](https://www.cve.org/CVERecord?id=CVE-2025-53023) 
+  [CVE-2025-50087](https://www.cve.org/CVERecord?id=CVE-2025-50087) 
+  [CVE-2025-50099](https://www.cve.org/CVERecord?id=CVE-2025-50099) 
+  [CVE-2025-50079](https://www.cve.org/CVERecord?id=CVE-2025-50079) 
+  [CVE-2025-50092](https://www.cve.org/CVERecord?id=CVE-2025-50092) 
+  [CVE-2025-50102](https://www.cve.org/CVERecord?id=CVE-2025-50102) 
+  [CVE-2025-50083](https://www.cve.org/CVERecord?id=CVE-2025-50083) 
+  [CVE-2025-50096](https://www.cve.org/CVERecord?id=CVE-2025-50096) 
+  [CVE-2025-50091](https://www.cve.org/CVERecord?id=CVE-2025-50091) 
+  [CVE-2025-50084](https://www.cve.org/CVERecord?id=CVE-2025-50084) 
+  [CVE-2025-50101](https://www.cve.org/CVERecord?id=CVE-2025-50101) 
+  [CVE-2025-50077](https://www.cve.org/CVERecord?id=CVE-2025-50077) 
+  [CVE-2025-50088](https://www.cve.org/CVERecord?id=CVE-2025-50088) 
+  [CVE-2025-50080](https://www.cve.org/CVERecord?id=CVE-2025-50080) 
+  [CVE-2025-50097](https://www.cve.org/CVERecord?id=CVE-2025-50097) 
+  [CVE-2025-50094](https://www.cve.org/CVERecord?id=CVE-2025-50094) 
+  [CVE-2025-50093](https://www.cve.org/CVERecord?id=CVE-2025-50093) 
+  [CVE-2025-50086](https://www.cve.org/CVERecord?id=CVE-2025-50086) 
+  [CVE-2025-50078](https://www.cve.org/CVERecord?id=CVE-2025-50078) 
+  [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-50104](https://www.cve.org/CVERecord?id=CVE-2025-50104) 
+  [CVE-2025-50098](https://www.cve.org/CVERecord?id=CVE-2025-50098) 
+  [CVE-2025-50100](https://www.cve.org/CVERecord?id=CVE-2025-50100) 
+  [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) 

# Aurora MySQL database engine updates 2025-04-09 (version 2.12.5, compatible with MySQL 5.7.44) - RDS Extended Support version
Aurora MySQL updates: 2025-04-09 (version 2.12.5, compatible with MySQL 5.7.44) - RDS Extended Support versionAurora MySQL version 2.12.5, compatible with MySQL 5.7.44

 Aurora MySQL version 2.12.5 is available. This version is compatible with MySQL 5.7.44. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html). <a name="2125"></a><a name="2.12.5"></a>

 **Version:** 2.12.5

Aurora MySQL 2.12.5 is generally available. Aurora MySQL 2.12 versions are compatible up to MySQL 5.7.44. For more information on community changes, see [Changes in MySQL 5.7.44 (2022-10-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html). 

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 upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.12.5. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.12.5.

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


 **Fixed security issues and CVEs:** 

This release includes all community CVE fixes up to and including MySQL 5.7.44. The following CVE fixes are included:
+  [CVE-2025-21543](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21543) 
+  [CVE-2025-21500](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21500) 
+  [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-21540](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21540) 
+  [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-21520](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21520) 
+  [CVE-2025-21501](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21501) 
+  [CVE-2024-37371](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-37371) 
+  [CVE-2024-11053](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-11053) 
+  [CVE-2024-21201](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21201) 
+  [CVE-2024-21241](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-21241) 
+  [CVE-2024-21230](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21230) 
+  [CVE-2023-44487](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-44487) 

 **Availability improvements:** 
+ Fixed an issue on the replica where a network interruption may not correctly re-establish connection with the writer.

# Aurora MySQL database engine updates 2024-10-23 (version 2.12.4, compatible with MySQL 5.7.44) - RDS Extended Support version
Aurora MySQL updates: 2024-10-23 (version 2.12.4, compatible with MySQL 5.7.44) - RDS Extended Support versionAurora MySQL version 2.12.4, compatible with MySQL 5.7.44

 Aurora MySQL version 2.12.4 is available. This version is compatible with MySQL 5.7.44. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html).<a name="2124"></a><a name="2.12.4"></a>

**Version:** 2.12.4

Aurora MySQL 2.12.4 is generally available. Aurora MySQL 2.12 versions are compatible up to MySQL 5.7.44. For more information on community changes, see [Changes in MySQL 5.7.44 (2022-10-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html).

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

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

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


**Fixed security issues and CVEs:**

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

## Integration of MySQL Community Edition bug fixes


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

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Scan batching

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ The `CREATE TABLESPACE` SQL statement
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ X Protocol

# Aurora MySQL database engine updates 2024-07-09 (version 2.12.3, compatible with MySQL 5.7.44) - RDS Extended Support version
Aurora MySQL updates: 2024-07-09 (version 2.12.3, compatible with MySQL 5.7.44) - RDS Extended Support versionAurora MySQL version 2.12.3, compatible with MySQL 5.7.44

 Aurora MySQL version 2.12.3 is available. This version is compatible with MySQL 5.7.44. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html).<a name="2123"></a><a name="2.12.3"></a>

**Version:** 2.12.3

Aurora MySQL 2.12.3 is generally available. Aurora MySQL 2.12 versions are compatible up to MySQL 5.7.44. For more information on community changes, see [Changes in MySQL 5.7.44 (2022-10-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html).

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 upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.12.3. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.12.3.

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


**Fixed security issues and CVEs:**
+ Fixed a security issue for MySQL stored procedures.

This release includes all community CVE fixes up to and including MySQL 5.7.44. The following CVE fixes are included:
+ [CVE-2023-21912](https://nvd.nist.gov/vuln/detail/CVE-2023-21912)
+ [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-20993](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-20993)
+ [CVE-2024-20998](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-20998)
+ [CVE-2024-21008](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21008)
+ [CVE-2024-21009](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21009)
+ [CVE-2024-21013](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21013)
+ [CVE-2024-21047](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21047)
+ [CVE-2024-21054](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21054)
+ [CVE-2024-21055](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21055)
+ [CVE-2024-21057](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21057)
+ [CVE-2024-21062](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21062)
+ [CVE-2024-21069](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21069)
+ [CVE-2024-21096](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21096)
+ [CVE-2024-21097](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21097)

**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 database server to restart due to the concurrent access of connection resources during seamless scaling, zero downtime restart (ZDR), and zero downtime patching (ZDP).
+ Fixed an issue that can cause a reader DB instance to restart when freeing memory used for log application.
+ Fixed an issue in a background process that caused prolonged or failed running of queries while the background operation drops temporary indexes.
+ Fixed an issue with startup routines that can cause writer DB instances to restart due to metadata inconsistency.
+ Added an indicator for transaction recovery progress. This avoids potential unavailability, in rare situations, when transaction recovery takes a long time to complete.
+ 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 where a low `thread_stack` parameter value caused the database to restart repeatedly. The minimum allowed `thread_stack` value has been increased from 131,072 to 136,192 to ensure successful booting and prevent startup issues.
+ Fixed an issue that causes a reader DB instance to restart when running a parallel query.
+ 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, in rare cases, can cause a DB instance to restart when a read-only transaction obtains shared locks.
+ 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.

**General improvements:**
+ 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.
+ Fixed an issue that can lead to incorrect query results when ZDR incorrectly restores session variables set as hints in queries.
+ Fixed an issue in parallel query that causes an incomplete result set to be returned when using the built-in `LPAD` and `RPAD` string functions.
+ Fixed an issue that causes missing foreign key indexes on reader DB instances when an `ALTER TABLE RENAME COLUMN` statement is run on the writer DB instance against a table with a foreign key.
+ Fixed an issue that can cause failure in completing the process of disabling write forwarding.
+ Fixed an issue during Aurora Serverless v1 scaling that causes the DB instance to restart due to incorrect access to an internal data structure while finding a scaling point.
+ 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.
+ The request timeout for [Aurora machine learning](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-ml.html) operations to Amazon SageMaker AI has been increased from 3 to 30 seconds. This helps resolve an issue where customers might see an increased number of retries or failures for requests to Amazon SageMaker AI from Aurora machine learning when using larger batch sizes.
+ 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.

## Integration of MySQL Community Edition bug fixes


This release includes all community bug fixes up to and including 5.7.44. For more information, see [MySQL bugs fixed by Aurora MySQL 2.x database engine updates](AuroraMySQL.Updates.MySQLBugs.md#AuroraMySQL.Updates.MySQLBugs.v2).
+ Fixed an issue where temporary tables bound to triggers while running statements could cause an unexpected DB engine restart.
+ Fixed a defect that can cause the server to exit when single-table `UPDATE` and `DELETE` statements using indexed expressions are run as prepared statements. ([Bug \$129257254](https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-17.html))

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Scan batching

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ The `CREATE TABLESPACE` SQL statement
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ X Protocol

# Aurora MySQL database engine updates 2024-03-19 (version 2.12.2, compatible with MySQL 5.7.44) - RDS Extended Support version
Aurora MySQL updates: 2024-03-19 (version 2.12.2, compatible with MySQL 5.7.44) - RDS Extended Support versionAurora MySQL version 2.12.2, compatible with MySQL 5.7.44

Aurora MySQL version 2.12.2 is available. This version is compatible with MySQL 5.7.44. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html).<a name="2122"></a><a name="2.12.2"></a>

**Version:** 2.12.2

Aurora MySQL 2.12.2 is generally available. Aurora MySQL 2.12 versions are compatible up to MySQL 5.7.44. For more information on community changes, see [Changes in MySQL 5.7.44 (2022-10-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-44.html).

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

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

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


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

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

Security issues:
+ Added a fix that ensures binary log replicas default to using SSL/TLS if the source supports encrypted connections, irrespective of the `MASTER_SSL` setting.

**Availability improvements:**
+ Fixed an issue that can prevent a read replica instance from launching successfully if there is a high workload on the writer instance.
+ Fixed an issue which can cause an Aurora MySQL database writer instance to failover 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 database instance and the underlying storage following a software update of the Aurora storage instance.
+ Fixed an issue which, in rare conditions, can cause the reader instances to restart.
+ Fixed an issue in which a privileged user can modify the [resource limits](https://dev.mysql.com/doc/refman/5.7/en/user-resources.html) associated with the user, [rdsadmin](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Security.html). When set incorrectly, these resource limits can impede the RDS monitoring agent's ability to monitor the health of the database instance leading to database unavailability.

**Upgrades and migrations:**
+ Fixed an issue that occurred when attempting to start the binary log replication for Aurora MySQL clusters that had migrated from Amazon RDS MySQL 5.7 and that contained unsupported stored procedures.
+ Disabled the database event scheduler during a major version upgrade to Aurora MySQL version 3. This update helps avoid any changes to the database by the event execution while the major version upgrade is in progress.

## Integration of MySQL Community Edition bug fixes


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

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Scan batching

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ The `CREATE TABLESPACE` SQL statement
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ X Protocol

# Aurora MySQL database engine updates 2023-12-28 (version 2.12.1, compatible with MySQL 5.7.40) - RDS Extended Support version
Aurora MySQL updates: 2023-12-28 (version 2.12.1, compatible with MySQL 5.7.40) - RDS Extended Support versionAurora MySQL version 2.12.1, compatible with MySQL 5.7.40

Aurora MySQL version 2.12.1 is available. This version is compatible with MySQL 5.7.40. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html).<a name="2121"></a><a name="2.12.1"></a>

**Version:** 2.12.1

Aurora MySQL 2.12.1 is generally available. Aurora MySQL 2.12 versions are compatible up to MySQL 5.7.40. For more information on community changes, see [Changes in MySQL 5.7.40 (2022-10-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-40.html).

Currently supported Aurora MySQL releases are 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 2.\$1 database cluster to Aurora MySQL 2.12.1. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.12.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*.

**Note**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


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

This release includes all community CVEs fixes up to and including MySQL 5.7.44.

Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes are below:
+ [CVE-2023-38546](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38546)
+ [CVE-2023-38545](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38545)
+ [CVE-2023-22053](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22053)
+ [CVE-2023-22028](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22028)
+ [CVE-2023-22026](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22026)
+ [CVE-2023-22015](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22015)
+ [CVE-2022-24407](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24407)
+ [CVE-2020-11105](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11105)
+ [CVE-2020-11104](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11104)
+ Fixed processing of single character tokens by a Full-Text Search (FTS) parser plugin (Bug \$135432973)
+ Fixed an issue where events that were reported while processing the audit log rotations might not be written to the audit log

**New features:**
+ Added support for multi-threaded binary log (binlog) replication, where the SQL thread on the binlog replica would apply binary log events in parallel when possible. Learn more about the configuration options to help fine-tune your multithreaded replication in the [Aurora User Guide](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.MySQL.html).

**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 that can lead to high CPU utilization and client application timeouts.
+ 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 in the lock manager that could cause a restart or failover, when handling two-phase commits with the isolation level set to `READ_COMMITED` or `READ_UNCOMMITED` and either XA transactions are used or binary log (binlog) is enabled.
+ 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 that may cause the database instance to restart when the number of database connections approaches the value set by the `max_connections` parameter.
+ Fixed an issue which can cause an Aurora reader instance to restart when executing Data Manipulation Language (DML) queries on a table containing a full-text index.
+ 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 a parallel query to fail due to transient network issues while reading data from the Aurora cluster volume.
+ Fixed an issue related to audit log file management which can cause log files to be inaccessible for download or rotation, and in some cases increase CPU utilization.
+ Fixed an issue where small read replica instances may experience increased replication lag after upgrading from versions below 2.11.\$1
+ Fixed an issue that can cause excessive log messages when consulting the [`procs_priv` grant table](https://dev.mysql.com/doc/refman/8.0/en/grant-tables.html#grant-tables-procs-priv) for verification of requests that involve stored routines.
+ Fixed a memory management issue which can cause the database instance to use excessive memory while executing queries using the hash join optimization.
+ Fixed an issue which can produce an incorrect value of the variable `Threads_running` in the `information_schema` and `performance_schema` global status tables when using write forwarding.
+ Fixed an issue that caused a restart of the database when executing `SELECT` statements with partitioned tables (created in a version of MySQL supporting the old `ha_partition` partition handler) and parallel query is chosen by the query planner.
+ Fixed an issue which can prevent new client connections from being established to the database when write forwarding is enabled.
+ Reduced binary log (binlog) replication lag when an Aurora MySQL binlog replica is executing `QUERY` events written to the source's binlog file without a default database defined by the `USE` command.
+ Fixed an issue which can cause the `CommitLatency` CloudWatch metric to be incorrectly reported when the `innodb_flush_log_at_trx_commit` parameter is not set to 1.
+ Fixed an issue which can cause database connections to be closed before being established. This issue is more likely to affect database instances which open and close connections at a high rate.
+ Fixed an issue which can cause a database restart when connected binary log (binlog) consumers are using duplicate binlog replication server IDs.
+ 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.

## Integration of MySQL Community Edition bug fixes


This release includes all community bug fixes up to and including 5.7.40 in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 2.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v2).
+ Fixed an issue which can cause existing and new remote connections to stall when run concurrently with `SHOW PROCESSLIST` statement (Community Bug \$134857411)
+ Replication: Some binary log events were not always handled correctly (Bug \$134617506)

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Scan batching

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ The `CREATE TABLESPACE` SQL statement
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ X Protocol

# Aurora MySQL database engine updates 2023-10-25 (version 2.12.0.1, compatible with MySQL 5.7.40) - RDS Extended Support version (Beta)
Aurora MySQL updates: 2023-10-25 (version 2.12.0.1, compatible with MySQL 5.7.40) - RDS Extended Support version (Beta)Aurora MySQL version 2.12.0.1, compatible with MySQL 5.7.40, Beta

Aurora MySQL version 2.12.0.1 Beta is available. This version is compatible with MySQL 5.7.40. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html).<a name="21201"></a><a name="2.12.0.1"></a>

**Version:** 2.12.0.1

Aurora MySQL 2.12.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, 2.12.1. Aurora MySQL 2.12 versions are compatible with MySQL 5.7.40.

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

You can upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.12.0.1. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.12.0.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


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

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

**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).

# Aurora MySQL database engine updates 2023-07-25 (version 2.12.0, compatible with MySQL 5.7.40) - RDS Extended Support version
Aurora MySQL updates: 2023-07-25 (version 2.12.0, compatible with MySQL 5.7.40) - RDS Extended Support versionAurora MySQL version 2.12.0, compatible with MySQL 5.7.40

Aurora MySQL version 2.12.0 is available. This version is compatible with MySQL 5.7.40. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html).<a name="2120"></a><a name="2.12.0"></a>

**Version:** 2.12.0

Aurora MySQL 2.12.0 is generally available. Aurora MySQL 2.12 versions are compatible up to MySQL 5.7.40. For more information on community changes, see [Changes in MySQL 5.7.40 (2022-10-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-40.html).

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

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

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


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

This release includes all community CVEs fixes up to and including MySQL 5.7.40.
+ Default SSL ciphers used by Aurora MySQL have been updated to exclude the less secure DES-CBC3-SHA values from the [SSL\$1CIPHER](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_ssl_cipher) database parameter. If you encounter SSL connection issues due to the removal of the DES-CBC3-SHA cipher, please use an applicable secure cipher from the following list, [Configuring cipher suites for connections to Aurora MySQL DB clusters](https://docs.aws.amazon.com//AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Security.html#AuroraMySQL.Security.SSL.ConfiguringCipherSuites). More information on MySQL client [Connection Cipher Configuration](https://dev.mysql.com/doc/refman/5.7/en/encrypted-connection-protocols-ciphers.html#encrypted-connection-cipher-configuration) can be found in the MySQL documentation. 
+ [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-21840](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21840)
+ [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-32221](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-32221)
+ [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-2021-2169](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2169)

**Availability improvements:**
+ Fixed an issue in the database activity streams event encryption which may cause database restarts
+ Fixed two issues which can cause a database restart to fail if it occurred while executing a Data Definition Language (DDL) query
+ Fixed an issue where connection surges can cause increased query latency or a database instance restart
+ Fixed an issue which, in rare cases, can cause an Aurora replica to restart during 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 where connection surges could cause the connection establishment process to take longer to complete or to fail with timeout errors
+ Fixed an issue where the Advanced Auditing log rotation may reduce the freeable memory, which could lead to the database instance restarting
+ 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 that can cause the writer instance to restart while executing the `OPTIMIZE TABLE` query on a table with a Full Text Search (FTS) index
+ Fixed an issue which can cause the writer instance in an Aurora global database primary AWS Region to restart when a `SELECT FOR UPDATE` query is executed using global write forwarding from an Aurora global database secondary Region
+ Fixed an issue which can cause an Aurora global database secondary AWS 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
+ 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:**
+ Introduced file management performance optimizations on binlog replicas to help reduce contention when writing to relay log files
+ Fixed an issue that can cause the `buffer_pool_read_requests` counter to be reported incorrectly in the `information_schema` metrics
+ Fixed an issue that can cause the local storage to fill up when performing `LOAD FROM S3` or `SELECT INTO S3` operations. The issue can also lead to higher CPU utilization, database restarts due to low memory, and increased latency for these queries.
+ Fixed an issue where DB 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 the SSL server status variables weren't being populated
+ Fixed an issue where the Data Manipulation Language (DML) statements executing duplicate writes could lead to excessive error logging and increased query latencies
+ Upgraded the time zone definitions to the IANA 2023c version
+ Added support for enabling and disabling session-level binary logging. See [Stored Procedures - Replicating](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html#mysql_rds_enable_session_binlog) in the Amazon Aurora User Guide
+ Added support for setting the session-level binary log format. See [Stored Procedures - Replicating](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html#mysql_rds_set_session_binlog_format) in the Amazon Aurora User Guide
+ Fixed an issue where setting the `aurora_disable_hash_join` parameter to `1` or `ON` might not prevent the optimizer from using a hash join
+ 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, in rare cases, can cause an Amazon Aurora reader instance to restart when accessing a table which has large update or Data Definition Language (DDL) operations running concurrently on the writer instance
+ Fixed an issue that can cause the `buffer_pool_read_requests` counter to be reported incorrectly in the `information_schema` metrics
+ Fixed an issue that can cause a binlog replica to restart if the system variable [server uuid](https://dev.mysql.com/doc/refman/5.7/en/replication-options.html#sysvar_server_uuid) of the source is missing or has an invalid value
+ 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
+ Fixed an issue wherein the `AuroraGlobalDBRPOLag` CloudWatch metrics always displayed zero regardless of the user workload

 **Upgrades and migrations:** 
+ To perform a minor version upgrade for an Aurora global database from Aurora MySQL version 2.07 or 2.11 to Aurora MySQL version 2.12 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).

## Integration of MySQL Community Edition bug fixes


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

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Scan batching.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ The `CREATE TABLESPACE` SQL statement
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ X Protocol

# Aurora MySQL database engine updates 2024-07-19 (version 2.11.6, compatible with MySQL 5.7.12) - RDS Extended Support version
Aurora MySQL updates: 2024-07-19 (version 2.11.6, compatible with MySQL 5.7.12) - RDS Extended Support versionAurora MySQL version 2.11.6, compatible with MySQL 5.7.12

Aurora MySQL version 2.11.6 is available. This version is compatible with MySQL 5.7.12. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html).<a name="2116"></a><a name="2.11.6"></a>

**Version:** 2.11.6

Aurora MySQL 2.11.6 is generally available. Aurora MySQL 2.11 versions are compatible with MySQL 5.7.12. For more information on community changes, see [Changes in MySQL 5.7.12 (2016-04-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html).

The currently supported 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, 3.05.\$1, 3.06.\$1, and 3.07.\$1.

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

If you upgrade an Aurora MySQL global database to version 2.11.\$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). 

Immediately after an in-place engine version upgrade to Aurora MySQL 2.11.\$1 is performed, an operating system upgrade is applied automatically to all affected instances on the db.r4, db.r5, db.t2, and db.t3 DB instance classes, if the instances are running an old operating system version. In a Multi-AZ DB cluster, all of the reader instances apply the operating system upgrade first. When the operating system upgrade on the first reader instance is finished, a failover occurs and the previous writer instance is upgraded.

**Note**  
The operating system upgrade isn't applied automatically to Aurora global databases during major version upgrades.

**Note**  
For information on how to upgrade your Aurora MySQL database cluster, see [Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.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 Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements


**Fixed security issues and CVEs:**
+ Fixed a security issue in MySQL stored procedures.

This release includes all community CVE fixes up to and including MySQL 5.7.12. The following CVE fixes are included in this release:
+ [CVE-2023-21912](https://nvd.nist.gov/vuln/detail/CVE-2023-21912)
+ [CVE-2023-38545](https://nvd.nist.gov/vuln/detail/CVE-2023-38545)
+ [CVE-2023-39975](https://nvd.nist.gov/vuln/detail/CVE-2023-39975)
+ [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-20963](https://nvd.nist.gov/vuln/detail/CVE-2024-20963)
+ [CVE-2024-20993](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-20993)
+ [CVE-2024-20998](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-20998)
+ [CVE-2024-21008](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21008)
+ [CVE-2024-21009](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21009)
+ [CVE-2024-21013](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21013)
+ [CVE-2024-21047](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21047)
+ [CVE-2024-21054](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21054)
+ [CVE-2024-21055](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21055)
+ [CVE-2024-21057](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21057)
+ [CVE-2024-21062](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21062)
+ [CVE-2024-21069](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21069)
+ [CVE-2024-21096](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21096)
+ [CVE-2024-21097](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21097)

**Availability improvements:**
+ Fixed an issue that can cause a database server to restart due to the concurrent access of connection resources during seamless scaling, zero-downtime restart (ZDR), and zero-downtime patching (ZDP).
+ Fixed an issue that can cause a reader DB instance to restart when freeing memory used for log application.
+ Fixed an issue that causes a reader DB instance to restart when running a parallel query.
+ 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.

**General improvements:**
+ 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.
+ Fixed an issue that can lead to incorrect query results when ZDR incorrectly restores session variables set as hints in queries.
+ Fixed an issue during Aurora Serverless v1 scaling that causes the DB instance to restart due to incorrect access to an internal data structure while finding a scaling point.
+ 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.

## Integration of MySQL Community Edition bug fixes


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

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2024-03-26 (version 2.11.5, compatible with MySQL 5.7.12) - RDS Extended Support version (Default)
Aurora MySQL updates: 2024-03-26 (version 2.11.5, compatible with MySQL 5.7.12) - RDS Extended Support version (Default)Aurora MySQL version 2.11.5, compatible with MySQL 5.7.12

Aurora MySQL version 2.11.5 is available. This version is compatible with MySQL 5.7.12. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html).<a name="2115"></a><a name="2.11.5"></a>

**Version:** 2.11.5

Aurora MySQL 2.11.5 is generally available. Aurora MySQL 2.11 versions are compatible with MySQL 5.7.12. For more information on community changes, see [Changes in MySQL 5.7.12 (2016-04-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html).

Version 2.11.5 is the current default version for Aurora MySQL version 2 when you create a DB cluster. For more information, see [Default Amazon Aurora versions](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.VersionPolicy.html#Aurora.VersionPolicy.DefaultVersions).

The currently supported 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, 3.05.\$1, and 3.06.\$1.

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

If you upgrade an Aurora MySQL global database to version 2.11.\$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). 

Immediately after an in-place engine version upgrade to Aurora MySQL 2.11.\$1 is performed, an operating system upgrade is applied automatically to all affected instances on the db.r4, db.r5, db.t2, and db.t3 DB instance classes, if the instances are running an old operating system version. In a Multi-AZ DB cluster, all of the reader instances apply the operating system upgrade first. When the operating system upgrade on the first reader instance is finished, a failover occurs and the previous writer instance is upgraded.

**Note**  
The operating system upgrade isn't applied automatically to Aurora global databases during major version upgrades.

**Note**  
For information on how to upgrade your Aurora MySQL database cluster, see [Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.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 Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements


**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-22015](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22015)
+ [CVE-2023-22026](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22026)
+ [CVE-2023-22028](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22028)
+ [CVE-2023-22084](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22084)
+ [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-2024-20963](https://nvd.nist.gov/vuln/detail/CVE-2024-20963)

**Availability improvements:**
+ 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, in rare conditions, can cause the reader DB instances to restart.
+ Fixed an issue with lock contention caused by an audit logging thread that can lead to high CPU utilization and client application timeouts.

**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 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.
+ Fixed an issue that can produce an incorrect value of the `Threads_running` variable in the `information_schema` and `performance_schema` global status tables when using write forwarding.

**Upgrades and migrations:**
+ Fixed an issue that prevented initiation of binary log replication on Aurora MySQL DB clusters migrated from RDS for MySQL 5.7.
+ Disabled the database event scheduler during major version upgrades to Aurora MySQL version 3. This helps avoid any changes to the database by event execution while the major version upgrade is in progress.

## Integration of MySQL Community Edition bug fixes


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

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2023-10-17 (version 2.11.4, compatible with MySQL 5.7.12) - RDS Extended Support version
Aurora MySQL updates: 2023-10-17 (version 2.11.4, compatible with MySQL 5.7.12) - RDS Extended Support versionAurora MySQL version 2.11.4, compatible with MySQL 5.7.12

 Aurora MySQL version 2.11.4 is available. This version is compatible with MySQL 5.7.12. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html).<a name="2114"></a><a name="2.11.4"></a>

 **Version:** 2.11.4 

 Aurora MySQL 2.11.4 is generally available. Aurora MySQL 2.11 versions are compatible with MySQL 5.7.12. For more information on community changes, see [Changes in MySQL 5.7.12 (2016-04-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html). 

 The currently supported 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, and 3.04.\$1. 

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

 If you upgrade an Aurora MySQL global database to version 2.11.\$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). 

Immediately after an in-place engine version upgrade to Aurora MySQL 2.11.\$1 is performed, an operating system upgrade is applied automatically to all affected instances on the db.r4, db.r5, db.t2, and db.t3 DB instance classes, if the instances are running an old operating system version. In a Multi-AZ DB cluster, all of the reader instances apply the operating system upgrade first. When the operating system upgrade on the first reader instance is finished, a failover occurs and the previous writer instance is upgraded.

**Note**  
The operating system upgrade isn't applied automatically to Aurora global databases during major version upgrades.

**Note**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.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 Amazon Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html) in the *Amazon Aurora User Guide*. 

## Improvements


**Fixed security issues and CVEs listed below:**
+ Fixed an issue where the events that were reported while processing audit log rotations might not be written to the audit log.
+ [CVE-2022-24407](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24407)

**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 a database instance to restart while executing I/O intensive read workloads.
+ 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 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 reader instance to restart when executing Data Manipulation Language (DML) queries on a table containing a full-text index.
+ Fixed an issue which can cause a reader instance to restart while executing a query which utilizes an Aurora parallel query execution plan.
+ Fixed an issue that can cause the writer instance to restart while executing the `OPTIMIZE TABLE` query on a table with a Full Text Search (FTS) index.
+ 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 small read replica instances may experience increased replication lag after upgrading from versions below 2.11.\$1.
+ Fixed an issue that can cause excessive log messages when consulting the [procs\$1priv grant table](https://dev.mysql.com/doc/refman/8.0/en/grant-tables.html#grant-tables-procs-priv) for verification of requests that involve stored routines.
+ Fixed a memory management issue which can cause the database instance to use excessive memory while executing queries using the hash join optimization.
+ Fixed an issue that caused a restart of the database when executing `SELECT` statements with partitioned tables (created in a version of MySQL supporting the old `ha_partition` partition handler) and parallel query is chosen by the query planner.
+ Fixed an issue which can prevent new client connections from being established to the database when write forwarding is enabled.
+ Reduced binary log (binlog) replication lag when an Aurora MySQL binlog replica is executing `QUERY` events written to the source's binlog file without a default database defined by the `USE` command.
+ 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`.
+ Added support for enabling and disabling session-level binary logging. See [Stored Procedures - Replicating](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html#mysql_rds_enable_session_binlog) in the *Amazon Aurora User Guide*.
+ Fixed an issue that can cause a binlog replica to restart if the system variable [server\$1uuid](https://dev.mysql.com/doc/refman/5.7/en/replication-options.html#sysvar_server_uuid) of the source is missing or has an invalid value.
+ Added support for setting session-level binary log format. See [Stored Procedures - Replicating](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-stored-proc-replicating.html#mysql_rds_set_session_binlog_format) in the *Amazon Aurora User Guide*.
+ Fixed an issue which can cause the `CommitLatency` CloudWatch metric to be incorrectly reported when the `innodb_flush_log_at_trx_commit` parameter is not set to 1.
+ 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 query execution time.
+ 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


This release includes all community bug fixes up to and including 5.7.12, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 2.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v2).
+ Replication: Some binary log events were not always handled correctly. (Bug \$134617506)
+ Fixed an issue which can cause higher CPU utilization due to background TLS certificate rotation (Community Bug Fix \$134284186).
+ In prepared statements, some types of subqueries could cause a server exit. (Bug \$133100586)

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2023-06-09 (version 2.11.3, compatible with MySQL 5.7.12) - RDS Extended Support version
Aurora MySQL updates: 2023-06-09 (version 2.11.3, compatible with MySQL 5.7.12) - RDS Extended Support versionAurora MySQL version 2.11.3, compatible with MySQL 5.7.12

 Aurora MySQL version 2.11.3 is available. This version is compatible with MySQL 5.7.12. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html). <a name="2113"></a><a name="2.11.3"></a>

 **Version:** 2.11.3 

 Aurora MySQL 2.11.3 is generally available. Aurora MySQL 2.11 versions are compatible with MySQL 5.7.12. For more information on community changes, see [Changes in MySQL 5.7.12 (2016-04-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html). 

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

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

 If you upgrade an Aurora MySQL global database to version 2.11.\$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). 

Immediately after an in-place engine version upgrade to Aurora MySQL 2.11.\$1 is performed, an operating system upgrade is applied automatically to all affected instances on the db.r4, db.r5, db.t2, and db.t3 DB instance classes, if the instances are running an old operating system version. In a Multi-AZ DB cluster, all of the reader instances apply the operating system upgrade first. When the operating system upgrade on the first reader instance is finished, a failover occurs and the previous writer instance is upgraded.

**Note**  
The operating system upgrade isn't applied automatically to Aurora global databases during major version upgrades.

 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**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


**Fixed security issues and CVEs listed below:**
+ Updated the default SSL ciphers used by Aurora MySQL to exclude the less secure `DES-CBC3-SHA` values from the [SSL\$1CIPHER](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_ssl_cipher) database parameter. If you encounter SSL connection issues due to the removal of the `DES-CBC3-SHA` cipher, please use an applicable secure cipher from this list, [ConfiguringCipherSuites](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Security.html#AuroraMySQL.Security.SSL.ConfiguringCipherSuites). More information on the MySQL client [Connection Cipher Configuration](https://dev.mysql.com/doc/refman/5.7/en/encrypted-connection-protocols-ciphers.html#encrypted-connection-cipher-configuration) can be found in the MySQL documentation.
+ [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 in database activity streams (DAS) event encryption which may cause database restarts.
+ Fixed two issues which can cause a database restart to fail if it occurred while executing a Data Definition Language (DDL) query.
+ 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:**
+ Introduced file management performance optimizations on binlog replicas to help reduce contention when writing to relay log files.
+ Fixed an issue where setting the `aurora_disable_hash_join` parameter to 1 or ON might not prevent the optimizer from using a hash join.
+ Fixed an issue that can cause the `buffer_pool_read_requests` counter to be reported incorrectly in the `information_schema` metrics.
+ Fixed an issue that can cause the local storage to fill up when performing `LOAD FROM S3` or `SELECT INTO S3` operations. The issue can also lead to higher CPU utilization, database restarts due to low memory, and increased latency for these queries.

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2023-03-24 (version 2.11.2, compatible with MySQL 5.7.12) - RDS Extended Support version
Aurora MySQL updates: 2023-03-24 (version 2.11.2, compatible with MySQL 5.7.12) - RDS Extended Support versionAurora MySQL version 2.11.2, compatible with MySQL 5.7.12

 Aurora MySQL version 2.11.2 is available. This version is compatible with MySQL 5.7.12. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html). <a name="2112"></a><a name="2.11.2"></a>

 **Version:** 2.11.2 

 Aurora MySQL 2.11.2 is generally available. Aurora MySQL 2.11 versions are compatible with MySQL 5.7.12. For more information on community changes, see [Changes in MySQL 5.7.12 (2016-04-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html). 

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

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

 If you upgrade an Aurora MySQL global database to version 2.11.\$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). 

Immediately after an in-place engine version upgrade to Aurora MySQL 2.11.\$1 is performed, an operating system upgrade is applied automatically to all affected instances on the db.r4, db.r5, db.t2, and db.t3 DB instance classes, if the instances are running an old operating system version. In a Multi-AZ DB cluster, all of the reader instances apply the operating system upgrade first. When the operating system upgrade on the first reader instance is finished, a failover occurs and the previous writer instance is upgraded.

**Note**  
The operating system upgrade isn't applied automatically to Aurora global databases during major version upgrades.

 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**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


**General improvements:**
+ Fixed an issue where DB 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 that can cause a reader instance in a global database secondary Region to become out of sync after upgrading to Aurora MySQL version 2.11 if the primary database writer is on Aurora MySQL version 2.10.

**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).

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2023-02-14 (version 2.11.1, compatible with MySQL 5.7.12) - RDS Extended Support version
Aurora MySQL updates: 2023-02-14 (version 2.11.1, compatible with MySQL 5.7.12) - RDS Extended Support versionAurora MySQL version 2.11.1, compatible with MySQL 5.7.12.

 Aurora MySQL version 2.11.1 is available. This version is compatible with MySQL 5.7.12. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html). <a name="2111"></a><a name="2.11.1"></a>

 **Version:** 2.11.1 

 Aurora MySQL 2.11.1 is generally available. Aurora MySQL 2.11 versions are compatible with MySQL 5.7.12. For more information on community changes, see [Changes in MySQL 5.7.12 (2016-04-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html). 

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

 You can upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.11.1. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.11.1. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.11.1. 

 If you upgrade an Aurora MySQL global database to version 2.11.\$1 and you have write forwarding turned on, you must upgrade your primary and secondary DB clusters to the exact same version, including the patch level, to continue using write forwarding. 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). 

Immediately after an in-place engine version upgrade to Aurora MySQL 2.11.\$1 is performed, an operating system upgrade is applied automatically to all affected instances on the db.r4, db.r5, db.t2, and db.t3 DB instance classes, if the instances are running an old operating system version. In a Multi-AZ DB cluster, all of the reader instances apply the operating system upgrade first. When the operating system upgrade on the first reader instance is finished, a failover occurs and the previous writer instance is upgraded.

**Note**  
The operating system upgrade isn't applied automatically to Aurora global databases during major version upgrades.

 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**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


**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-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-2021-2169](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2169)

**Availability improvements:**
+ Fixed an issue where connection surges can cause increased query latency or a database instance restart.
+ Fixed an issue which, in rare cases, can cause an Aurora replica to restart during 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 where connection surges could cause the connection establishment process to take longer to complete or to fail with timeout errors.
+ Fixed an issue where the Advanced Audit log rotation may reduce the freeable memory, which could lead to the database instance restarting.
+ 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 [SSL server status variables](https://dev.mysql.com/doc/refman/8.0/en/server-status-variables.html#statvar_Ssl_accept_renegotiates)) weren't being populated.
+ Fixed an issue where the Data Manipulation Language (DML) statements executing duplicate writes could lead to excessive error logging and increased query latencies.

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2022-10-25 (version 2.11.0, compatible with MySQL 5.7.12) - RDS Extended Support version
Aurora MySQL updates: 2022-10-25 (version 2.11.0, compatible with MySQL 5.7.12) - RDS Extended Support versionAurora MySQL version 2.11.0, compatible with MySQL 5.7.12

 Aurora MySQL version 2.11.0 is available. This version is compatible with MySQL 5.7.12. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html). <a name="2110"></a><a name="2.11.0"></a>

 **Version:** 2.11.0 

 Aurora MySQL 2.11.0 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7.12. For more information on community changes, see [Changes in MySQL 5.7.12 (2016-04-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html). 

 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, 2.11.\$1, 3.01.\$1 and 3.02.\$1. 

 You can upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.11.0. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.11.0. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.11.0. 

 If you upgrade an Aurora MySQL global database to version 2.11.\$1 and you have write forwarding turned on, you must upgrade your primary and secondary DB clusters to the exact same version, including the patch level, to continue using write forwarding. 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*. 

**Note**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


**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 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)

The following CVE fixes are included in this release:
+ [CVE-2022-21460](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21460)
+ [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)
+ [CVE-2022-21417](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21417)
+ [CVE-2022-21304](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21304)
+ [CVE-2022-21303](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21303)
+ [CVE-2022-21245](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21245)
+ [CVE-2021-36222](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-36222)
+ [CVE-2021-28196](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-28196)
+ [CVE-2021-23841](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23841)
+ [CVE-2021-22926](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22926)
+ [CVE-2021-3449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3449)
+ [CVE-2021-2307](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2307)
+ [CVE-2021-2226](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2226)
+ [CVE-2021-2202](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2202)
+ [CVE-2021-2194](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2194)
+ [CVE-2021-2179](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2179)
+ [CVE-2021-2178](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2178)
+ [CVE-2021-2174](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2174)
+ [CVE-2021-2171](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2171)
+ [CVE-2021-2169](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2169)
+ [CVE-2021-2166](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2166)
+ [CVE-2021-2160](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2160)
+ [CVE-2021-2154](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2154)

 **New features:** 
+ With the release of Aurora MySQL version 2.11, a new operating system upgrade is available. We recommend that you apply this pending OS update to all your Aurora MySQL database instances after upgrading to version 2.11. For more information, see [Working with operating system updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_UpgradeDBInstance.Maintenance.html#OS_Updates).
+ A new dynamic configuration option, innodb\$1deadlock\$1detect, may be used to disable deadlock detection. On high concurrency systems, deadlock detection can cause a slowdown when numerous threads wait for the same lock. At times, it may be more efficient to disable deadlock detection and rely on the innodb\$1lock\$1wait\$1timeout setting for transaction rollback when a deadlock occurs. (Bug \$123477773) More information on Innodb deadlock detection can be found in the [MySQL documentation](https://dev.mysql.com/doc/refman/5.7/en/innodb-deadlock-detection.html).
+ The `UUID_TO_BIN`, `BIN_TO_UUID` and `IS_UUID` functions from MySQL 8.0 have been added. More information on using these functions can be found in [MySQL Miscellaneous function](https://dev.mysql.com/doc/refman/8.0/en/miscellaneous-functions.html).
+ Added support for optimizer hints allowing the user to enable or disable Aurora MySQL parallel query on a per-table or per-query basis.
  + [Working with parallel query for Amazon Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-parallel-query.html)
  + [Aurora MySQL hints](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.html#AuroraMySQL.Reference.Hints)
+ Removed R3 instance type support.
+ Added support for R6i instances.

**Availability improvements:**
+ Fixed an issue which can prevent cross region logical replication in a database cluster due to incorrect binlog file and position written to the error logs. This issue may occur when the engine is restarted after running a DDL statement.
+ Fixed an issue which, in rare conditions, can cause Aurora reader instances to restart when running Access-Control List (ACL) statements such as GRANT and FLUSH on the writer instance. This issue is more likely to affect reader instances with a large number of users and ACL operations (e.g., permission changes).
+ Fixed an issue which, in rare conditions, can cause the writer instance to restart or failover when a transaction accesses a row being deleted by another transaction.
+ Improved the Fulltext phrase search performance to significantly reduce the time taken to search phrases in a table with fulltext indexes.
+ Fixed an issue where, after a writer instance restarts, it would get stuck in slow recovery and subsequently restart again. This issue occurs when there are a large number of uncommitted rows in the database at the time of the initial restart.
+ Fixed an issue which, in rare cases, causes the database server to restart due to a long semaphore wait when the [deadlock detector thread](https://dev.mysql.com/doc/refman/5.7/en/innodb-deadlocks.html) gets stuck.
+ Fixed an issue which, in rare cases, can cause the database to restart due to a long semaphore wait when I/O threads become deadlocked.
+ 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 the database server to restart when all of the following conditions are true: 
  + ALLOW\$1INVALID\$1DATES is disabled in SQL MODE.
  + The database server is processing an INSERT, UPDATE, DELETE or SELECT statement with an invalid value of DATETIME type such that the month is not between 1 and 12.
+ Fixed an issue where the binary log retention period was not honored when log-bin was set to OFF, leading to higher than expected storage utilization. After this fix, the binary logs will be purged based on your retention period. More information on how to configure your binary log retention period can be found in the [Aurora MySQL User Guide](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.html#AuroraMySQL.Replication.MySQL.RetainBinlogs).
+ Fixed an issue which can cause the freeable memory on the database instance to reduce when certain Data Control Language (DCL) SQL statements such as GRANT, FLUSH PRIVILEGES etc. are run on that instance. Frequent use of such statements can cause the freeable memory to keep reducing and may cause the database instance to restart because of out-of-memory issues. Use of such statements on the writer instance can also cause the freeable memory on the reader instances to reduce.
+ Introduced a larger read buffer size for reads performed from the relay logs to minimize the number of read I/O operations, which reduces contention between the I/O and SQL threads.
+ Fixed an issue that can cause the mysql.rds\$1rotate\$1slow\$1log stored procedure to fail with the error message "Table 'mysql.slow\$1log\$1backup' doesn't exist".
+ Fixed an issue where excessive query cache invalidation causes higher than expected CPU usage and latencies on the read replica due to the read replica having to read the data from the disk instead of from the query cache. 
+ Fixed an issue which allowed users to run the INSTALL PLUGIN and UNINSTALL PLUGIN commands on a reader instance, which can cause deadlock on LOCK\$1plugin, LOCK\$1system\$1variables\$1hash, LOCK\$1global\$1system\$1variables. These statements can now only be executed on the writer instance in a database cluster.
+ Fixed an issue where clusters may experience higher than expected commit latency when binary logging is enabled. This affects all transactions that generate large binlog events (over 500MB in size).
+ Fixed an issue that can cause the trx\$1active\$1transactions metric in the INFORMATION\$1SCHEMA.INNODB\$1METRICS table to have an incorrect value.
+ Fixed an issue which can stop logical replication due to the binlog file becoming inconsistent while executing a rollback to savepoint for a large transaction.
+ Masked credential hashes in general-log, slow-query-log, and audit-log by default using a consistent mask secret. This is configurable via the aurora\$1mask\$1password\$1hashes\$1type parameter.
+ Fixed an issue where the Zero-Downtime-Restart (ZDR) duration is incorrectly reported in the customer observed events.
+ Fixed an issue which can cause 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 1457](https://dev.mysql.com/doc/mysql-errors/5.7/en/server-error-reference.html#error_er_sp_proc_table_corrupt).
+ Fixed an issue where dump thread initialization could get deadlocked with the thread for purging binary logs. This can stop the active binlog file from rotating and instead continue growing or cause issues with new binlog replica connections.
+ Fixed an issue where the query cache can return stale result on an Aurora read replica.

## Integration of MySQL Community Edition bug fixes


This release includes all community bug fixes up to and including 5.7, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 2.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v2).
+ Fixed an issue where the code for reading character set information from Performance Schema statement events tables (for example, events\$1statements\$1current) did not prevent simultaneous writing to that character set information. As a result, the SQL query text character set could be invalid, which could result in a server exit. With this fix, an invalid character set causes SQL\$1TEXT column truncation and prevents server exits. (Bug \$123540008)
+ InnoDB: Backport of a fix for Community Bug \$125189192, Bug \$184038. Fixed an issue where after a RENAME TABLE operation that moved a table to a different schema, InnoDB failed to update INNODB\$1SYS\$1DATAFILES data dictionary table. This resulted in an error on restart indicating that it could not locate the tablespace data file. 
+ InnoDB: Fixed an issue where the server dropped an internally defined foreign key index when adding a new index and attempted to use a secondary index defined on a virtual generated column as the foreign key index, causing a server exit. InnoDB now permits a foreign key constraint to reference a secondary index defined on a virtual generated column. (Bug \$123533396)
+ Fixed an issue where two sessions concurrently executing an INSERT ... ON DUPLICATE KEY UPDATE operation generated a deadlock. During partial rollback of a tuple, another session could update it. The fix for this bug reverts the fixes for Bug \$111758237, Bug \$117604730, and Bug \$120040791. (Bug \$125966845)
+ Backport of a fix for Community Bug \$127407480: Fixed an issue where the EXECUTE and ALTER ROUTINE privileges weren't correctly granted to routine creators even with automatic\$1sp\$1privileges enabled.
+ Backport of fix for Community Bug\$124671968: Fixed an issue where a query could produce incorrect results if the WHERE clause contained a dependent subquery, the table had a secondary index on the columns in the select list followed by the columns in the subquery, and `GROUP BY` or `DISTINCT` permitted the query to use a Loose Index Scan.
+ Fixed an issue where replication breaks if a multi-table delete statement is issued against multiple tables with foreign keys. (Bug \$180821)
+ Fixed an issue where in special cases certain slave errors are not ignored even with [slave\$1skip\$1errors](https://dev.mysql.com/doc/refman/5.6/en/replication-options-replica.html#sysvar_slave_skip_errors) enabled. In cases when opening and locking a table failed or when field conversions failed on a server running row-based replication, the error is considered critical and the state of [slave\$1skip\$1errors](https://dev.mysql.com/doc/refman/5.6/en/replication-options-replica.html#sysvar_slave_skip_errors) is ignored. The fix ensures that with [slave\$1skip\$1errors](https://dev.mysql.com/doc/refman/5.6/en/replication-options-replica.html#sysvar_slave_skip_errors)) enabled, all errors reported during applying a transaction are correctly handled. (Bug \$170640, Bug \$117653275)
+ Fixed an issue where a [https://dev.mysql.com/doc/refman/5.7/en/set-password.html](https://dev.mysql.com/doc/refman/5.7/en/set-password.html) statement was replicated from a MySQL 5.6 master to a MySQL 5.7 slave, or from a MySQL 5.7 master with the [log\$1builtin\$1as\$1identified\$1by\$1password](https://dev.mysql.com/doc/refman/5.7/en/replication-options-binary-log.html#sysvar_log_builtin_as_identified_by_password) system variable set to ON to a MySQL 5.7 slave, the password hash was itself also hashed before being stored on the slave. The issue has now been fixed and the replicated password hash is stored as originally passed to the slave. (Bug\$124687073)
+ Fixed an issue where serialization of a JSON value consisting of a large sub-document wrapped in many levels of JSON arrays, objects, or both, sometimes required an excessive amount time to complete. (Bug \$123031146)
+  Statements that cannot be parsed (due, for example, to syntax errors) are no longer written to the slow query log. (Bug \$133732907) 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2022-11-01 (version 2.10.3) (Deprecated)
Aurora MySQL updates: 2022-11-01 (version 2.10.3) (Deprecated)Aurora MySQL version 2.10.3, compatible with MySQL 5.7

 Aurora MySQL version 2.10.3 is available. This version is compatible with MySQL 5.7. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html). <a name="2103"></a><a name="2.10.3"></a>

 **Version:** 2.10.3 

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

 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, 2.11.\$1, 3.01.\$1 and 3.02.\$1. 

 You can upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.10.3. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.10.3. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.10.3. 

 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**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


**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-21444](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21444)
+ [CVE-2022-21344](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21344)
+ [CVE-2022-21304](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21304)
+ [CVE-2022-21245](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21245)
+ [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)

 **General improvements:** 
+ Fixed an issue which, in rare conditions, causes the database server to restart due to a long semaphore wait when the [deadlock detector thread](https://dev.mysql.com/doc/refman/5.7/en/innodb-deadlocks.html) gets stuck.
+ Fixed an issue which can cause the freeable memory on the database instance to reduce when certain Data Control Language (DCL) SQL statements such as GRANT, FLUSH PRIVILEGES etc. are run on that instance. Frequent use of such statements can cause the freeable memory to keep reducing and may cause the database instance to restart because of out-of-memory issues. Use of such statements on the writer instance can also cause the freeable memory on the reader instances to reduce.
+ Fixed an issue where queries against the "performance\$1schema.events\$1waits\$1summary\$1global\$1by\$1event\$1name" table may become slow when a database instance is under heavy load with the "wait/io/aurora\$1respond\$1to\$1client" performance\$1schema wait event enabled.
+ Fixed an issue which, in rare conditions, can cause the database server to stall and restart when transactions partially roll back due to a constraint violation on the secondary indexes.
+ Fixed an issue which, in rare conditions, can cause the writer instance to restart or failover when a transaction accesses a row being deleted by another transaction.
+ Fixed an issue which, in rare conditions, can cause the database to restart due to a long semaphore wait when I/O threads become deadlocked.
+ Fixed an issue which can cause the read replica to restart during failover in rare conditions when the Unix socket lock file is in use.
+ Fixed an issue where excessive query cache invalidation causes higher than expected CPU usage and latencies on the read replica due to the read replica having to read the data from the disk instead of from the query cache.

## Integration of MySQL Community Edition bug fixes


This release includes all community bug fixes up to and including 5.7, in addition to the below. For more information, see [MySQL bugs fixed by Aurora MySQL 2.x database engine updates](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.MySQLBugs.html#AuroraMySQL.Updates.MySQLBugs.v2).
+ Fixed an issue where the code for reading character set information from Performance Schema statement events tables (for example, events\$1statements\$1current) did not prevent simultaneous writing to that character set information. As a result, the SQL query text character set could be invalid, which could result in a server exit. With this fix, an invalid character set causes SQL\$1TEXT column truncation and prevents server exits. (Bug \$123540008)
+ Fixed an issue when an UPDATE required a temporary table having a primary key larger than 1024 bytes and that table was created using InnoDB, the server could exit. (Bug \$125153670)
+ Fixed an issue where two sessions concurrently executing an INSERT ... ON DUPLICATE KEY UPDATE operation generated a deadlock. During partial rollback of a tuple, another session could update it. The fix for this bug reverts the fixes for Bug \$111758237, Bug \$117604730, and Bug \$120040791. (Bug \$125966845)

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2022-01-26 (version 2.10.2) (Deprecated)
Aurora MySQL updates: 2022-01-26 (version 2.10.2) (Deprecated)Aurora MySQL version 2.10.2

 Aurora MySQL version 2.10.2 is available. <a name="2102"></a><a name="2.10.2"></a>

 **Version:** 2.10.2 

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

 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 upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.10.0. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.10.0. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.10.0. 

 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**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


**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-35624](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35624)
+ [CVE-2021-35604](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-35604)
+ [CVE-2021-22926](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22926)
+ [CVE-2021-2390](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2390)
+ [CVE-2021-2389](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2389)
+ [CVE-2021-2385](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2385)
+ [CVE-2021-2356](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2356)
+ [CVE-2019-17543](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17543)
+ [CVE-2019-2960](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2960)

 **General improvements:** 
+  Added a performance optimization to help reduce database IO latency in 24XL instance classes. 
+  Added support for ECDHE SSL ciphers. For more information on configuring your clients to use these SSL Ciphers please see the following MySQL documentation, [encrypted connection protocols ciphers](https://dev.mysql.com/doc/refman/5.7/en/encrypted-connection-protocols-ciphers.html#encrypted-connection-cipher-configuration) 
+  Fixed security issues related to Aurora MySQL integration with other AWS Services such as Amazon S3, Amazon ML, and AWS Lambda. 
+  Fixed an issue which can cause a database instance restart to fail when the database has approximately over 1GB of user and privilege combinations. 
+  Fixed an issue with Parallel Query which could cause the database to return incorrect groupings or sort order when executing queries with a GROUP BY clause and a WHERE clause that contain a range predicate. 
+  Fixed an issue which causes general\$1log and slow\$1log tables to become inaccessible after an in-place major version upgrade from Aurora MySQL 1.x (compatible with MySQL 5.6) to Aurora MySQL 2.x (compatible with MySQL 5.7). 
+  Fixed an issue which, in rare cases, causes the database instance to restart when innodb\$1trx, innodb\$1locks or innodb\$1lockwaits tables are queried while the database is under heavy workload. Monitoring tools such as Performance Insights may query such tables. 
+  Fixed an issue where the value of a TIMESTAMP column of an existing row is updated to the latest timestamp when all of the following conditions are satisfied: 

  1. A trigger exists for the table.

  1. An INSERT is performed on the table that has an ON DUPLICATE KEY UPDATE clause.

  1. The inserted row causes a duplicate value violation in a UNIQUE index or PRIMARY KEY.

  1. One or more columns are of TIMESTAMP data type and have a default value of CURRENT\$1TIMESTAMP.
+  Fixed an issue which, in rare cases, could prevent a binlog replica from connecting to an instance with binlog enabled. 
+  Fixed an issue where, in rare conditions, transactions were unable to commit when running on an instance with binlog enabled. 
+  Fixed an issue where new connections could not be established to an instance with binlog enabled. 
+  Fixed an issue which can cause excessive internal logging when attempting zero downtime patching and restart causing local storage to fill up. 
+  Fixed an issue that causes a binlog replica to stop with an HA\$1ERR\$1FOUND\$1DUPP\$1KEY error when replicating certain DDL and DCL statements. The issue occurs when the source instance is configured with MIXED binary logging format and READ COMMITTED or READ UNCOMMITTED isolation level. 
+  Fixed an issue where the binlog replication I/O thread is unable to keep up with the primary instance, when multi-threaded replication is enabled 
+  Fixed an issue where, in rare conditions, a high number of active connections to the database instance may cause the CloudWatch CommitLatency metric to be incorrectly reported. 
+  Fixed an issue which causes local storage on Graviton instances to fill up when performing LOAD FROM S3 or SELECT INTO S3. 
+  Fixed an issue which can cause wrong query results when querying a table with a foreign key and both of the following conditions are met: 

  1.  Query cache is enabled 

  1.  A transaction with a cascading delete or update on that table is rolled back 
+  Fixed an issue which, in rare conditions, can cause Aurora reader instances to restart. The chance of this issue occurring increases as the number of transaction rollbacks increases. 
+  Fixed an issue where the number of mutex 'LOCK\$1epoch\$1id\$1master' occurrences in Performance Schema increases when a session is opened and closed. 
+  Fixed an issue which can cause an increasing number of deadlocks for workloads which have many transactions updating the same set of rows concurrently. 
+  Fixed an issue which, in rare conditions, can cause the instances to restart when the database volume grows to a multiple of 160GB. 
+  Fixed an issue with Parallel Query which could cause the database to restart when executing SQL statements with a LIMIT clause. 
+  Fixed an issue which, in rare conditions, can cause the database instance to restart when using XA transactions with the READ COMMITTED isolation level. 
+  Fixed an issue where, after an Aurora Read instance restarts, it may restart again if there is a heavy DDL workload during the restart. 
+  Fixed an issue with incorrect reporting of Aurora reader replication lag. 
+  Fixed an issue which, in rare conditions, can cause a writer instance to restart when an in-memory data-integrity check fails. 
+  Fixed an issue which, in rare conditions, incorrectly shows the “Database Load” chart in Performance Insights (PI) sessions as actively using CPU even though the sessions have finished processing and are idle. 
+  Fixed an issue which, in rare conditions, can cause the database server to restart when a query is processed using Parallel Query. 
+  Fixed an issue which, in rare conditions, can cause the writer instance in a primary Global Database cluster to restart because of a race condition during Global Database replication. 
+  Fixed an issue that can occur during a database instance restart, which can cause more than one restart. 

## Integration of MySQL Community Edition bug fixes

+  Fixed an issue in InnoDB where an error in code related to table statistics raised an assertion in the dict0stats.cc source file. (Bug \$124585978) 
+  Fixed an issue where a secondary index over a virtual column became corrupted when the index was built online. For [UPDATE](https://dev.mysql.com/doc/refman/5.7/en/update.html) statements, we fix this as follows: If the virtual column value of the index record is set to NULL, then we generate this value from the cluster index record. (Bug \$130556595)) 
+  Fixed an issue in InnoDB where deleting marked rows were able to acquire an external read lock before a partial rollback was completed. The external read lock prevented conversion of an implicit lock to an explicit lock during the partial rollback, causing an assertion failure. (Bug \$129195848) 
+  Fixed an issue where the empty host names in accounts could cause the server to misbehave. (Bug \$128653104) 
+  Fixed an issue in InnoDB where a query interruption during a lock wait caused an error. (Bug \$128068293) 
+  Fixed an issue in replication where Interleaved transactions could sometimes deadlock the slave applier when the transaction isolation level was set to [REPEATABLE READ](https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html#isolevel_repeatable-read). (Bug \$125040331) 
+  Fixed an issue which can cause binlog replicas to stall due to lock wait timeout. (Bug \$127189701) 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2021-10-21 (version 2.10.1) (Deprecated)
Aurora MySQL updates: 2021-10-21 (version 2.10.1) (Deprecated)Aurora MySQL version 2.10.1

 Aurora MySQL version 2.10.1 is available. <a name="2101"></a><a name="2.10.1"></a>

 **Version:** 2.10.1 

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

 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 upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.10.0. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.10.0. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.10.0. 

 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**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


**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-2307](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2307)
+ [CVE-2021-2226](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2226)
+ [CVE-2021-2194](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2194)
+ [CVE-2021-2174](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2174)
+ [CVE-2021-2171](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2171)
+ [CVE-2021-2169](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2169)
+ [CVE-2021-2166](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2166)
+ [CVE-2021-2160](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2160)
+ [CVE-2021-2154](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2154)
+ [CVE-2021-2032](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2032)
+ [CVE-2021-2001](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2001)

 **Availability improvements:** 
+ Added the ability to cleanly shut down the cluster for future major version upgrades.

 **General improvements:** 
+  Fixed an issue that can cause high CPU consumption on the reader instances due to excessive logging of informational messages in internal diagnostic log files. 
+  Fixed an issue where the value of a TIMESTAMP column of an existing row is updated to the latest timestamp when all of the following conditions are satisfied: 

  1. A trigger exists for the table.

  1. An INSERT is performed on the table that has an ON DUPLICATE KEY UPDATE clause.

  1. The inserted row causes a duplicate value violation in a UNIQUE index or PRIMARY KEY.

  1. One or more columns are of TIMESTAMP data type and have a default value of CURRENT\$1TIMESTAMP.
+  Fixed an issue introduced in version 2.10.0 which causes use of json\$1merge function to raise an error code in certain cases. In particular, when json\$1merge function is used in a DDL containing generated columns, it can return error code 1305. 
+  Fixed an issue where, in rare conditions, read replicas restarts when a large object's update history is being validated for a transaction's read view on the read replica. 
+  Fixed an issue which, in rare conditions, causes a writer instance to restart when an in-memory data- integrity check fails. 

## Integration of MySQL community edition bug fixes

+  CURRENT\$1TIMESTAMP PRODUCES ZEROS IN TRIGGER. (Bug \$125209512) 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2021-05-25 (version 2.10.0) (Deprecated)
Aurora MySQL updates: 2021-05-25 (version 2.10.0) (Deprecated)Aurora MySQL version 2.10.0

 Aurora MySQL version 2.10.0 is available. Some of the highlights include [higher availability of reader instances during writer restarts](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_RebootCluster.html), [improvements to zero-downtime patching (ZDP)](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html), [improvements to zero-downtime restart (ZDR)](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.html), and the [binlog I/O cache optimization](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.html). <a name="2100"></a><a name="2.10.0"></a>

 **Version:** 2.10.0 

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

 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 upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.10.0. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.10.0. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.10.0. 

 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**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


**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-23841](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23841)
+ [CVE-2021-3449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3449)
+ [CVE-2020-28196](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28196)
+ [CVE-2020-14790](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14790)
+ [CVE-2020-14776](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14776)
+  [CVE-2020-14567](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14567) 
+  [CVE-2020-14559](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14559) 
+  [CVE-2020-14553](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14553) 
+  [CVE-2020-14547](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14547) 
+  [CVE-2020-14540](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14540) 
+  [CVE-2020-14539](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14539) 
+  [CVE-2018-3251](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3251) 
+  [CVE-2018-3156](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3156) 
+  [CVE-2018-3143](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3143) 
+ [CVE-2016-5440](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5440)

 **New features:** 
+  The `db.t3.large` instance class is now supported for Aurora MySQL. 
+  *Binary log replication:* 
  +  Introduced the binlog I/O cache to improve binlog performance by reducing contention between writer threads and dump threads. For more information, see [ Optimizing binary log replication](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.html#binlog-optimization) in the *Amazon Aurora User Guide*. 
  +  In [Aurora MySQL version 2.08](AuroraMySQL.Updates.2080.md), we introduced improved binary log (binlog) processing to reduce crash recovery time and commit time latency when very large transactions are involved. These improvements are now supported for clusters that have GTID enabled. 
+  *Improved reader instance availability:* 
  +  Previously, when a writer instance restarted, all reader instances in an Aurora MySQL cluster restarted as well. With today's launch, in-Region 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 MySQL cluster (version 2.10 and higher)](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_RebootCluster.html#aurora-mysql-survivable-replicas) in the *Amazon Aurora User Guide*. 
**Important**  
 After you upgrade to Aurora MySQL 2.10, rebooting the writer instance doesn't perform a reboot of the entire cluster. If you want to reboot the entire cluster, now you reboot any reader instances in the cluster after rebooting the writer instance. 
+  Improved the performance of the read ahead page reads requested by logical read ahead (LRA) technique. This was done by batching the multiple page reads in a single request sent to Aurora storage. As a result, the queries that use the LRA optimization execute up to 3x faster. 
+  *Zero-downtime restarts and patching:* 
  +  Improved zero-downtime restart (ZDR) and zero-downtime patching (ZDP) to enable ZDR and ZDP in a wider range of scenarios, including the added support for cases when binary logging is enabled. Also, improved visibility into ZDR and ZDP events. See documentation for details: [ Zero-downtime restart (ZDR) for Amazon Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Replication.html#AuroraMySQL.Replication.Availability) and [ Using zero-downtime patching](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html#AuroraMySQL.Updates.ZDP) in the *Amazon Aurora User Guide*. 

 **Availability improvements:** 
+  Improvements for faster startup when the database has a large number of temporary indexes and tables created during a prior interrupted DDL activity. 
+  Fixed multiple issues related to repeated restarts during the crash recovery of interrupted DDL operations, such as `DROP TRIGGER`, `ALTER TABLE`, and specifically `ALTER TABLE` that modifies the type of partitioning or number of partitions in a table. 
+  Fixed an issue that could cause a server restart during Database Activity Streams (DAS) log processing. 
+  Fixed an issue printing an error message while processing an `ALTER` query on system tables. 

 **General improvements:** 
+  Fixed an issue where the query cache could return stale results on a reader instance. 
+  Fixed an issue where some Aurora commit metrics were not being updated when the system variable `innodb_flush_log_at_trx_commit` was set to 0 or 2. 
+  Fixed an issue where a query result stored in the query cache was not refreshed by multistatement transactions. 
+  Fixed an issue that could cause the last-modified timestamp of binary log files to not be updated correctly. This could lead to binary log files being purged prematurely, before reaching the customer-configured retention period. 
+  Fixed incorrect reported binlog file name and position from InnoDB after crash recovery. 
+  Fixed an issue that could cause large transactions to generate incorrect binlog events if the `binlog_checksum` parameter was set to `NONE`. 
+  Fixed an issue that caused a binlog replica to stop with an error if the replicated transaction contained a DDL statement and a large number of row changes. 
+  Fixed an issue leading to a restart in a reader instance when dropping a table. 
+  Fixed an issue that caused open source connectors to fail when attempting to consume a binlog file with a large transaction. 
+  Fixed an issue that could lead to incorrect query results on the large geometry column after creating a spatial index on the table with the large geometry values. 
+  The database now recreates the temporary tablespace during restart, which allows the associated storage space to be freed and reclaimed. 
+  Fixed an issue that prevented `performance_schema` tables from being truncated on Aurora reader instances. 
+  Fixed an issue that caused a binlog replica to stop with an `HA_ERR_KEY_NOT_FOUND` error. 
+  Fixed an issue that caused the database to restart when running `FLUSH TABLES WITH READ LOCK` statement. 
+  Fixed an issue that prevented the use of user-level lock functions on Aurora reader instances. 

## Integration of MySQL community edition bug fixes

+  Interleaved transactions could sometimes deadlock the replica applier when the transaction isolation level was set to [REPEATABLE READ](https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html#isolevel_repeatable-read). (Bug \$125040331) 
+  When a stored procedure contained a statement referring to a view which in turn referred to another view, the procedure could not be invoked successfully more than once. (Bug \$187858, Bug \$126864199) 
+  For queries with many `OR` conditions, the optimizer now is more memory-efficient and less likely to exceed the memory limit imposed by the [range\$1optimizer\$1max\$1mem\$1size](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_range_optimizer_max_mem_size) system variable. In addition, the default value for that variable has been raised from 1,536,000 to 8,388,608. (Bug \$179450, Bug \$122283790) 
+  *Replication:* In the `next_event()` function, which is called by a replica's SQL thread to read the next event from the relay log, the SQL thread did not release the `relaylog.log_lock` it acquired when it ran into an error (for example, due to a closed relay log), causing all other threads waiting to acquire a lock on the relay log to hang. With this fix, the lock is released before the SQL thread leaves the function under the situation. (Bug \$121697821) 
+  Fixing a memory corruption for `ALTER TABLE` with virtual column. (Bug \$124961167; Bug \$124960450) 
+  *Replication:* Multithreaded replicas could not be configured with small queue sizes using [slave\$1pending\$1jobs\$1size\$1max](https://dev.mysql.com/doc/refman/5.7/en/replication-options-replica.html#sysvar_slave_pending_jobs_size_max) if they ever needed to process transactions larger than that size. Any packet larger than [slave\$1pending\$1jobs\$1size\$1max](https://dev.mysql.com/doc/refman/5.7/en/replication-options-replica.html#sysvar_slave_pending_jobs_size_max) was rejected with the error `ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX`, even if the packet was smaller than the limit set by [slave\$1max\$1allowed\$1packet](https://dev.mysql.com/doc/refman/5.7/en/replication-options-replica.html#sysvar_slave_max_allowed_packet). With this fix, [slave\$1pending\$1jobs\$1size\$1max](https://dev.mysql.com/doc/refman/5.7/en/replication-options-replica.html#sysvar_slave_pending_jobs_size_max) becomes a soft limit rather than a hard limit. If the size of a packet exceeds [slave\$1pending\$1jobs\$1size\$1max](https://dev.mysql.com/doc/refman/5.7/en/replication-options-replica.html#sysvar_slave_pending_jobs_size_max) but is less than [slave\$1max\$1allowed\$1packet](https://dev.mysql.com/doc/refman/5.7/en/replication-options-replica.html#sysvar_slave_max_allowed_packet), the transaction is held until all the replica workers have empty queues, and then processed. All subsequent transactions are held until the large transaction has been completed. The queue size for replica workers can therefore be limited while still allowing occasional larger transactions. (Bug \$121280753, Bug \$177406) 
+  *Replication:* When using a multithreaded replica, applier errors displayed worker ID data that was inconsistent with data externalized in Performance Schema replication tables. (Bug \$125231367) 
+  *Replication:* On a GTID-based replication replica running with [-gtid-mode=ON](https://dev.mysql.com/doc/refman/5.7/en/replication-options-gtids.html#sysvar_gtid_mode), [-log-bin=OFF](https://dev.mysql.com/doc/refman/5.7/en/replication-options-binary-log.html#sysvar_log_bin), and using [-slave-skip-errors](https://dev.mysql.com/doc/refman/5.7/en/replication-options-replica.html#sysvar_slave_skip_errors), when an error was encountered that should be ignored `Exec_Master_Log_Pos` was not being correctly updated, causing `Exec_Master_Log_Pos` to loose synchrony with `Read_master_log_pos`. If a `GTID_NEXT` was not specified, the replica would never update its GTID state when rolling back from a single statement transaction. The `Exec_Master_Log_Pos` would not be updated because even though the transaction was finished, its GTID state would show otherwise. The fix removes the restraint of updating the GTID state when a transaction is rolled back only if `GTID_NEXT` is specified. (Bug \$122268777) 
+  *Replication:* A partially failed statement was not correctly consuming an auto-generated or specified GTID when binary logging was disabled. The fix ensures that a partially failed [DROP TABLE](https://dev.mysql.com/doc/refman/5.7/en/drop-table.html), a partially failed [DROP USER](https://dev.mysql.com/doc/refman/5.7/en/drop-user.html), or a partially failed [DROP VIEW](https://dev.mysql.com/doc/refman/5.7/en/drop-view.html) consume respectively the relevant GTID and save it into `@@GLOBAL.GTID_EXECUTED` and `mysql.gtid_executed` table when binary logging is disabled. (Bug \$121686749) 
+  *Replication:* Replicas running MySQL 5.7 could not connect to a MySQL 5.5 source due to an error retrieving the [server\$1uuid](https://dev.mysql.com/doc/refman/5.7/en/replication-options.html#sysvar_server_uuid), which is not part of MySQL 5.5. This was caused by changes in the method of retrieving the `server_uuid`. (Bug \$122748612) 
+  *Replication:* The GTID transaction skipping mechanism that silently skips a GTID transaction that was previously executed did not work properly for XA transactions. (Bug \$125041920) 
+  [">XA ROLLBACK](https://dev.mysql.com/doc/refman/5.7/en/xa.html) statements that failed because an incorrect transaction ID was given, could be recorded in the binary log with the correct transaction ID, and could therefore be actioned by replication replicas. A check is now made for the error situation before binary logging takes place, and failed XA `ROLLBACK` statements are not logged. (Bug \$126618925) 
+  *Replication:* If a replica was set up using a [CHANGE MASTER TO](https://dev.mysql.com/doc/refman/5.7/en/change-master-to.html) statement that did not specify the source log file name and source log position, then shut down before [START SLAVE](https://dev.mysql.com/doc/refman/5.7/en/start-slave.html) was issued, then restarted with the option [-relay-log-recovery](https://dev.mysql.com/doc/refman/5.7/en/replication-options-replica.html#sysvar_relay_log_recovery)) set, replication did not start. This happened because the receiver thread had not been started before relay log recovery was attempted, so no log rotation event was available in the relay log to provide the source log file name and source log position. In this situation, the replica now skips relay log recovery and logs a warning, then proceeds to start replication. (Bug \$128996606, Bug \$193397) 
+  *Replication:* In row-based replication, a message that incorrectly displayed field lengths was returned when replicating from a table with a `utf8mb3` column to a table of the same definition where the column was defined with a `utf8mb4` character set. (Bug \$125135304, Bug \$183918) 
+  *Replication:* When a [RESET SLAVE](https://dev.mysql.com/doc/refman/5.7/en/reset-slave.html) statement was issued on a replication replica with GTIDs in use, the existing relay log files were purged, but the replacement new relay log file was generated before the set of received GTIDs for the channel had been cleared. The former GTID set was therefore written to the new relay log file as the `PREVIOUS_GTIDS` event, causing a fatal error in replication stating that the replica had more GTIDs than the source, even though the gtid\$1executed set for both servers was empty. Now, when `RESET SLAVE` is issued, the set of received GTIDs is cleared before the new relay log file is generated, so that this situation does not occur. (Bug \$127411175) 
+  *Replication:* With GTIDs in use for replication, transactions including statements that caused a parsing error ([ER\$1PARSE\$1ERROR](https://dev.mysql.com/doc/mysql-errors/8.0/en/server-error-reference.html#error_er_parse_error)) could not be skipped manually by the recommended method of injecting an empty or replacement transaction with the same GTID. This action should result in the replica identifying the GTID as already used, and therefore skipping the unwanted transaction that shared its GTID. However, in the case of a parsing error, because the statement was parsed before the GTID was checked to see if it needed to be skipped, the replication applier thread stopped due to the parsing error, even though the intention was for the transaction to be skipped anyway. With this fix, the replication applier thread now ignores parsing errors if the transaction concerned needs to be skipped because the GTID was already used. Note that this behavior change does not apply in the case of workloads consisting of binary log output produced by `mysqlbinlog`. In that situation, there would be a risk that a transaction with a parsing error that immediately follows a skipped transaction would also be silently skipped, when it ought to raise an error. (Bug \$127638268) 
+  *Replication:* Enable the SQL thread to GTID skip a partial transaction. (Bug \$125800025) 
+  *Replication:* When a negative or fractional timeout parameter was supplied to `WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS()`, the server behaved in unexpected ways. With this fix: 
  +  A fractional timeout value is read as-is, with no round-off. 
  +  A negative timeout value is rejected with an error if the server is on a strict SQL mode; if the server is not on a strict SQL mode, the value makes the function return `NULL` immediately without any waiting and then issue a warning. (Bug \$124976304, Bug \$183537) 
+  *Replication:* If the `WAIT_FOR_EXECUTED_GTID_SET()` function was used with a timeout value including a fractional part (for example, 1.5), an error in the casting logic meant that the timeout was rounded down to the nearest whole second, and to zero for values less than 1 second (for example, 0.1). The casting logic has now been corrected so that the timeout value is applied as originally specified with no rounding. Thanks to Dirkjan Bussink for the contribution. (Bug \$129324564, Bug \$194247) 
+  With GTIDs enabled, [XA COMMIT](https://dev.mysql.com/doc/refman/5.7/en/xa.html) on a disconnected XA transaction within a multiple-statement transaction raised an assertion. (Bug \$122173903) 
+  *Replication:* An assertion was raised in debug builds if an [XA ROLLBACK](https://dev.mysql.com/doc/refman/5.7/en/xa.html) statement was issued for an unknown transaction identifier when the [gtid\$1next](https://dev.mysql.com/doc/refman/5.7/en/replication-options-gtids.html#sysvar_gtid_next) value had been set manually. The server now does not attempt to update the GTID state if an XA `ROLLBACK` statement fails with an error. (Bug \$127928837, Bug \$190640) 
+  Fix wrong sorting order issue when multiple `CASE` functions are used in `ORDER BY` clause (Bug\$122810883). 
+  Some queries that used ordering could access an uninitialized column during optimization and cause a server exit. (Bug \$127389294) 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2021-11-12 (version 2.09.3) (Deprecated)
Aurora MySQL updates: 2021-11-12 (version 2.09.3) (Deprecated)Aurora MySQL version 2.09.3

 Aurora MySQL version 2.09.3 is available. 

 **Version:** 2.09.3 

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

 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 upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.10.0. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.10.0. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.10.0. 

 To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the Amazon RDS API. 

 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**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


 **Security fixes:** 

 Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes below: 
+  [CVE-2021-23841](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23841) 
+  [CVE-2021-3712](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3712) 
+  [CVE-2021-3449](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3449) 
+  [CVE-2021-2307](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2307) 
+  [CVE-2021-2226](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2226) 
+  [CVE-2021-2174](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2174) 
+  [CVE-2021-2171](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2171) 
+  [CVE-2021-2169](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2169) 
+  [CVE-2021-2166](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2166) 
+  [CVE-2021-2154](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2154) 
+  [CVE-2021-2060](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2060) 
+  [CVE-2021-2032](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2032) 
+  [CVE-2021-2001](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2001) 
+  [CVE-2020-28196](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28196) 
+  [CVE-2020-14769](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14769) 
+  [CVE-2019-17543](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17543) 
+  [CVE-2019-2960](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-CVE-2019-2960) 

 **Availability improvements:** 
+ Introduced an optimization which can reduce contention for queries that are executed on tables in information\$1schema.
+  Add support for ECDHE SSL ciphers. 

 **General improvements:** 
+ Fixed an issue which, in rare conditions, can cause a writer instance to restart when an in-memory data-integrity check fails. 
+ Fixed an issue which, in rare conditions, can cause the database instance to restart when the cluster volume is expanding while binary logging is enabled.
+ Fixed a rare race condition during a database instance restart, which can cause more than one restart.
+ Fixed an issue which can cause a database instance restart to fail when the database has a large number of user and privilege combinations.
+ Fixed an issue with parallel query which can cause the database to restart when executing SQL statements with LIMIT clause.
+ Fixed an issue with incorrect reporting of aurora replication lag.
+ Fixed an issue which can cause general\$1log and slow\$1log tables to become inaccessible after in-place major version upgrade from Aurora-MySQL 1.x (based on MySQL 5.6) to Aurora-MySQL 2.x (based on MySQL 5.7).
+ Fixed an issue which, in rare cases, can cause the database instance to restart when innodb\$1trx, innodb\$1locks or innodb\$1lockwaits tables are queried while the database is under heavy workload. Monitoring tools and features such as performance insights may query such tables.
+ Fixed an issue which can cause a database instance to restart when "FLUSH TABLES WITH READ LOCK" SQL statement is executed.
+ Fixed an issue where the InnoDB purge process pauses during the deletion of a reader instance leading to a temporary increase in history list length.
+ Fixed an issue with parallel query which can cause the database to restart when executing a SQL statement against a table containing a virtual column.
+ Fixed an issue with parallel query which can cause the database to return incorrect groupings or sort order when executing queries with GROUP BY clause and a WHERE clause containing a range predicate.
+ Fixed an issue in parallel query which, in rare conditions, can cause the database to restart when executing SQL statements with JSON functions.
+ Fixed an issue which, in rare conditions, can cause the writer instance in primary Global Database cluster to restart because of a race condition during Global Database Replication.
+ Fixed an issue that can cause a Binlog replica to stop with an HA\$1ERR\$1FOUND\$1DUPP\$1KEY error when replicating certain DDL and DCL statements. The issue occurs when the source instance is configured with MIXED binary logging format and READ COMMITTED or READ UNCOMMITTED isolation level.
+ Fixed an issue which, in rare conditions, can cause the database instance to restart when using XA transactions in READ COMMITTED isolation level.
+ Fixed an issue where the value of a TIMESTAMP column of an existing row is updated to the latest timestamp when all of the following conditions are satisfied: 1. a trigger exists for the table; 2. an INSERT is performed on the table that has an ON DUPLICATE KEY UPDATE clause; 3. the inserted row can cause a duplicate value violation in a UNIQUE index or PRIMARY KEY; and 4. one or more columns are of TIMESTAMP data type and have a default value of CURRENT\$1TIMESTAMP.
+ Fixed an issue which, in rare conditions, can cause a reader instance to restart due to an incorrect check processing.
+ Fixed an issue which can cause the reader instance to restart when the writer instance grows the database volume to cross specific volume size boundaries.
+ Fixed an issue which can cause longer restart times for database instances using cloned cluster volumes.
+ Fixed an issue where a database instance restart may fail one or more times after a TRUNCATE TABLE operation was performed on the writer instance.
+ Fixed an issue which, in rare conditions, can cause the database instance to restart.
+ Fixed an issue which, in rare conditions, can cause the writer instance to restart when the database volume grows to a multiple of 160GB.

## Integration of MySQL community edition bug fixes

+ Bug \$123533396 - When adding a new index, the server dropped an internally defined foreign key index and attempted to use a secondary index defined on a virtual generated column as the foreign key index, causing a server exit. InnoDB now permits a foreign key constraint to reference a secondary index defined on a virtual generated column.
+ Bug \$129550513 - Replication: A locking issue in the WAIT\$1FOR\$1EXECUTED\$1GTID\$1SET() function can cause the server to hang in certain circumstances. The issue has now been corrected.

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2021-02-26 (version 2.09.2) (Deprecated)
Aurora MySQL updates: 2021-02-26 (version 2.09.2) (Deprecated)Aurora MySQL version 2.09.2

 Aurora MySQL version 2.09.2 is available. 

 **Version:** 2.09.2 

 Aurora MySQL 2.09.2 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6. 

 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 upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.09.2. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.09.2. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.09.2. 

 To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the Amazon RDS API. 

 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**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


 **New features:** 
+  Aurora MySQL clusters now support the following EC2 R6g instances powered by Arm-based AWS Graviton2 processors: `r6g.large`, `r6g.xlarge`, `r6g.2xlarge`, `r6g.4xlarge`, `r6g.8xlarge`, `r6g.12xlarge`, `r6g.16xlarge`. For more information, see [ Aurora DB instance classes](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Concepts.DBInstanceClass.html) in the *Amazon Aurora User Guide*. 

 **Security fixes:** 

 Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes below: 
+  [CVE-2020-14775](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14775) 
+  [CVE-2020-14793](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14793) 
+  [CVE-2020-14765](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14765) 
+  [CVE-2020-14769](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14769) 
+  [CVE-2020-14812](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14812) 
+  [CVE-2020-14760](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14760) 
+  [CVE-2020-14672](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14672) 
+  [CVE-2020-14790](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14790) 
+  [CVE-2020-1971](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1971) 

 **Availability improvements:** 
+  Fixed an issue introduced in 2.09.0 that can cause elevated write latency during the scaling of the cluster storage volume. 
+  Fixed an issue in the dynamic resizing feature that could cause Aurora Read Replicas to restart. 
+  Fixed an issue that could cause longer downtime during upgrade from 1.23.\$1 to 2.09.\$1. 
+  Fixed an issue where a DDL or DML could cause engine restart during a page prefetch request. 
+  Fixed an issue that caused a binlog replica to stop with an error if the replicated transaction contains a DDL statement and a large number of row changes. 
+  Fixed an issue where a database acting as a binlog replica could restart while replicating a DDL event on the mysql `time_zone` table. 
+  Fixed an issue that could cause large transactions to generate incorrect binlog events if the `binlog_checksum` parameter was set to `NONE`. 
+  Fixed an issue that caused a binlog replica to stop with an `HA_ERR_KEY_NOT_FOUND` error. 
+  Improved overall stability. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2020-12-11 (version 2.09.1) (Deprecated)
Aurora MySQL updates: 2020-12-11 (version 2.09.1) (Deprecated)Aurora MySQL version 2.09.1

 Aurora MySQL version 2.09.1 is available. 

 **Version:** 2.09.1 

 Aurora MySQL 2.09.1 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6. 

 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 upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.09.1. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.09.1. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.09.1. 

 To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

 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**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


 **Security fixes:** 

 Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes below: 
+  [CVE-2020-14567](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14567) 
+  [CVE-2020-14559](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14559) 
+  [CVE-2020-14553](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14553) 
+  [CVE-2020-14547](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14547) 
+  [CVE-2020-14540](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14540) 
+  [CVE-2020-2812](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2812) 
+  [CVE-2020-2806](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2806) 
+  [CVE-2020-2780](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2780) 
+  [CVE-2020-2765](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2765) 
+  [CVE-2020-2763](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2763) 
+  [CVE-2020-2760](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2760) 
+  [CVE-2020-2579](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2579) 

 **Incompatible changes:** 

 This version introduces a permission change that affects the behavior of the `mysqldump` command. Users must have the `PROCESS` privilege to access the `INFORMATION_SCHEMA.FILES` table. To run the `mysqldump` command without any changes, grant the `PROCESS` privilege to the database user that the `mysqldump` command connects to. You can also run the `mysqldump` command with the `--no-tablespaces` option. With that option, the `mysqldump `output doesn't include any `CREATE LOGFILE GROUP` or `CREATE TABLESPACE` statements. In that case, the `mysqldump` command doesn't access the `INFORMATION_SCHEMA.FILES` table, and you don't need to grant the `PROCESS` permission. 

 **Availability improvements:** 
+  Fixed an issue that might cause a client session to hang when the database engine encounters an error while reading from or writing to the network. 
+  Fixed a memory leak in dynamic resizing feature, introduced in 2.09.0. 

 **Global databases:** 
+  Fixed multiple issues where a global database secondary Region's replicas might restart when upgraded to release 2.09.0 while the primary Region writer was on an older release version. 

## Integration of MySQL community edition bug fixes

+  **Replication:** Interleaved transactions could sometimes deadlock the slave applier when the transaction isolation level was set to [REPEATABLE READ](https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html#isolevel_repeatable-read). (Bug \$125040331) 
+  For a table having a [TIMESTAMP](https://dev.mysql.com/doc/refman/5.7/en/datetime.html) or [DATETIME](https://dev.mysql.com/doc/refman/5.7/en/datetime.html) column having a default of [CURRENT\$1TIMESTAMP](https://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html#function_current-timestamp), the column could be initialized to `0000-00-00 00:00:00` if the table had a `BEFORE INSERT` trigger. (Bug \$125209512, Bug \$184077) 
+  For an [INSERT](https://dev.mysql.com/doc/refman/5.7/en/insert.html) statement for which the `VALUES` list produced values for the second or later row using a subquery containing a join, the server could exit after failing to resolve the required privileges. (Bug \$123762382) 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2020-09-17 (version 2.09.0) (Deprecated)
Aurora MySQL updates: 2020-09-17 (version 2.09.0) (Deprecated)Aurora MySQL version 2.09.0

Aurora MySQL version 2.09.0 is available.

**Version:** 2.09.0

Aurora MySQL 2.09.0 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 Aurora MySQL 1.23.\$1 into Aurora MySQL 2.09.0. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.09.0. You can't upgrade an existing Aurora MySQL 1.23.\$1 cluster directly to 2.09.0; however, you can restore its snapshot to Aurora MySQL 2.09.0. 

**Important**  
 The improvements to Aurora storage in this version limit the available upgrade paths from Aurora MySQL 1.\$1 to Aurora MySQL 2.09. When you upgrade an Aurora MySQL 1.\$1 cluster to 2.09, you must upgrade from Aurora MySQL 1.23. 

 To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **New features:** 
+  With this release, you can create Amazon Aurora MySQL database instances with up to 128 tebibytes (TiB) of storage. The new storage limit is an increase from the prior 64 TiB. The 128 TiB storage size supports larger databases. This capability is not supported on small instances sizes (db.t2 or db.t3). A single tablespace cannot grow beyond 64 TiB due to [InnoDB limitations with 16 KB page size](https://dev.mysql.com/doc/refman/5.7/en/innodb-limits.html). 

   Aurora alerts you when the cluster volume size is near 128 TiB, so that you can take action prior to hitting the size limit. The alerts appear in the mysql log and RDS Events in the AWS Management Console. 
+  You can now turn parallel query on or off for an existing cluster by changing the value of the DB cluster parameter `aurora_parallel_query`. You don't need to use the `parallelquery` setting for the `--engine-mode` parameter when creating the cluster. 

   Parallel query is now expanded to be available in all regions where Aurora MySQL is available. 

   There are a number of other functionality enhancements and changes to the procedures for upgrading and enabling parallel query in an Aurora cluster. For more information, see [ Working with parallel query for Amazon Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-mysql-parallel-query.html) in the *Amazon Aurora User Guide*. 
+  Aurora dynamically resizes your cluster storage space. With dynamic resizing, the storage space for your Aurora DB cluster automatically decreases when you remove data from the DB cluster. For more information, see [ Storage scaling](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Managing.Performance.html#Aurora.Managing.Performance.StorageScaling) in the *Amazon Aurora User Guide*. 
**Note**  
 The dynamic resizing feature is being deployed in phases to the AWS Regions where Aurora is available. Depending on the Region where your cluster is, this feature might not be available yet. For more information, see [the What's New announcement](https://aws.amazon.com/about-aws/whats-new/2020/10/amazon-aurora-enables-dynamic-resizing-database-storage-space/). 

 **High priority fixes:** 
+  Backport of Community Bug \$127659490: SELECT USING DYNAMIC RANGE AND INDEX MERGE USE TOO MUCH MEMORY (OOM) 
+  Bug \$126881508: MYSQL \$11: DISABLE\$1ABORT\$1ON\$1ERROR IN AUTH\$1COMMON.H 
+  Backport of Community Bug \$124437124: POSSIBLE BUFFER OVERFLOW ON CREATE TABLE 
+  Backport of Bug \$127158030: INNODB ONLINE ALTER CRASHES WITH CONCURRENT DML 
+  Bug \$129770705: SERVER CRASHED WHILE EXECUTING SELECT WITH SPECIFIC WHERE CLAUSE 
+  Backport of BUG \$126502135: MYSQLD SEGFAULTS IN MDL\$1CONTEXT::TRY\$1ACQUIRE\$1LOCK\$1IMPL 
+  Backport of Bug \$126935001: ALTER TABLE AUTO\$1INCREMENT TRIES TO READ INDEX FROM DISCARDED TABLESPACE 
+  Bug \$128491099: [FATAL] MEMORY BLOCK IS INVALID \$1 INNODB: ASSERTION FAILURE: UT0UT.CC:670 
+  Bug \$130499288: GCC 9.2.1 REPORTS A NEW WARNING FOR OS\$1FILE\$1GET\$1PARENT\$1DIR 
+  Bug \$129952565 where MYSQLD GOT SIGNAL 11 WHILE EXECUTING A QUERY(UNION \$1 ORDER BY \$1 SUB-QUERY) 
+  Bug \$130628268: OUT OF MEMORY CRASH 
+  Bug \$130441969: BUG \$129723340: MYSQL SERVER CRASH AFTER SQL QUERY WITH DATA ?AST 
+  Bug \$130569003: 5.7 REPLICATION BREAKAGE WITH SYNTAX ERROR WITH GRANT MANAGEMENT 
+  Bug \$129915479: RUNNING COM\$1REGISTER\$1SLAVE WITHOUT COM\$1BINLOG\$1DUMP CAN RESULTS IN SERVER EXIT 
+  Bug \$130569003: 5.7 REPLICATION BREAKAGE WITH SYNTAX ERROR WITH GRANT MANAGEMENT 
+  Bug \$129915479: RUNNING COM\$1REGISTER\$1SLAVE WITHOUT COM\$1BINLOG\$1DUMP CAN RESULTS IN SERVER EXIT 
+  Bug \$120712046: SHOW PROCESSLIST AND PERFORMANCE\$1SCHEMA TABLES DO NOT MASK PASSWORD FROM QUERY 
+  Backport bug \$118898433: EXTREMELY SLOW PERFORMANCE WITH OUTER JOINS AND JOIN BUFFER (fixed in 5.7.21). Queries with many left joins were slow if join buffering was used (for example, using the block nested loop algorithm). (Bug \$118898433, Bug \$172854)" 
+  Backport bug \$126402045: MYSQLD CRASHES ON QUERY (fixed in MySQL 5.7.23). Certain cases of subquery materialization could cause a server exit. These queries now produce an error suggesting that materialization be disabled. (Bug \$126402045) 
+  [Backport from MySQL] users other than rdsadmin is disallowed to update pfs table in the reader replica. 
+  Fix the issue where the customer can not update the perfschema in the reader replica 
+  Bug \$126666274: INFINITE LOOP IN PERFORMANCE SCHEMA BUFFER CONTAINER 
+  [Bug \$126997096](https://github.com/mysql/mysql-server/commit/78f25d2809ad457e81f90342239c9bc32a36cdfa): relay\$1log\$1space value is not updated in a synchronized manner so that its value sometimes much higher than the actual disk space used by relay logs. 
+  BUG \$125082593: FOREIGN KEY VALIDATION DOESN'T NEED TO ACQUIRE GAP LOCK IN READ COMMITTED 
+ [CVE-2019-2731](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2731)
+ [CVE-2018-2645](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2645)
+ [CVE-2019-2581](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2581)
+ [CVE-2018-2787](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2787)
+ [CVE-2019-2482](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2482)
+ [CVE-2018-2640](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2640)
+ [CVE-2018-2784](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2784)
+ [CVE-2019-2628](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2628)
+ [CVE-2019-2911](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2911)
+ [CVE-2019-2628](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2628)
+ [CVE-2018-3284](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3284)
+ [CVE-2018-3065](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3065)
+ [CVE-2019-2537](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2537)
+ [CVE-2019-2948](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2948)
+ [CVE-2019-2434](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2434)
+ [CVE-2019-2420](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2420)

 **Availability improvements:** 
+  Enable lock manager ABA fix by default. 
+  Fixed an issue in the lock manager where a race condition can cause a lock to be shared by two transactions, causing the database to restart. 
+  Fixed an issue when creating a temporary table with compressed row format might result in a restart. 
+  Fix default value of `table_open_cache` on 16XL and 24XL instances which could cause repeated failovers and high CPU utilization on large instances classes (R4/R5-16XL, R5-12XL, R5-24XL). This impacted 2.07.x. 
+  Fixed an issue where restoring a cluster from Amazon S3 to Aurora MySQL version 2.08.0 takes longer than expected when the S3 backup didn't include the `mysql.host` table. 
+  Fixed an issue which might cause repeated failovers due to updates of virtual columns with secondary indexes. 
+  Fixed an issue related to transaction lock memory management with long-running write transactions resulting in a database restart. 
+  Fixed multiple issues where the engine might crash during zero-downtime patching while checking for safe point for patching. 
+  Fixed an issue to skip redo logging for temporary tables, which was previously causing a crash. 
+  Fixed a race condition in the lock manager between killing connection/query and the session killed. 
+  Fixed an issue where the database could crash if it is a binlog replica and receives a DDL event over the MySQL `time_zone` table. 

 **Global databases:** 
+  MySQL `INFORMATION_SCHEMA.REPLICA_HOST_STATUS` view in a secondary Region now shows the entries for the replicas belonging to that Region. 
+  Fixed unexpected query failures that could occur in a Global DB secondary Region after temporary network connectivity issues between the primary and secondary Regions. 
+  

 **Parallel query:** 
+  Fixed the `EXPLAIN` plan for a Parallel Query query, which is incorrect for a simple single-table query. 
+  Fixed self-deadlatch that may occur when Parallel Query is enabled. 

 **General improvements:** 
+  Export to S3 now supports the `ENCRYPTION` keyword. 
+  The `aurora_binlog_replication_max_yield_seconds` parameter now has a max value of 36,000. The previous maximum accepted value was 45. This parameter works only when the parameter `aurora_binlog_use_large_read_buffer` is set to 1. 
+  Changed the behavior to map `MIXED` `binlog_format` to `ROW` instead of `STATEMENT` when executing `LOAD DATA FROM INFILE | S3`. 
+  Fixed an issue where a binlog replica connected to an Aurora MySQL binlog primary might show incomplete data when the primary executed `LOAD DATA FROM S3` and `binlog_format` is set to `STATEMENT`. 
+  Increased maximum allowable length for audit system variables `server_audit_incl_users` and `server_audit_excl_users` from 1024 bytes to 2000 bytes. 
+  Fixed an issue where users may lose access to the database when lowering the `max_connections` parameter in the parameter group when the current connections is greater than the value being set. 
+  Fixed an issue in Data Activity Streams where a single quote and backslash were not escaped properly. 

## Integration of MySQL community edition bug fixes

+  Bug \$127659490: SELECT USING DYNAMIC RANGE AND INDEX MERGE USE TOO MUCH MEMORY(OOM) 
+  Bug \$126881508: MYSQL \$11: DISABLE\$1ABORT\$1ON\$1ERROR IN AUTH\$1COMMON.H 
+  Bug \$124437124: POSSIBLE BUFFER OVERFLOW ON CREATE TABLE 
+  Bug \$127158030: INNODB ONLINE ALTER CRASHES WITH CONCURRENT DML 
+  Bug \$129770705: SERVER CRASHED WHILE EXECUTING SELECT WITH SPECIFIC WHERE CLAUSE 
+  Bug \$126502135: MYSQLD SEGFAULTS IN MDL\$1CONTEXT::TRY\$1ACQUIRE\$1LOCK\$1IMPL 
+  Bug \$126935001: ALTER TABLE AUTO\$1INCREMENT TRIES TO READ INDEX FROM DISCARDED TABLESPACE 
+  Bug \$128491099: [FATAL] MEMORY BLOCK IS INVALID \$1 INNODB: ASSERTION FAILURE: UT0UT.CC:670 
+  Bug \$130499288: GCC 9.2.1 REPORTS A NEW WARNING FOR OS\$1FILE\$1GET\$1PARENT\$1DIR 
+  Bug \$129952565: where MYSQLD GOT SIGNAL 11 WHILE EXECUTING A QUERY(UNION \$1 ORDER BY \$1 SUB-QUERY) 
+  Bug \$130628268: OUT OF MEMORY CRASH 
+  Bug \$130441969: BUG \$129723340: MYSQL SERVER CRASH AFTER SQL QUERY WITH DATA ?AST 
+  Bug \$130569003: 5.7 REPLICATION BREAKAGE WITH SYNTAX ERROR WITH GRANT MANAGEMENT 
+  Bug \$129915479: RUNNING COM\$1REGISTER\$1SLAVE WITHOUT COM\$1BINLOG\$1DUMP CAN RESULTS IN SERVER EXIT 
+  Bug \$130569003: 5.7 REPLICATION BREAKAGE WITH SYNTAX ERROR WITH GRANT MANAGEMENT 
+  Bug \$129915479: RUNNING COM\$1REGISTER\$1SLAVE WITHOUT COM\$1BINLOG\$1DUMP CAN RESULTS IN SERVER EXIT 
+  Bug \$120712046: SHOW PROCESSLIST AND PERFORMANCE\$1SCHEMA TABLES DO NOT MASK PASSWORD FROM QUERY 
+  Bug \$118898433: EXTREMELY SLOW PERFORMANCE WITH OUTER JOINS AND JOIN BUFFER (fixed in 5.7.21) 
+  Bug \$126402045: MYSQLD CRASHES ON QUERY (fixed in MySQL 5.7.23) 
+  Bug \$123103937: PS\$1TRUNCATE\$1ALL\$1TABLES() DOES NOT WORK IN SUPER\$1READ\$1ONLY MODE 
+  Bug \$126666274: INFINITE LOOP IN PERFORMANCE SCHEMA BUFFER CONTAINER 
+  Bug \$126997096: relay\$1log\$1space value is not updated in a synchronized manner so that its value sometimes much higher than the actual disk space used by relay logs. ([https://github.com/mysql/mysql-server/commit/78f25d2809ad457e81f90342239c9bc32a36cdfa](https://github.com/mysql/mysql-server/commit/78f25d2809ad457e81f90342239c9bc32a36cdfa)) 
+  Bug \$125082593: FOREIGN KEY VALIDATION DOESN'T NEED TO ACQUIRE GAP LOCK IN READ COMMITTED 
+  Bug \$124764800: REPLICATION FAILING ON SLAVE WITH XAER\$1RMFAIL ERROR. 
+  Bug \$181441: WARNING ABOUT LOCALHOST WHEN USING SKIP-NAME-RESOLVE. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2022-01-06 (version 2.08.4) (Deprecated)
Aurora MySQL updates: 2022-01-06 (version 2.08.4) (Deprecated)Aurora MySQL version 2.08.4

Aurora MySQL version 2.08.4 is available.

**Version:** 2.08.4

Aurora MySQL 2.08.4 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 upgrade an existing Aurora MySQL 2.\$1 database cluster to Aurora MySQL 2.10.0. For clusters running Aurora MySQL version 1, you can upgrade an existing Aurora MySQL 1.23 or higher cluster directly to 2.10.0. You can also restore a snapshot from any currently supported Aurora MySQL release into Aurora MySQL 2.10.0. 

 To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the Amazon RDS API. 

 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**  
 For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*. 

## Improvements


 **Security fixes and general improvements:** 
+ Fixed security issues related to Aurora MySQL integration with other AWS Services such as Amazon S3, Amazon ML, and AWS Lambda.
+ Fixed an issue where the value of a TIMESTAMP column of an existing row is updated to the latest timestamp when all of the following conditions are satisfied: 1. a trigger exists for the table; 2. an INSERT is performed on the table that has an ON DUPLICATE KEY UPDATE clause; 3. the inserted row can cause a duplicate value violation in a UNIQUE index or PRIMARY KEY; and 4. one or more columns are of TIMESTAMP data type and have a default value of CURRENT\$1TIMESTAMP.
+ Fixed an issue which, in rare conditions, causes a writer instance to restart when an in-memory data-integrity check fails.
+ Fixed an issue with parallel query which could cause the database to restart when executing SQL statements with a LIMIT clause.

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2020-11-12 (version 2.08.3) (Deprecated)
Aurora MySQL updates: 2020-11-12 (version 2.08.3) (Deprecated)Aurora MySQL version 2.08.3

Aurora MySQL version 2.08.3 is available.

**Version:** 2.08.3

Aurora MySQL 2.08.3 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 upgrade existing Aurora MySQL 2.\$1 database clusters directly to Aurora MySQL 2.08.3. You can upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.07.3 or higher and then directly upgrade to 2.08.3. 

 To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **Security fixes:** 

 Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes below: 
+ [CVE-2020-14567](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14567)
+ [CVE-2020-14559](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14559)
+ [CVE-2020-14553](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14553)
+ [CVE-2020-14547](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14547)
+ [CVE-2020-14540](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14540)
+ [CVE-2020-2812](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2812)
+ [CVE-2020-2806](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2806)
+ [CVE-2020-2780](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2780)
+ [CVE-2020-2765](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2765)
+ [CVE-2020-2763](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2763)
+ [CVE-2020-2760](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2760)
+ [CVE-2020-2579](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2579)

 **Incompatible changes:** 

 This version introduces a permission change that affects the behavior of the `mysqldump` command. Users must have the `PROCESS` privilege to access the `INFORMATION_SCHEMA.FILES` table. To run the `mysqldump` command without any changes, grant the `PROCESS` privilege to the database user that the `mysqldump` command connects to. You can also run the `mysqldump` command with the `--no-tablespaces` option. With that option, the `mysqldump `output doesn't include any `CREATE LOGFILE GROUP` or `CREATE TABLESPACE` statements. In that case, the `mysqldump` command doesn't access the `INFORMATION_SCHEMA.FILES` table, and you don't need to grant the `PROCESS` permission. 

## Integration of MySQL community edition bug fixes

+  Bug \$123762382 - INSERT VALUES QUERY WITH JOIN IN A SELECT CAUSES INCORRECT BEHAVIOR. 
+  Bug \$125209512 - CURRENT\$1TIMESTAMP PRODUCES ZEROS IN TRIGGER. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2020-08-28 (version 2.08.2) (Deprecated)
Aurora MySQL updates: 2020-08-28 (version 2.08.2) (Deprecated)Aurora MySQL version 2.08.2

Aurora MySQL version 2.08.2 is available.

**Version:** 2.08.2

Aurora MySQL 2.08.2 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.08.2. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.08.2. You can't upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.08.2; however, you can restore its snapshot to Aurora MySQL 2.08.2. For more information about restoring snapshots, see [ Restoring from a DB cluster snapshot](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_RestoreFromSnapshot.html) in the *Amazon Aurora User Guide*. 

 To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **Critical fixes:** 
+  Fixed an issue that might cause an unplanned outage and affect database availability. 

 **Availability fixes:** 
+ Fixed an issue where the Aurora MySQL database could restart if it is a binlog replica and replicates a DDL event over the mysql `time_zone` table. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2020-06-18 (version 2.08.1) (Deprecated)
Aurora MySQL updates: 2020-06-18 (version 2.08.1) (Deprecated)Aurora MySQL version 2.08.1

Aurora MySQL version 2.08.1 is available.

**Version:** 2.08.1

Aurora MySQL 2.08.1 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.08.1. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.08.1. You can't upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.08.1; however, you can restore its snapshot to Aurora MySQL 2.08.1. 

 To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **New features:** 
+  Global database write forwarding. In an Aurora global database, now you can perform certain write operations, such as DML statements, while connected to a secondary cluster. The write operations are forwarded to the primary cluster, and any changes are replicated back to the secondary clusters. For more information, see [ Using write forwarding in an Amazon Aurora global database](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-global-database-write-forwarding.html) in the *Amazon Aurora User Guide*. 

 **General stability fixes:** 
+  Fixed an issue where restoring a cluster from Amazon S3 to Aurora MySQL version 2.08.0 took longer than expected if the S3 backup didn't include the `mysql.host` table. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2020-06-02 (version 2.08.0) (Deprecated)
Aurora MySQL updates: 2020-06-02 (version 2.08.0) (Deprecated)Aurora MySQL version 2.08.0

Aurora MySQL version 2.08.0 is available.

**Version:** 2.08.0

Aurora MySQL 2.08.0 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.08.0. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.08.0. You can't upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.08.0; however, you can restore its snapshot to Aurora MySQL 2.08.0. 

 To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **New features:** 
+  Improved binary log (binlog) processing to reduce crash recovery time and commit time latency when very large transactions are involved. 
+  Launching Database Activity Streams (DAS) feature for Aurora MySQL. This feature provides a near-real-time data stream of the database activity in your relational database to help you monitor activity. For more information, see [ Monitoring Amazon Aurora with Database Activity Streams](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/DBActivityStreams.html) in the *Amazon Aurora User Guide*.
+  Updated timezone files to support the latest Brazil timezone change. 
+  Introduced new keywords in SQL to exercise the hash join functionality for a specific table and/or inner table: `HASH_JOIN`, `HASH_JOIN_PROBING`, and `HASH_JOIN_BUILDING`. For additional details, see [ Aurora MySQL hints](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.html#AuroraMySQL.Reference.Hints) in the *Amazon Aurora User Guide*. 
+  Introduced join order hint support in Aurora MySQL 5.7 by backporting [a MySQL 8.0 feature](https://github.com/mysql/mysql-server/commit/d2d91c3286b9ac3b95ef0e5036c5319aa4ffeda2#diff-4d30ba39ad1958c6f8148f67c94a896b). The new hints are `JOIN_FIXED_ORDER`, `JOIN_ORDER`, `JOIN_PREFIX`, and `JOIN_SUFFIX`. For detailed documentation of join order hint support, see [WL\$19158: Join order hints](https://dev.mysql.com/worklog/task/?id=9158). 
+  Aurora Machine Learning now supports user-defined functions with `MEDIUMINT` as the return type. 
+  The `lambda_async()` stored procedure now supports all MySQL `utf8` characters. 

 **High priority fixes:** 
+  Fixed an issue that could cause a reader DB instance to return incomplete results for an FTS query after the `INFORMATION_SCHEMA.INNODB_SYS_TABLES` table is queried on the writer DB instance. 
+ [CVE-2019-5443](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5443)
+ [CVE-2019-3822](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3822)

 **Availability improvements:** 
+  Fixed an issue that resulted in a database restart after a multi-query statement that accesses multiple tables or databases is executed with the query cache enabled. 
+  Fixed a race condition in the lock manager that resulted in a database restart or failover during transaction rollback. 
+  Fixed an issue that triggered database restart or failover when multiple connections are trying to update the same table with a Full-Text Search index. 
+  Fixed an issue that could trigger a database restart or failover during a `kill session` command. If you encounter this issue, contact AWS support to enable this fix on your instance. 
+  Fixed an issue that caused reader DB instance to restart during a multi-statement transaction with multiple `SELECT` statements and a heavy write workload on the writer DB instance with `AUTOCOMMIT` enabled. 
+  Fixed an issue that caused reader DB instance to restart after executing long-running queries while the writer DB instance is under a heavy OLTP write workload. 

 **General improvements:** 
+  Improved database recovery time and commit latency for long running transactions when binlog is enabled. 
+  Improved the algorithm to generate better statistics for estimating distinct value counts on indexed columns, including columns with skewed data distributions. 
+  Reduced the response time and CPU utilization of join queries that access MyISAM temporary tables and the results spill to local storage. 
+  Fixed an issue that prevented Aurora MySQL 5.6 snapshots with database or table names containing spaces from being restored to a new Aurora MySQL 5.7 cluster. 
+  Included victim transaction info when deadlock is resolved in `show engine innodb status`. 
+  Fixed an issue that caused connections to get stuck when clients of multiple different versions are connected to the same database and are accessing the query cache. 
+  Fixed a memory leak resulting from multiple invocations of the Zero-Downtime Patch (ZDP) or Zero-Downtime Restart (ZDR) workflow throughout the lifetime of a database instance. 
+  Fixed an error message in Zero-Downtime Patch (ZDP) or Zero-Downtime Restart (ZDR) operations wrongly stating that the last transaction was aborted if the auto-commit flag is turned off. 
+  Fixed an issue in Zero-Downtime Patch (ZDP) operations that could lead to a server failure error message when restoring user session variables in the new database process. 
+  Fixed an issue in Zero Downtime Patch (ZDP) operations that might cause intermittent database failures when there are long running queries during patching. 
+  Fixed an issue where queries including an Aurora Machine Learning function returned empty error messages due to an incorrectly handled error response from Machine Learning services such as Amazon SageMaker AI and Amazon Comprehend. 
+  Fixed an issue in the out-of-memory monitoring functionality that did not honor a custom value of the `table_definition_cache` parameter. 
+  The error message "Query execution was interrupted" is returned if an Aurora Machine Learning query is interrupted. Previously, the generic message "Internal error in processing ML request" was returned instead. 
+  Fixed an issue that could cause a binlog worker to experience a connection timeout when the `slave_net_timeout` parameter is less than the `aurora_binlog_replication_max_yield_seconds` parameter and there is low workload on the binlog master cluster. 
+  Improved monitoring of the binlog recovery progress by outputting informational messages in the error log at a frequency of one message per minute. 
+  Fixed an issue that could cause active transactions not to be reported by the `SHOW ENGINE INNODB STATUS` query. 

## Integration of MySQL community edition bug fixes

+  [Bug \$125289359](https://github.com/mysql/mysql-server/commit/64161c9abd50de7ba0b542bd4895881f6ead6531): A full-text cache lock taken when data is synchronized was not released if the full-text cache size exceeded the full-text cache size limit. 
+  [Bug \$129138644](https://github.com/mysql/mysql-server/commit/fbfd9fcd32afc11ba77d52fa0690aa26dcd64f72): Manually changing the system time while the MySQL server was running caused page cleaner thread delays. 
+  [Bug \$125222337](https://github.com/mysql/mysql-server/commit/273d5c9d7072c63b6c47dbef6963d7dc491d5131): A NULL virtual column field name in a virtual index caused a server exit during a field name comparison that occurs while populating virtual columns affected by a foreign key constraint. 
+  [Bug \$125053286](https://github.com/mysql/mysql-server/commit/d7b37d4d141a95f577916448650c429f0d6e193d): Executing a stored procedure containing a query that accessed a view could allocate memory that was not freed until the session ended. 
+  [Bug \$125586773](https://github.com/mysql/mysql-server/commit/88301e5adab65f6750f66af284be410c4369d0c1): Executing a stored procedure containing a statement that created a table from the contents of certain [SELECT](https://dev.mysql.com/doc/refman/5.7/en/select.html) statements could result in a memory leak. 
+  [Bug \$128834208](https://github.com/mysql/mysql-server/commit/ca722bbb409209d683534846a90093c118bf8c5b): During log application, after an [OPTIMIZE TABLE](https://dev.mysql.com/doc/refman/5.7/en/optimize-table.html) operation, InnoDB did not populate virtual columns before checking for virtual column index updates. 
+  [Bug \$126666274](https://github.com/mysql/mysql-server/commit/bd87573bc159c849f34aa8293ec43ac053cbfda0): Infinite loop in performance schema buffer container due to 32-bit unsigned integer overflow. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2023-08-15 (version 2.07.10) (Deprecated)
Aurora MySQL updates: 2023-08-15 (version 2.07.10) (Deprecated)[Aurora MySQL version 2.07.10, compatible with MySQL 5.7.12](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.20710.html)

Aurora MySQL version 2.07.10 is available. This version is compatible with MySQL 5.7.12. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html).

**Version:** 2.07.10

Aurora MySQL 2.07.10 is generally available. Aurora MySQL 2.07 versions are compatible with MySQL 5.7.12. For more information on community changes, see [Changes in MySQL 5.7.12 (2016-04-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.html).

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

 You can restore a snapshot from a currently supported Aurora MySQL release into Aurora MySQL 2.07.10. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.07.10. In-place upgrade is available for Aurora MySQL 1.\$1 clusters to Aurora MySQL 2.\$1 (see [ Upgrading from Aurora MySQL 1.x to 2.x](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Updates.MajorVersionUpgrade.1to2)). It's also available for Aurora MySQL 2.\$1 clusters to Aurora MySQL 3.\$1 (see [ Upgrading from Aurora MySQL 2.x to 3.x](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Updates.MajorVersionUpgrade.2to3)). 

Immediately after an in-place engine version upgrade to Aurora MySQL 2.07.10 is performed, an operating system upgrade is applied automatically to all of the affected instances on the db.r4, db.r5, db.t2, and db.t3 DB instance classes, if the instances are running an old operating system version. In a Multi-AZ DB cluster, all of the reader instances apply the operating system upgrade first. When the operating system upgrade on the first reader instance is finished, a failover occurs and the previous writer instance is upgraded.

**Note**  
The operating system upgrade isn't applied automatically to Aurora global databases during major version upgrades.

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*.

For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


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

 Fixes and other enhancements to fine-tune handling in a managed environment. Additional CVE fixes below: 
+ [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)
+ Fixed an issue where events that were reported while processing audit log rotations might not be written to the audit log.
+ Updated the default SSL ciphers used by Aurora MySQL to exclude the less secure DES-CBC3-SHA values from the [SSL\$1CIPHER](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_ssl_cipher) database parameter. If you encounter SSL connection issues due to the removal of the DES-CBC3-SHA cipher, please use an applicable secure cipher from the following information, [Configuring cipher suites for connections to Aurora MySQL DB clusters](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Security.html#AuroraMySQL.Security.SSL.ConfiguringCipherSuites).
+ OpenSSL was upgraded to version 1.0.2zh.

 **General improvements:** 
+ Added support for ECDHE-RSA SSL ciphers that use smaller key sizes for encryption.
+ Fixed a memory management issue when executing queries with hash joins.

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP).
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ The `CREATE TABLESPACE` SQL statement
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ X Protocol

# Aurora MySQL database engine updates 2023-05-04 (version 2.07.9) (Deprecated)
Aurora MySQL updates: 2023-05-04 (version 2.07.9) (Deprecated)[Aurora MySQL version 2.07.9, compatible with MySQL 5.7.12.](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.2079.html)

Aurora MySQL version 2.07.9 is available. This version is compatible with MySQL 5.7.12. For full details, see [Aurora MySQL version 2 compatible with MySQL 5.7](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.CompareMySQL57.html).

**Version:** 2.07.9

Aurora MySQL 2.07.9 is generally available. Aurora MySQL 2.07 versions are compatible with MySQL 5.7.12. For more information on community changes, see [Changes in MySQL 5.7.12 (2016-04-11, General Availability)](https://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-12.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 restore a snapshot from a currently supported Aurora MySQL release into Aurora MySQL 2.07.9. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.07.9. In-place upgrade is available for Aurora MySQL 1.\$1 clusters to Aurora MySQL 2.\$1 (see [ Upgrading from Aurora MySQL 1.x to 2.x](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Updates.MajorVersionUpgrade.1to2)). It's also available for Aurora MySQL 2.\$1 clusters to Aurora MySQL 3.\$1 (see [ Upgrading from Aurora MySQL 2.x to 3.x](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Updates.MajorVersionUpgrade.2to3)). 

Immediately after an in-place engine version upgrade to Aurora MySQL 2.07.9 is performed, an operating system upgrade is applied automatically to all of the affected instances on the db.r4, db.r5, db.t2, and db.t3 DB instance classes, if the instances are running an old operating system version. In a Multi-AZ DB cluster, all of the reader instances apply the operating system upgrade first. When the operating system upgrade on the first reader instance is finished, a failover occurs and the previous writer instance is upgraded.

**Note**  
The operating system upgrade isn't applied automatically to Aurora global databases during major version upgrades.

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*.

For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **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)

 **Availability improvements:** 
+ Fixed an issue where the Advanced Audit log rotation may reduce the freeable memory, which could lead to the DB instance restarting.
+ Fixed an issue which can occur during database restarts and results in the database not starting up successfully for an extended duration.

 **General improvements:** 
+ Fixed an issue which, in rare conditions, can cause the instances to restart when the database volume grows to a multiple of 160GB.

## Features not supported in Aurora MySQL version 2


The following features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP).
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2022-06-16 (version 2.07.8) (Deprecated)
Aurora MySQL updates: 2022-06-16 (version 2.07.8) (Deprecated)[Aurora MySQL database engine updates 2022-06-16 (version 2.07.8)](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.2078.html) is available.

Aurora MySQL version 2.07.8 is available.

**Version:** 2.07.8

Aurora MySQL 2.07.8 is generally available. Aurora MySQL 2.\$1 versions are compatible with MySQL 5.7 and Aurora MySQL 1.\$1 versions are compatible with MySQL 5.6.

**Note**  <a name="lts_notice_2078"></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.Updates.Versions.html#AuroraMySQL.Updates.LTS) 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 a currently supported Aurora MySQL release into Aurora MySQL 2.07.8. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.07.8. In-place upgrade is available for Aurora MySQL 1.\$1 clusters to Aurora MySQL 2.\$1 (see [ Upgrading from Aurora MySQL 1.x to 2.x](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Updates.MajorVersionUpgrade.1to2)). It's also available for Aurora MySQL 2.\$1 clusters to Aurora MySQL 3.\$1 (see [ Upgrading from Aurora MySQL 2.x to 3.x](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Updates.MajorVersionUpgrade.2to3)). 

 To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **Security fixes:** 

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

 **General improvements:** 
+ Fixed an issue which, in rare cases, causes the database server to restart when the deadlock detector thread gets stuck because of a race condition.

## Integration of MySQL community edition bug fixes

+  When an UPDATE required a temporary table having a primary key larger than 1024 bytes and that table was created using InnoDB, the server could exit. (Bug \$125153670) 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2021-11-24 (version 2.07.7) (Deprecated)
Aurora MySQL updates: 2021-11-24 (version 2.07.7) (Deprecated)Aurora MySQL version 2.07.7

Aurora MySQL version 2.07.7 is available.

**Version:** 2.07.7

Aurora MySQL 2.07.7 is generally available. Aurora MySQL 2.\$1 versions are compatible with MySQL 5.7 and Aurora MySQL 1.\$1 versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.07.7. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.07.7. You can't upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.07.7; however, you can restore its snapshot to Aurora MySQL 2.07.7. 

 To create a cluster with an older version of Aurora MySQL, specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **Security fixes:** 

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

 **General improvements:** 
+ Fixed security issues related to Aurora MySQL integration with other AWS Services such as Amazon S3, Amazon ML, Lambda.
+ Fixed an issue with incorrect reporting of an Aurora replication lag.
+ Fixed an issue which can cause a database instance restart to fail when the database has a large number of user and privilege combinations.
+ Fixed an issue which can cause general\$1log and slow\$1log tables to become inaccessible after in-place major version upgrade from Aurora MySQL 1.x (based on MySQL 5.6) to Aurora MySQL 2.x (based on MySQL 5.7).
+ Fixed an issue which, in rare conditions, can cause a reader instance to restart due to an incorrect check processing.
+ Fixed an issue which, in rare conditions, shows the "Database Load" chart in Performance Insights (PI) sessions as actively using CPU even though the sessions have finished processing and are idle.
+ Fixed an issue with parallel query which can cause the database to restart when executing SQL statements with a LIMIT clause.
+ Fixed an issue where the value of a TIMESTAMP column of an existing row is updated to the latest timestamp when all of the following conditions are satisfied: 1. A trigger exists for the table; 2. an INSERT is performed on the table that has an ON DUPLICATE KEY UPDATE clause; 3. the inserted row can cause a duplicate value violation in a UNIQUE index or PRIMARY KEY; and, 4. one or more columns are of TIMESTAMP data type and have a default value of CURRENT\$1TIMESTAMP.
+ Fixed an issue which, in rare conditions, can cause the database instance to restart when using XA transactions in READ COMMITTED isolation level.

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2021-09-02 (version 2.07.6) (Deprecated)
Aurora MySQL updates: 2021-09-02 (version 2.07.6) (Deprecated)Aurora MySQL version 2.07.6

Aurora MySQL version 2.07.6 is available.

**Version:** 2.07.6

Aurora MySQL 2.07.6 is generally available. Aurora MySQL 2.\$1 versions are compatible with MySQL 5.7 and Aurora MySQL 1.\$1 versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.07.6. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.07.6. You can't upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.07.6; however, you can restore its snapshot to Aurora MySQL 2.07.6. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

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*.

## Integration of MySQL community edition bug fixes

+  INSERTING 64K SIZE RECORDS TAKE TOO MUCH TIME. ([Bug\$123031146](https://github.com/mysql/mysql-server/commit/a2f9ea422e4bdfd65da6dd0c497dc233629ec52e)) 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2021-07-06 (version 2.07.5) (Deprecated)
Aurora MySQL updates: 2021-07-06 (version 2.07.5) (Deprecated)Aurora MySQL version 2.07.5

Aurora MySQL version 2.07.5 is available.

**Version:** 2.07.5

Aurora MySQL 2.07.5 is generally available. Aurora MySQL 2.\$1 versions are compatible with MySQL 5.7 and Aurora MySQL 1.\$1 versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.07.5. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.07.5. You can't upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.07.5; however, you can restore its snapshot to Aurora MySQL 2.07.5. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

**Note**  <a name="lts_notice_2075"></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.Updates.Versions.html#AuroraMySQL.Updates.LTS) 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


 **Availability improvements:** 
+  Fixed an issue that user-level locks are not allowed on an Aurora Replica. 
+  Fixed an issue that could cause a restart of a database when using XA transactions in `READ COMMITTED` isolation level. 
+  Extended maximum allowable length to 2000 for the `server_audit_incl_users` and `server_audit_excl_users` global parameters. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2021-03-04 (version 2.07.4) (Deprecated)
Aurora MySQL updates: 2021-03-04 (version 2.07.4) (Deprecated)Aurora MySQL version 2.07.4

Aurora MySQL version 2.07.4 is available.

**Version:** 2.07.4

Aurora MySQL 2.07.4 is generally available. Aurora MySQL 2.\$1 versions are compatible with MySQL 5.7 and Aurora MySQL 1.\$1 versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.07.4. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.07.4. You can't upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.07.4; however, you can restore its snapshot to Aurora MySQL 2.07.4. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

**Note**  <a name="lts_notice_2074"></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.Updates.Versions.html#AuroraMySQL.Updates.LTS) 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


 **Security fixes:** 
+ [CVE-2020-14812](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14812)
+ [CVE-2020-14793](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14793)
+ [CVE-2020-14790](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14790)
+ [CVE-2020-14775](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14775)
+ [CVE-2020-14769](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14769)
+ [CVE-2020-14765](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14765)
+ [CVE-2020-14760](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14760)
+ [CVE-2020-14672](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14672)
+ [CVE-2020-1971](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-1971)

 **Availability improvements:** 
+  Fixed an issue that could cause a client to hang in case of a network error while reading or writing a network packet. 
+  Improved engine restart times in some cases after interrupted DDL. 
+  Fixed an issue where a DDL or DML could cause engine restart during a page prefetch request. 
+  Fixed an issue where a replica could restart while performing a reverse scan of a table/index on an Aurora Read Replica. 
+  Fixed an issue in clone cluster operation that could cause the clone to take longer. 
+  Fixed an issue that could cause a restart of a database when using parallel query optimization for geospatial columns. 
+  Fixed an issue that caused a binlog replica to stop with an `HA_ERR_KEY_NOT_FOUND` error. 

## Integration of MySQL community edition bug fixes

+  Fixed an issue in the Full-text ngram parser when dealing with tokens containing ' ' (space), '%', or ','. Customers should rebuild their FTS indexes if using ngram parser. (Bug \$125873310) 
+  Fixed an issue that could cause engine restart during query execution with nested SQL views. (Bug \$127214153, Bug \$126864199) 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2020-11-10 (version 2.07.3) (Deprecated)
Aurora MySQL updates: 2020-11-10 (version 2.07.3) (Deprecated)Aurora MySQL version 2.07.3

Aurora MySQL version 2.07.3 is available.

**Version:** 2.07.3

Aurora MySQL 2.07.3 is generally available. Aurora MySQL 2.\$1 versions are compatible with MySQL 5.7 and Aurora MySQL 1.\$1 versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.07.3. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.07.3. You can't upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.07.3; however, you can restore its snapshot to Aurora MySQL 2.07.3. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

**Note**  <a name="lts_notice_2073"></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.Updates.Versions.html#AuroraMySQL.Updates.LTS) 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


 **Security fixes:** 

 Fixes and other enhancements to fine-tune handling in a managed environment. 
+ [CVE-2021-2144](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-2144)
+ [CVE-2020-14567](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14567)
+ [CVE-2020-14559](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14559)
+ [CVE-2020-14553](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14553)
+ [CVE-2020-14547](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14547)
+ [CVE-2020-14540](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14540)
+ [CVE-2020-2812](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2812)
+ [CVE-2020-2806](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2806)
+ [CVE-2020-2780](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2780)
+ [CVE-2020-2765](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2765)
+ [CVE-2020-2763](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2763)
+ [CVE-2020-2760](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2760)
+ [CVE-2020-2579](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2579)
+ [CVE-2019-2740](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2740)

 **Incompatible changes:** 

 This version introduces a permission change that affects the behavior of the `mysqldump` command. Users must have the `PROCESS` privilege to access the `INFORMATION_SCHEMA.FILES` table. To run the `mysqldump` command without any changes, grant the `PROCESS` privilege to the database user that the `mysqldump` command connects to. You can also run the `mysqldump` command with the `--no-tablespaces` option. With that option, the `mysqldump `output doesn't include any `CREATE LOGFILE GROUP` or `CREATE TABLESPACE` statements. In that case, the `mysqldump` command doesn't access the `INFORMATION_SCHEMA.FILES` table, and you don't need to grant the `PROCESS` permission. 

 **Availability improvements:** 
+  Fixed a race condition in the lock manager between the killing of a connection/query and the termination of the session resulting in a database restart. 
+  Fixed an issue that results in a database restart after a multi-query statement that accesses multiple tables or databases is executed with the query cache enabled. 
+  Fixed an issue that might cause repeated restarts due to updates of virtual columns with secondary indexes. 

## Integration of MySQL community edition bug fixes

+  *InnoDB:* Concurrent XA transactions that ran successfully to the XA prepare stage on the master conflicted when replayed on the slave, resulting in a lock wait timeout in the applier thread. The conflict was due to the GAP lock range which differed when the transactions were replayed serially on the slave. To prevent this type of conflict, GAP locks taken by XA transactions in [READ COMMITTED](https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html#isolevel_read-committed) isolation level are now released (and no longer inherited) when XA transactions reach the prepare stage. (Bug \$127189701, Bug \$125866046) 
+  *InnoDB:* A gap lock was taken unnecessarily during foreign key validation while using the [READ COMMITTED](https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html#isolevel_read-committed) isolation level. (Bug \$125082593) 
+  *Replication:* When using XA transactions, if a lock wait timeout or deadlock occurred for the applier (SQL) thread on a replication slave, the automatic retry did not work. The cause was that while the SQL thread would do a rollback, it would not roll the XA transaction back. This meant that when the transaction was retried, the first event was XA START which was invalid as the XA transaction was already in progress, leading to an XAER\$1RMFAIL error. (Bug \$124764800) 
+  *Replication:* Interleaved transactions could sometimes deadlock the slave applier when the transaction isolation level was set to [REPEATABLE READ](https://dev.mysql.com/doc/refman/5.7/en/innodb-transaction-isolation-levels.html#isolevel_repeatable-read). (Bug \$125040331) 
+  *Replication:* The value returned by a [SHOW SLAVE STATUS](https://dev.mysql.com/doc/refman/5.7/en/show-slave-status.html) statement for the total combined size of all existing relay log files (Relay\$1Log\$1Space) could become much larger than the actual disk space used by the relay log files. The I/O thread did not lock the variable while it updated the value, so the SQL thread could automatically delete a relay log file and write a reduced value before the I/O thread finished updating the value. The I/O thread then wrote its original size calculation, ignoring the SQL thread's update and so adding back the space for the deleted file. The Relay\$1Log\$1Space value is now locked during updates to prevent concurrent updates and ensure an accurate calculation. (Bug \$126997096, Bug \$187832) 
+  For an [INSERT](https://dev.mysql.com/doc/refman/5.7/en/insert.html) statement for which the VALUES list produced values for the second or later row using a subquery containing a join, the server could exit after failing to resolve the required privileges. (Bug \$123762382) 
+  For a table having a [TIMESTAMP](https://dev.mysql.com/doc/refman/5.7/en/datetime.html) or [DATETIME](https://dev.mysql.com/doc/refman/5.7/en/datetime.html) column having a default of [CURRENT\$1TIMESTAMP](https://dev.mysql.com/doc/refman/5.7/en/date-and-time-functions.html#function_current-timestamp), the column could be initialized to `0000-00-00 00:00:00` if the table had a `BEFORE INSERT` trigger. (Bug \$125209512, Bug \$184077) 
+  A server exit could result from simultaneous attempts by multiple threads to register and deregister metadata Performance Schema objects. (Bug \$126502135) 
+  Executing a stored procedure containing a statement that created a table from the contents of certain [SELECT](https://dev.mysql.com/doc/refman/5.7/en/select.html) statements could result in a memory leak. (Bug \$125586773) 
+  Executing a stored procedure containing a query that accessed a view could allocate memory that was not freed until the session ended. (Bug \$125053286) 
+  Certain cases of subquery materialization could cause a server exit. These queries now produce an error suggesting that materialization be disabled. (Bug \$126402045) 
+  Queries with many left joins were slow if join buffering was used (for example, using the block nested loop algorithm). (Bug \$118898433, Bug \$172854) 
+  The optimizer skipped the second column in a composite index when executing an inner join with a `LIKE` clause against the second column. (Bug \$128086754) 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2020-04-17 (version 2.07.2) (Deprecated)
Aurora MySQL updates: 2020-04-17 (version 2.07.2) (Deprecated)Aurora MySQL version 2.07.2

Aurora MySQL version 2.07.2 is available.

**Version:** 2.07.2

Aurora MySQL 2.07.2 is generally available. Aurora MySQL 2.\$1 versions are compatible with MySQL 5.7 and Aurora MySQL 1.\$1 versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.07.2. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.07.2. You can't upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.07.2; however, you can restore its snapshot to Aurora MySQL 2.07.2. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

**Note**  
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.Updates.Versions.html#AuroraMySQL.Updates.LTS) 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


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

 **High priority fixes:** 
+  Fixed an issue that caused cloning to take longer on some database clusters with high write loads. 
+  Fixed an issue that could cause queries on a reader DB instance with execution plans using secondary indexes to return uncommitted data. The issue is limited to data affected by data manipulation language (DML) operations that modify primary or secondary index key columns. 

 **General improvements:** 
+  Fixed an issue that resulted in a slow restore of an Aurora 1.x DB cluster containing FTS (Full Text Search) indexes to an Aurora 2.x DB cluster. 
+  Fixed an issue that caused slower restores of an Aurora 1.x database snapshot containing partitioned tables with special characters in table names to an Aurora 2.x DB cluster. 
+  Fixed an issue that caused errors when querying slow query logs and general logs in reader DB instances. 

## Integration of MySQL community edition bug fixes

+  Bug \$123104498: Fixed an issue in Performance Schema in reporting total memory used. ([https://github.com/mysql/mysql-server/commit/20b6840df5452f47313c6f9a6ca075bfbc00a96b](https://github.com/mysql/mysql-server/commit/20b6840df5452f47313c6f9a6ca075bfbc00a96b)) 
+  Bug \$122551677: Fixed an issue in Performance Schema that could lead to the database engine crashing when attempting to take it offline. ([https://github.com/mysql/mysql-server/commit/05e2386eccd32b6b444b900c9f8a87a1d8d531e9](https://github.com/mysql/mysql-server/commit/05e2386eccd32b6b444b900c9f8a87a1d8d531e9)) 
+  Bug \$123550835, Bug \$123298025, Bug \$181464: Fixed an issue in Performance Schema that causes a database engine crash due to exceeding the capacity of an internal buffer. ([https://github.com/mysql/mysql-server/commit/b4287f93857bf2f99b18fd06f555bbe5b12debfc](https://github.com/mysql/mysql-server/commit/b4287f93857bf2f99b18fd06f555bbe5b12debfc)) 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*.
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-12-23 (version 2.07.1) (Deprecated)
Aurora MySQL updates: 2019-12-23 (version 2.07.1) (Deprecated)Aurora MySQL version 2.07.1

Aurora MySQL version 2.07.1 is available.

**Version:** 2.07.1

Aurora MySQL 2.07.1 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.07.1. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.07.1. You cannot upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.07.1; however, you can restore its snapshot to Aurora MySQL 2.07.1. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

**Note**  
 This version is currently not available in the following AWS Regions: AWS GovCloud (US-East) [us-gov-east-1], AWS GovCloud (US-West) [us-gov-west-1], China (Ningxia) [cn-northwest-1], Asia Pacific (Hong Kong) [ap-east-1], and Middle East (Bahrain) [me-south-1]. There will be a separate announcement once it is made available. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **High priority fixes:** 
+ Fixed a slow memory leak in Aurora specific database tracing and logging sub-system that lowers the freeable memory.

 **General Stability fixes:** 
+ Fixed a crash during execution of a complex query involving multi-table joins and aggregation that use intermediate tables internally.

## Comparison with Aurora MySQL Version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-11-25 (version 2.07.0) (Deprecated)
Aurora MySQL updates: 2019-11-25 (version 2.07.0) (Deprecated)Aurora MySQL version 2.07.0

Aurora MySQL version 2.07.0 is available.

**Version:** 2.07.0

Aurora MySQL 2.07.0 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.07.0. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.07.0. You cannot upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.07.0; however, you can restore its snapshot to Aurora MySQL 2.07.0. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

**Note**  
 This version is currently not available in the following AWS Regions: AWS GovCloud (US-East) [us-gov-east-1], AWS GovCloud (US-West) [us-gov-west-1], China (Ningxia) [cn-northwest-1], Asia Pacific (Hong Kong) [ap-east-1], Middle East (Bahrain) [me-south-1], and South America (São Paulo) [sa-east-1]. There will be a separate announcement once it is made available. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **New features:** 
+  Global Databases now allow adding secondary read-only replica regions for database clusters deployed in these AWS Regions: regions: US East (N. Virginia) [us-east-1], US East (Ohio) [us-east-2], US West (N. California) [us-west-1], US West (Oregon) [us-west-2], Europe (Ireland) [eu-west-1], Europe (London) [eu-west-2], Europe (Paris) [eu-west-3], Asia Pacific (Tokyo) [ap-northeast-1], Asia Pacific (Seoul) [ap-northeast-2], Asia Pacific (Singapore) [ap-southeast-1], Asia Pacific (Sydney) [ap-southeast-2], Canada (Central) [ca-central-1], Europe (Frankfurt) [eu-central-1], and Asia Pacific (Mumbai) [ap-south-1]. 
+  Amazon Aurora machine learning is a highly optimized integration between the Aurora MySQL database and AWS machine learning (ML) services. Aurora machine learning allows developers to add a variety of ML-based predictions to their database applications by invoking ML models using the familiar SQL programming language they already use for database development, without having to build custom integrations or learn separate tools. For more information, see [Using machine learning (ML) capabilities with Amazon Aurora](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-ml.html). 
+  Added support for the ANSI `READ COMMITTED` isolation level on the read replicas. This isolation level enables long-running queries on the read replica to execute without impacting the high throughput of writes on the writer node. For more information, see [Aurora MySQL isolation levels](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Reference.html#AuroraMySQL.Reference.IsolationLevels). 

 **Critical fixes:** 
+ [CVE-2019-2922](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2922)
+ [CVE-2019-2923](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2923)
+ [CVE-2019-2924](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2924)
+ [CVE-2019-2910](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2910)

 **High-priority fixes:** 
+  Fixed an issue in the DDL recovery that resulted in prolonged database downtime. Clusters that become unavailable after executing multi-table drop statement, for example `DROP TABLE t1, t2, t3`, should be updated to this version. 
+  Fixed an issue in the DDL recovery that resulted in prolonged database downtime. Clusters that become unavailable after executing `INPLACE ALTER TABLE` DDL statements should be updated to this version. 

 **General stability fixes:** 
+  Fixed an issue that generated inconsistent data in the `information_schema.replica_host_status` table. 

## Integration of MySQL community edition bug fixes

+  Bug \$126251621: INCORRECT BEHAVIOR WITH TRIGGER AND GCOL 
+  Bug \$122574695: ASSERTION `\$1TABLE \$1\$1 (\$1TABLE->READ\$1SET \$1\$1 BITMAP\$1IS\$1SET(TABLE->READ\$1SET, FIEL 
+  Bug \$125966845: INSERT ON DUPLICATE KEY GENERATE A DEADLOCK 
+  Bug \$123070734: CONCURRENT TRUNCATE TABLES CAUSE STALL 
+  Bug \$126191879: FOREIGN KEY CASCADES USE EXCESSIVE MEMORY 
+  Bug \$120989615: INNODB AUTO\$1INCREMENT PRODUCES SAME VALUE TWICE 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.07.0 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.07.0 does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-11-22 (version 2.06.0) (Deprecated)
Aurora MySQL updates: 2019-11-22 (version 2.06.0) (Deprecated)Aurora MySQL version 2.06.0

Aurora MySQL version 2.06.0 is available.

**Version:** 2.06.0

Aurora MySQL 2.06.0 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 Currently supported Aurora MySQL releases are 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 1.19.\$1, 2.01.\$1, 2.02.\$1, 2.03.\$1, 2.04.\$1, 2.05.\$1, and 2.06.\$1. 

 You can restore a snapshot from a currently supported Aurora MySQL release into Aurora MySQL 2.06.0. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.06.0. You cannot upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.06.0; however, you can restore its snapshot to Aurora MySQL 2.06.0. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

**Note**  
 This version is currently not available in the following AWS Regions: AWS GovCloud (US-East) [us-gov-east-1], AWS GovCloud (US-West) [us-gov-west-1], China (Ningxia) [cn-northwest-1], Asia Pacific (Hong Kong) [ap-east-1], and Middle East (Bahrain) [me-south-1]. There will be a separate announcement once it is made available. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **New features:** 
+  Aurora MySQL clusters now support the instance types db.r5.8xlarge, db.r5.16xlarge, and db.r5.24xlarge. For more information about instance types for Aurora MySQL clusters, see [ Aurora DB instance classes](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Concepts.DBInstanceClass.html) in the *Amazon Aurora User Guide*. 
+  The hash join feature is now generally available and does not require the Aurora lab mode setting to be ON. This feature can improve query performance when you need to join a large amount of data by using an equi-join. For more information about using this feature, see [ Using the Data API for Aurora Serverless](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/data-api.html) in the *Amazon Aurora User Guide*. 
+  The hot row contention feature is now generally available and does not require the Aurora lab mode setting to be ON. This feature substantially improves throughput for workloads with many transactions contending for rows on the same page. 
+  Aurora MySQL 2.06 and higher support "rewinding" a DB cluster to a specific time, without restoring data from a backup. This feature, known as Backtrack, provides a quick way to recover from user errors, such as dropping the wrong table or deleting the wrong row. Backtrack completes within seconds, even for large databases. Read [the AWS blog](https://aws.amazon.com/blogs/aws/amazon-aurora-backtrack-turn-back-time/) for an overview, and refer to [ Backtracking an Aurora DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Managing.Backtrack.html) in the *Amazon Aurora User Guide* for more details. 
+  Aurora 2.06 and higher support synchronous AWS Lambda invocations through the native function `lambda_sync()`. Also available is native function `lambda_async()`, which can be used as an alternative to the existing stored procedure for asynchronous Lambda invocation. For information about calling Lambda functions, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*. 

 **Critical fixes:** 

 None. 

 **High-priority fixes:** 

 **Security fixes** 
+ [CVE-2019-2805](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2805)
+ [CVE-2019-2791](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2791)
+ [CVE-2019-2778](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2778)
+ [CVE-2019-2758](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2758)
+ [CVE-2019-2739](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2739)
+ [CVE-2019-2730](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2730)
+ [CVE-2018-3064](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3064)
+ [CVE-2018-3058](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3058)
+ [CVE-2018-2786](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2786)
+ [CVE-2017-3653](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3653)
+ [CVE-2017-3465](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3465)
+ [CVE-2017-3455](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3455)
+ [CVE-2017-3244](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3244)
+ [CVE-2016-5612](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5612)

 **Connection handling** 
+  Database availability has been improved to better service a surge in client connections while executing one or more DDLs. It is handled by temporarily creating additional threads when needed. You are advised to upgrade if the database becomes unresponsive following a surge in connections while processing DDL. 

 **Engine restart** 
+  Fixed an issue of prolonged unavailability while restarting the engine. This addresses an issue in the buffer pool initialization. This issue occurs rarely but can potentially impact any supported release. 
+  Fixed an issue that causes a database configured as a binary log (binlog) master to restart while a heavy write workload is running. 

 **General stability fixes:** 
+  Made improvements where queries accessing uncached data could be slower than usual. Customers experiencing unexplained elevated read latency while accessing uncached data are encouraged to upgrade as they may be experiencing this issue. 
+  Fixed an issue that failed to restore partitioned tables from a database snapshot. Customers who encounter errors when accessing partitioned tables in a database that has been restored from the snapshot of an Aurora MySQL 1.\$1 database are advised to use this version. 
+  Improved stability of the Aurora Replicas by fixing lock contention between threads serving read queries and the one applying schema changes while a DDL query is in progress on the writer DB instance. 
+  Fixed a stability issue related to `mysql.innodb_table_stats` table update triggered by DDL operations. 
+  Fixed an issue that incorrectly reported `ERROR 1836` when a nested query is executed against a temporary table on the Aurora Replica. 

 **Performance enhancements:** 
+  Improved performance of binlog replication by preventing unnecessary API calls to the cache if the query cache has been disabled on the binlog worker. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*. 

## MySQL 5.7 compatibility


Aurora MySQL 2.06.0 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.06.0 does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-11-11 (version 2.05.0) (Deprecated)
Aurora MySQL updates: 2019-11-11 (version 2.05.0) (Deprecated)Aurora MySQL version 2.05.0

Aurora MySQL version 2.05.0 is available.

**Version:** 2.05.0

Aurora MySQL 2.05.0 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 Currently supported Aurora MySQL releases are 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 1.19.\$1, 2.01.\$1, 2.02.\$1, 2.03.\$1 and 2.04.\$1. 

 You can restore a snapshot from a currently supported Aurora MySQL release into Aurora MySQL 2.05.0. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters, up to 2.04.6, to Aurora MySQL 2.05.0. You cannot upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.05.0; however, you can restore its snapshot to Aurora MySQL 2.05.0. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

**Note**  
 This version is currently not available in the following AWS Regions: AWS GovCloud (US-East) [us-gov-east-1], AWS GovCloud (US-West) [us-gov-west-1], China (Ningxia) [cn-northwest-1], Asia Pacific (Hong Kong) [ap-east-1], Europe (Stockholm) [eu-north-1], and Middle East (Bahrain) [me-south-1]. There will be a separate announcement once it is made available. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **Critical fixes:** 
+ [CVE-2018-0734](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-0734)
+ [CVE-2019-2534](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2534)
+ [CVE-2018-3155](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3155)
+ [CVE-2018-2612](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2612)
+ [CVE-2017-3599](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3599)
+ [CVE-2018-3056](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3056)
+ [CVE-2018-2562](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2562)
+ [CVE-2017-3329](https://nvd.nist.gov/vuln/detail/CVE-2017-3329)
+ [CVE-2018-2696](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2696)
+ Fixed an issue where the events in current binlog file on the master were not replicated on the worker if the value of the parameter `sync_binlog` was not set to 1.

 **High-priority fixes:** 
+  Customers with database size close to 64 tebibytes (TiB) are strongly advised to upgrade to this version to avoid downtime due to stability bugs affecting volumes close to the Aurora storage limit. 
+  The default value of the parameter `aurora_binlog_replication_max_yield_seconds` has been changed to zero to prevent an increase in replication lag in favor of foreground query performance on the binlog master. 

## Integration of MySQL bug fixes

+  Bug\$123054591: PURGE BINARY LOGS TO is reading the whole binlog file and causing MySql to Stall 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*.
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.05.0 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.05.0 does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2020-08-14 (version 2.04.9) (Deprecated)
Aurora MySQL updates: 2020-08-14 (version 2.04.9) (Deprecated)Aurora MySQL version 2.04.9

Aurora MySQL version 2.04.9 is available.

**Version:** 2.04.9

Aurora MySQL 2.04.9 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

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**  
 This version is currently not available in the following AWS Regions: AWS GovCloud (US-East) [us-gov-east-1], AWS GovCloud (US-West) [us-gov-west-1], Asia Pacific (Hong Kong) [ap-east-1], and Middle East (Bahrain) [me-south-1]. There will be a separate announcement once it is made available. 

**Note**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **High-priority fixes:** 

 **Critical fixes:** 
+ [CVE-2020-2760](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-2760)
+ [CVE-2019-5443](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-5443)
+ [CVE-2019-3822](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3822)
+ [CVE-2019-2924](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2924)
+ [CVE-2019-2923](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2923)
+ [CVE-2019-2922](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2922)
+ [CVE-2019-2911](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2911)
+ [CVE-2019-2910](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2910)
+ [CVE-2019-2805](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2805)
+ [CVE-2019-2791](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2791)
+ [CVE-2019-2778](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2778)
+ [CVE-2019-2758](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2758)
+ [CVE-2019-2740](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2740)
+ [CVE-2019-2739](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2739)
+ [CVE-2019-2730](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2730)
+ [CVE-2019-2628](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2628)
+ [CVE-2018-3064](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3064)
+ [CVE-2018-3058](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-3058)
+ [CVE-2018-2813](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2813)
+ [CVE-2018-2786](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-2786)
+ [CVE-2017-3653](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3653)
+ [CVE-2017-3465](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3465)
+ [CVE-2017-3464](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3464)
+ [CVE-2017-3455](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3455)
+ [CVE-2017-3244](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3244)
+ [CVE-2016-5612](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5612)
+ [CVE-2016-5436](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5436)

 **Availability improvements:** 
+  Fixed an issue that could cause a database restart or failover due to execution of a `kill session` command. If you encounter this issue, contact AWS support to enable this fix on your instance. 
+  Fixed an issue that causes a database restart during execution of a complex query involving multi-table joins and aggregation that use intermediate tables internally. 
+  Fixed an issue that causes database restarts due to an interrupted `DROP TABLE` on multiple tables. 
+  Fixed an issue that causes a database failover during database recovery. 
+  Fixed a database restart caused by incorrect reporting of threads\$1running when audit and slow query logs are enabled. 
+  Fixed an issue where a `kill query` command might get stuck during execution. 
+  Fixed a race condition in the lock manager that resulted in a database restart or failover during transaction rollback. 
+  Fixed an issue that triggered database restart or failover when multiple connections are trying to update the same table with a Full-Text Search index. 
+  Fixed an issue that can cause a deadlatch when purging an index resulting in a failover or restart. 

 **General improvements:** 
+  Fixed issues that could cause queries on read replicas to use data from an uncommitted transaction. This issue is limited to the transactions that are started immediately after a database restart. 
+  Fixed an issue encountered during `INPLACE ALTER TABLE` for a table with triggers defined and when the DDL did not contain a `RENAME` clause. 
+  Fixed an issue that caused cloning to take longer on some database clusters with high writeload. 
+  Fixed an issue encountered during an upgrade when a partitioned table has embedded spaces in the name. 
+  Fixed an issue where the read replica might transiently see partial results of a recently committed transaction on the writer. 
+  Fixed an issue where queries on a read replica against an FTS table may produce stale results. This will only occur when the FTS query on the read replica closely follows a query on `INFORMATION_SCHEMA.INNODB_SYS_TABLES` for the same FTS table on the writer. 
+  Fixed an issue that resulted in a slow restore of Aurora 1.x database cluster containing FTS (Full-Text Search) indexes to an Aurora 2.x database cluster. 
+  Extended maximum allowable length to 2000 for `server_audit_incl_users` and `server_audit_excl_users` global parameters. 
+  Fixed an issue where Aurora 1.x to Aurora 2.x restore might take an extended time to complete. 
+  Fixed an issue where a `lambda_async` invocation through stored procedure doesn't work with Unicode. 
+  Fixed an issue encountered when a spatial index does not properly handle an off-record geometry column. 
+  Fixed an issue that might cause a query to fail on a reader DB instance with `InternalFailureException` error with message"Operation terminated (internal error)". 

## Integration of MySQL bug fixes

+  Bug \$123070734, Bug \$180060: Concurrent TRUNCATE TABLEs cause stalls 
+  Bug \$123103937: PS\$1TRUNCATE\$1ALL\$1TABLES() DOES NOT WORK IN SUPER\$1READ\$1ONLY MODE 
+  Bug\$122551677: When taking the server offline, a race condition within the Performance Schema could lead to a server exit. 
+  Bug \$127082268: Invalid FTS sync synchronization. 
+  BUG \$112589870: Fixed an issues which causes a restart with multi-query statement when query cache is enabled. 
+  Bug \$126402045: Certain cases of subquery materialization could cause a server exit. These queries now produce an error suggesting that materialization be disabled. 
+  Bug \$118898433: Queries with many left joins were slow if join buffering was used (for example, using the block nested loop algorithm). 
+  Bug \$125222337: A NULL virtual column field name in a virtual index caused a server exit during a field name comparison that occurs while populating virtual columns affected by a foreign key constraint. ([https://github.com/mysql/mysql-server/commit/273d5c9d7072c63b6c47dbef6963d7dc491d5131](https://github.com/mysql/mysql-server/commit/273d5c9d7072c63b6c47dbef6963d7dc491d5131)) 
+  Bug \$125053286: Executing a stored procedure containing a query that accessed a view could allocate memory that was not freed until the session ended. ([https://github.com/mysql/mysql-server/commit/d7b37d4d141a95f577916448650c429f0d6e193d](https://github.com/mysql/mysql-server/commit/d7b37d4d141a95f577916448650c429f0d6e193d)) 
+  Bug \$125586773: Executing a stored procedure containing a statement that created a table from the contents of certain SELECT (https://dev.mysql.com/doc/refman/5.7/en/select.html) statements could result in a memory leak. ([https://github.com/mysql/mysql-server/commit/88301e5adab65f6750f66af284be410c4369d0c1](https://github.com/mysql/mysql-server/commit/88301e5adab65f6750f66af284be410c4369d0c1)) 
+  Bug \$126666274: INFINITE LOOP IN PERFORMANCE SCHEMA BUFFER CONTAINER. 
+  Bug \$123550835, Bug \$123298025, Bug \$181464: A SELECT Performance Schema tables when an internal buffer was full could cause a server exit. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*.
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*. 
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.04.9 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.04.9 does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-11-20 (version 2.04.8) (Deprecated)
Aurora MySQL updates: 2019-11-20 (version 2.04.8) (Deprecated)Aurora MySQL version 2.04.8

Aurora MySQL version 2.04.8 is available.

**Version:** 2.04.8

Aurora MySQL 2.04.8 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 of any 2.\$1 Aurora MySQL release into Aurora MySQL 2.04.8. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.04.8. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

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**  
 This version is currently not available in the following AWS Regions: AWS GovCloud (US-East) [us-gov-east-1], AWS GovCloud (US-West) [us-gov-west-1], Asia Pacific (Hong Kong) [ap-east-1], and Middle East (Bahrain) [me-south-1]. There will be a separate announcement once it is made available. 

**Note**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **New features:** 
+  **Read replica improvements:** 
  +  Reduced network traffic from the writer instance by efficiently transmitting data to reader instances within the Aurora DB cluster. This improvement is enabled by default, because it helps prevent replicas from falling behind and restarting. The parameter for this feature is `aurora_enable_repl_bin_log_filtering`. 
  +  Reduced network traffic from the writer to reader instances within the Aurora DB cluster using compression. This improvement is enabled by default for 8xlarge and 16xlarge instance classes only, because these instances can tolerate additional CPU overhead for compression. The parameter for this feature is `aurora_enable_replica_log_compression`. 

 **High-priority fixes:** 
+  Improved memory management in the Aurora writer instance that prevents restart of writer due to out of memory conditions during heavy workload in presence of reader instances within the Aurora DB cluster. 
+  Fix for a non-deterministic condition in the scheduler that results in engine restart while accessing the performance schema object concurrently. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.04.8 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.04.8 does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-11-14 (version 2.04.7) (Deprecated)
Aurora MySQL updates: 2019-11-14 (version 2.04.7) (Deprecated)Aurora MySQL version 2.04.7

Aurora MySQL version 2.04.7 is available.

**Version:** 2.04.7

Aurora MySQL 2.04.7 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 a currently supported Aurora MySQL release into Aurora MySQL 2.04.7. You also have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.04.7. You can't upgrade an existing Aurora MySQL 1.\$1 cluster directly to 2.04.7; however, you can restore its snapshot to Aurora MySQL 2.04.7. 

 To create a cluster with an older version of Aurora MySQL, please specify the engine version through the AWS Management Console, the AWS CLI, or the RDS API. 

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**  
 This version is currently not available in the following AWS Regions: AWS GovCloud (US-East) [us-gov-east-1], AWS GovCloud (US-West) [us-gov-west-1], Asia Pacific (Hong Kong) [ap-east-1], and Middle East (Bahrain) [me-south-1]. There will be a separate announcement once it is made available. 

**Note**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


 **High-priority fixes:** 

 **Connection Handling** 
+  Database availability has been improved to better service a surge in client connections while executing one or more DDLs. It is handled by temporarily creating additional threads when needed. You are advised to upgrade if the database becomes unresponsive following a surge in connections while processing DDL. 
+  Fixed an issue that resulted in an incorrect value for the `Threads_running` global status variable. 

 **Engine Restart** 
+  Fixed an issue of prolonged unavailability while restarting the engine. This addresses an issue in the buffer pool initialization. This issue occurs rarely but can potentially impact any supported release. 

 **General stability fixes:** 
+  Made improvements where queries accessing uncached data could be slower than usual. Customers experiencing unexplained elevated read latencies while accessing uncached data are encouraged to upgrade as they may be experiencing this issue. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.04.7 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.04.7 does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-09-19 (version 2.04.6) (Deprecated)
Aurora MySQL updates: 2019-09-19 (version 2.04.6) (Deprecated)Aurora MySQL version 2.04.6

Aurora MySQL version 2.04.6 is available.

**Version:** 2.04.6

Aurora MySQL 2.04.6 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.04.6. We do not allow in-place upgrade of Aurora MySQL 1.\$1 clusters. This restriction will be lifted in a later Aurora MySQL 2.\$1 release. You can restore snapshots of Aurora MySQL 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 1.19.\$1, 2.01.\$1, 2.02.\$1, 2.03.\$1 and 2.04.\$1 into Aurora MySQL 2.04.6. 

 To use an older version of Aurora MySQL, you can create new database clusters by specifying the engine version through the AWS Management Console, the AWS CLI, or the Amazon RDS API. 

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**  
 This version is currently not available in the following AWS Regions: Europe (London) [eu-west-2], AWS GovCloud (US-East) [us-gov-east-1], AWS GovCloud (US-West) [us-gov-west-1], China (Ningxia) [cn-northwest-1], and Asia Pacific (Hong Kong) [ap-east-1]. There will be a separate announcement once it is made available. 

**Note**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements

+  Fixed an issue where the events in current binlog file on the master were not replicated on the worker if the value of the parameter `sync_binlog` was not set to 1. 
+  The default value of the parameter `aurora_binlog_replication_max_yield_seconds` has been changed to zero to prevent an increase in replication lag in favor of foreground query performance on the binlog master. 

## Integration of MySQL bug fixes

+  Bug\$123054591: PURGE BINARY LOGS TO is reading the whole binlog file and causing MySql to Stall 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.04.6 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.04.6 does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-07-08 (version 2.04.5) (Deprecated)
Aurora MySQL updates: 2019-07-08 (version 2.04.5) (Deprecated)Aurora MySQL version 2.04.5

Aurora MySQL version 2.04.5 is available.

**Version:** 2.04.5

Aurora MySQL 2.04.5 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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 have the option to upgrade existing Aurora MySQL 2.\$1 database clusters to Aurora MySQL 2.04.5. We do not allow in-place upgrade of Aurora MySQL 1.\$1 clusters. This restriction will be lifted in a later Aurora MySQL 2.\$1 release. You can restore snapshots of Aurora MySQL 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 1.19.\$1, 2.01.\$1, 2.02.\$1, 2.03.\$1 and 2.04.\$1 into Aurora MySQL 2.04.5. 

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**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


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

 **General fixes:** 
+  Fixed a race condition during storage volume growth that caused the database to restart. 
+  Fixed an internal communication failure during volume open that caused the database to restart. 
+  Added DDL recovery support for `ALTER TABLE ALGORITHM=INPLACE` on partitioned tables. 
+  Fixed an issue with DDL recovery of `ALTER TABLE ALGORITHM=COPY` that caused the database to restart. 
+  Improved Aurora Replica stability under heavy delete workload on the writer. 
+  Fixed a database restart caused by a deadlatch between the thread performing full-text search index sync and the thread performing eviction of full-text search table from dictionary cache. 
+  Fixed a stability issue on the binlog worker during DDL replication while the connection to the binlog master is unstable. 
+  Fixed an out-of-memory issue in the full-text search code that caused the database to restart. 
+  Fixed an issue on the Aurora Writer that caused it to restart when the entire 64 tebibyte (TiB) volume is used. 
+  Fixed a race condition in the Performance Schema feature that caused the database to restart. 
+  Fixed an issue that caused aborted connections when handling an error in network protocol management. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.04.5 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.04.5 does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-05-29 (version 2.04.4) (Deprecated)
Aurora MySQL updates: 2019-05-29 (version 2.04.4) (Deprecated)Aurora MySQL version 2.04.4

Aurora MySQL version 2.04.4 is available.

**Version:** 2.04.4

Aurora MySQL 2.04.4 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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. 

When creating a new Aurora MySQL DB cluster (including restoring a snapshot), you have the option of choosing compatibility with either MySQL 5.7 or MySQL 5.6. We do not allow in-place upgrade of Aurora MySQL 1.\$1 clusters or restore of Aurora MySQL 1.\$1 clusters from an Amazon S3 backup into Aurora MySQL 2.04.4. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

You can restore snapshots of Aurora MySQL 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 1.19.\$1, 2.01.\$1, 2.02.\$1, 2.03.\$1, and 2.04.\$1 into Aurora MySQL 2.04.4.

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**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1], Europe (Stockholm) [eu-north-1], China (Ningxia) [cn-northwest-1], and Asia Pacific (Hong Kong) [ap-east-1] AWS Regions. There will be a separate announcement once it is made available. 

**Note**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements

+  Fixed an issue that could cause failures when loading data into Aurora from S3. 
+  Fixed an issue that could cause failures when upload data from Aurora to S3. 
+  Fixed an issue that caused aborted connections when handling an error in network protocol management. 
+  Fixed an issue that could cause a crash when dealing with partitioned tables. 
+  Fixed an issue with the Performance Insights feature being unavailable in some regions. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.04.4 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.04.4 does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-05-09 (version 2.04.3) (Deprecated)
Aurora MySQL updates: 2019-05-09 (version 2.04.3) (Deprecated)Aurora MySQL version 2.04.3

Aurora MySQL version 2.04.3 is available.

**Version:** 2.04.3

Aurora MySQL 2.04.3 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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. 

When creating a new Aurora MySQL DB cluster (including restoring a snapshot), you have the option of choosing compatibility with either MySQL 5.7 or MySQL 5.6. We do not allow in-place upgrade of Aurora MySQL 1.\$1 clusters or restore of Aurora MySQL 1.\$1 clusters from an Amazon S3 backup into Aurora MySQL 2.04.3. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

You can restore snapshots of Aurora MySQL 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 1.19.\$1, 2.01.\$1, 2.02.\$1, 2.03.\$1, and 2.04.\$1 into Aurora MySQL 2.04.3.

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**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] and China (Ningxia) [cn-northwest-1] AWS Regions. There will be a separate announcement once it is made available. 

**Note**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements

+  Fixed a bug in binlog replication that can cause an issue on Aurora instances configured as binlog worker. 
+  Fixed an out-of-memory condition when handling large stored routines. 
+  Fixed an error in handling certain kinds of `ALTER TABLE` commands. 
+  Fixed an issue with aborted connections because of an error in network protocol management. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.04.3 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.04.3 does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-05-02 (version 2.04.2) (Deprecated)
Aurora MySQL updates: 2019-05-02 (version 2.04.2) (Deprecated)Aurora MySQL version 2.04.2

Aurora MySQL version 2.04.2 is available.

**Version:** 2.04.2

Aurora MySQL 2.04.2 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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. 

When creating a new Aurora MySQL DB cluster (including restoring a snapshot), you have the option of choosing compatibility with either MySQL 5.7 or MySQL 5.6. We do not allow in-place upgrade of Aurora MySQL 1.\$1 clusters or restore of Aurora MySQL 1.\$1 clusters from an Amazon S3 backup into Aurora MySQL 2.04.2. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

You can restore snapshots of Aurora MySQL 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 1.19.\$1, 2.01.\$1, 2.02.\$1, 2.03.\$1, 2.04.0, and 2.04.1 into Aurora MySQL 2.04.2.

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**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] and China (Ningxia) [cn-northwest-1] AWS Regions. There will be a separate announcement once it is made available. 

**Note**  
For information on how to upgrade your Aurora MySQL database cluster, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements

+  Added support for SSL binlog replication using custom certificates. For information on using SSL binlog replication in Aurora MySQL, see [mysql\$1rds\$1import\$1binlog\$1ssl\$1material](https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/mysql_rds_import_binlog_ssl_material.html). 
+  Fixed a deadlatch on the Aurora primary instance that occurs when a table with a Full Text Search index is being optimized. 
+  Fixed an issue on the Aurora Replicas where performance of certain queries using `SELECT(*)` could be impacted on tables that have secondary indexes. 
+  Fixed a condition that resulted in Error 1032 being posted. 
+  Improved the stability of Aurora Replicas by fixing multiple deadlatches. 

## Integration of MySQL bug fixes

+  Bug \$124829050 - INDEX\$1MERGE\$1INTERSECTION OPTIMIZATION CAUSES WRONG QUERY RESULTS 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.04.2 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.04.2 does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-03-25 (version 2.04.1) (Deprecated)
Aurora MySQL updates: 2019-03-25 (version 2.04.1) (Deprecated)Aurora MySQL version 2.04.1

Aurora MySQL version 2.04.1 is available.

**Version:** 2.04.1

Aurora MySQL 2.04.1 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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. 

When creating a new Aurora MySQL DB cluster (including restoring a snapshot), you have the option of choosing compatibility with either MySQL 5.7 or MySQL 5.6. We do not allow in-place upgrade of Aurora MySQL 1.\$1 clusters or restore of Aurora MySQL 1.\$1 clusters from an Amazon S3 backup into Aurora MySQL 2.04.1. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

You can restore snapshots of Aurora MySQL 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 1.19.\$1, 2.01.\$1, 2.02.\$1, 2.03.\$1, 2.04.0 into Aurora MySQL 2.04.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*.

**Note**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] region. There will be a separate announcement once it is made available. 

**Note**  
The procedure to upgrade your DB cluster has changed. For more information, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements

+  Fixed an issue where an Aurora MySQL 5.6 snapshot for versions lower than 1.16 could not be restored to the latest Aurora MySQL 5.7 cluster. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-03-25 (version 2.04.0) (Deprecated)
Aurora MySQL updates: 2019-03-25 (version 2.04.0) (Deprecated)Aurora MySQL version 2.04

Aurora MySQL version 2.04 is available.

**Version:** 2.04

Aurora MySQL 2.04 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

 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. 

When creating a new Aurora MySQL DB cluster (including restoring a snapshot), you have the option of choosing compatibility with either MySQL 5.7 or MySQL 5.6. We do not allow in-place upgrade of Aurora MySQL 1.\$1 clusters or restore of Aurora MySQL 1.\$1 clusters from an Amazon S3 backup into Aurora MySQL 2.04.0. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

You can restore snapshots of Aurora MySQL 1.19.\$1, 2.01.\$1, 2.02.\$1, and 2.03.\$1 into Aurora MySQL 2.04.0. You cannot restore snapshots of Aurora MySQL 1.14.\$1 or lower, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1 into Aurora MySQL 2.04.0. This restriction is removed in Aurora MySQL 2.04.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*.

**Note**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] region. There will be a separate announcement once it is made available. 

**Note**  
The procedure to upgrade your DB cluster has changed. For more information, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements

+  Supports GTID-based replication. For information about using GTID-based replication with Aurora MySQL, [ Using GTID-based replication for Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/mysql-replication-gtid.html) in the *Amazon Aurora User Guide*. 
+  Fixed an issue where an Aurora Replica incorrectly throws a`Running in read-only mode` error when a statement deleting or updating rows in a temporary table contains an InnoDB subquery. 

## Integration of MySQL bug fixes

+  Bug \$126225783: MYSQL CRASH ON CREATE TABLE (REPRODUCEABLE) -> INNODB: ALONG SEMAPHORE WAIT. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL Version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL Version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


This Aurora MySQL version is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

This Aurora MySQL version does not currently support the following MySQL 5.7 features:
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement

# Aurora MySQL database engine updates 2019-02-07 (version 2.03.4) (Deprecated)
Aurora MySQL updates: 2019-02-07 (version 2.03.4) (Deprecated)Aurora MySQL version 2.03.4

Aurora MySQL version 2.03.4 is available.

**Version:** 2.03.4

Aurora MySQL 2.03.4 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

When creating a new Aurora MySQL DB cluster (including restoring a snapshot), you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

We don't allow in-place upgrade of Aurora MySQL 1.\$1 clusters into Aurora MySQL 2.03.4 or restore to Aurora MySQL 2.03.4 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

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**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] and China (Beijing) [cn-north-1] regions. There will be a separate announcement once it is made available. 

**Note**  
The procedure to upgrade your DB cluster has changed. For more information, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements

+  Support for UTF8MB4 Unicode 9.0 accent-sensitive and case-insensitive collation, `utf8mb4_0900_as_ci`. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.03.4 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.03.4 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

# Aurora MySQL database engine updates 2019-01-18 (version 2.03.3) (Deprecated)
Aurora MySQL updates: 2019-01-18 (version 2.03.3) (Deprecated)Aurora MySQL version 2.03.3

Aurora MySQL version 2.03.3 is available.

**Version:** 2.03.3

Aurora MySQL 2.03.3 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

When creating a new Aurora MySQL DB cluster (including restoring a snapshot), you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

We don't allow in-place upgrade of Aurora MySQL 1.\$1 clusters into Aurora MySQL 2.03.3 or restore to Aurora MySQL 2.03.3 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

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**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] and China (Beijing) [cn-north-1] regions. There will be a separate announcement once it is made available. 

**Note**  
The procedure to upgrade your DB cluster has changed. For more information, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements


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

 **Critical fixes:** 
+  Fixed an issue where an Aurora Replica might become dead-latched when running a backward scan on an index. 
+  Fixed an issue where an Aurora Replica might restart when the Aurora primary instance runs in-place DDL operations on partitioned tables. 
+  Fixed an issue where an Aurora Replica might restart during query cache invalidation after a DDL operation on the Aurora primary instance. 
+  Fixed an issue where an Aurora Replica might restart during a `SELECT` query on a table while the Aurora primary instance runs truncation on that table. 
+  Fixed a wrong result issue with MyISAM temporary tables where only indexed columns are accessed. 
+  Fixed an issue in slow logs that generated incorrect large values for `query_time` and `lock_time` periodically after approximately 40,000 queries. 
+  Fixed an issue where a schema named "tmp" could cause migration from RDS for MySQL to Aurora MySQL to become stuck. 
+  Fixed an issue where the audit log might have missing events during log rotation. 
+  Fixed an issue where the Aurora primary instance restored from an Aurora 5.6 snapshot might restart when the Fast DDL feature in the lab mode is enabled. 
+  Fixed an issue where the CPU usage is 100% caused by the dictionary stats thread. 
+  Fixed an issue where an Aurora Replica might restart when running a `CHECK TABLE` statement. 

## Integration of MySQL bug fixes

+  Bug \$125361251: INCORRECT BEHAVIOR WITH INSERT ON DUPLICATE KEY IN SP 
+  Bug \$126734162: INCORRECT BEHAVIOR WITH INSERT OF BLOB \$1 ON DUPLICATE KEY UPDATE 
+  Bug \$127460607: INCORRECT BEHAVIOR OF IODKU WHEN INSERT SELECT's SOURCE TABLE IS EMPTY 
+  A query using a `DISTINCT` or `GROUP BY` clause could return incorrect results. (MySQL 5.7 Bug \$179591, Bug \$122343910) 
+  A `DELETE` from joined tables using a derived table in the `WHERE` clause fails with error 1093 (Bug \$123074801). 
+  GCOLS: INCORRECT BEHAVIOR WITH CHARSET CHANGES (Bug \$125287633). 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.03.3 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.03.3 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

# Aurora MySQL database engine updates 2019-01-09 (version 2.03.2) (Deprecated)
Aurora MySQL updates: 2019-01-09 (version 2.03.2) (Deprecated)Aurora MySQL version 2.03.2

Aurora MySQL version 2.03.2 is available.

**Version:** 2.03.2

Aurora MySQL 2.03.2 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

When creating a new Aurora MySQL DB cluster (including restoring a snapshot), you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

We don't allow in-place upgrade of Aurora MySQL 1.\$1 clusters into Aurora MySQL 2.03.2 or restore to Aurora MySQL 2.03.2 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

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**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] and China (Beijing) [cn-north-1] regions. There will be a separate announcement once it is made available. 

**Note**  
The procedure to upgrade your DB cluster has changed. For more information, see [ Upgrading the minor version or patch level of an Aurora MySQL DB cluster](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Patching.html) in the *Amazon Aurora User Guide*.

## Improvements

+  **Aurora Version Selector** – Starting with Aurora MySQL 2.03.2, you can choose from among multiple versions of MySQL 5.7-compatible Aurora on the AWS Management Console. For more information, see [ Checking or specifying Aurora MySQL engine versions through AWS](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Versions.html#AuroraMySQL.Updates.EngineVersions) in the *Amazon Aurora User Guide*. 

 **Critical fixes:** 
+ [CVE-2016-3495](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3495)

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.03.2 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.03.2 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

# Aurora MySQL database engine updates 2018-10-24 (version 2.03.1) (Deprecated)
Aurora MySQL updates: 2018-10-24 (version 2.03.1) (Deprecated)Aurora MySQL version 2.03.1

Aurora MySQL version 2.03.1 is available.

**Version:** 2.03.1

Aurora MySQL 2.03.1 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

When creating a new Aurora MySQL DB cluster, you can choose compatibility with either MySQL 5.7 or MySQL 5.6. When restoring a MySQL 5.6-compatible snapshot, you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

You can restore snapshots of Aurora MySQL 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 2.01.\$1, 2.02.\$1, and 2.03 into Aurora MySQL 2.03.1.

We don't allow in-place upgrade of Aurora MySQL 1.\$1 clusters into Aurora MySQL 2.03.1 or restore to Aurora MySQL 2.03.1 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

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**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] and China (Beijing) [cn-north-1] regions. There will be a separate announcement once it is made available. 

## Improvements

+  Fix an issue where the Aurora Writer might restart when running transaction deadlock detection. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.03.1 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.03.1 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

# Aurora MySQL database engine updates 2018-10-11 (version 2.03) (Deprecated)
Aurora MySQL updates: 2018-10-11 (version 2.03) (Deprecated)Aurora MySQL version 2.03

Aurora MySQL version 2.03 is available.

**Version:** 2.03

Aurora MySQL 2.03 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

When creating a new Aurora MySQL DB cluster, you can choose compatibility with either MySQL 5.7 or MySQL 5.6. When restoring a MySQL 5.6-compatible snapshot, you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

You can restore snapshots of Aurora MySQL 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 2.01.\$1, and 2.02.\$1 into Aurora MySQL 2.03.

We don't allow in-place upgrade of Aurora MySQL 1.\$1 clusters into Aurora MySQL 2.03 or restore to Aurora MySQL 2.03 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

**Note**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] and China (Beijing) [cn-north-1] regions. There will be a separate announcement once it is made available. 

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

+  Performance schema is available. 
+  Fixed an issue where zombie sessions with killed state might consume more CPU. 
+  Fixed a dead latch issue when a read-only transaction is acquiring a lock on a record on the Aurora Writer. 
+  Fixed an issue where the Aurora Replica without customer workload might have high CPU utilization. 
+  Multiple fixes on issues that might cause the Aurora Replica or the Aurora writer to restart. 
+  Added capability to skip diagnostic logging when the disk throughput limit is reached. 
+  Fixed a memory leak issue when binlog is enabled on the Aurora Writer. 

## Integration of MySQL community edition bug fixes

+  REVERSE SCAN ON A PARTITIONED TABLE DOES ICP - ORDER BY DESC (Bug \$124929748). 
+  JSON\$1OBJECT CREATES INVALID JSON CODE (Bug\$126867509). 
+  INSERTING LARGE JSON DATA TAKES AN INORDINATE AMOUNT OF TIME (Bug \$122843444). 
+  PARTITIONED TABLES USE MORE MEMORY IN 5.7 THAN 5.6 (Bug \$125080442). 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.03 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.03 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

# Aurora MySQL database engine updates 2018-10-08 (version 2.02.5) (Deprecated)
Aurora MySQL updates: 2018-10-08 (version 2.02.5) (Deprecated)Aurora MySQL version 2.02.5

Aurora MySQL version 2.02.5 is available.

**Version:** 2.02.5

Aurora MySQL 2.02.5 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

When creating a new Aurora MySQL DB cluster, you can choose compatibility with either MySQL 5.7 or MySQL 5.6. When restoring a MySQL 5.6-compatible snapshot, you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

You can restore snapshots of Aurora MySQL 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 2.01.\$1, and 2.02.\$1 into Aurora MySQL 2.02.5. You can also perform an in-place upgrade from Aurora MySQL 2.01.\$1 or 2.02.\$1 to Aurora MySQL 2.02.5.

We don't allow in-place upgrade of Aurora MySQL 1.\$1 clusters into Aurora MySQL 2.02.5 or restore to Aurora MySQL 2.02.5 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

The performance schema is disabled for this release of Aurora MySQL 5.7. Upgrade to Aurora 2.03 for performance schema support.

**Note**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] and China (Beijing) [cn-north-1] regions. There will be a separate announcement once it is made available. 

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

+  Fix an issue where an Aurora Replica might restart when it is doing a reverse scan on a table. 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.02.5 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.02.5 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

# Aurora MySQL database engine updates 2018-09-21 (version 2.02.4) (Deprecated)
Aurora MySQL updates: 2018-09-21 (version 2.02.4) (Deprecated)Aurora MySQL version 2.02.4

Aurora MySQL version 2.02.4 is available.

**Version:** 2.02.4

Aurora MySQL 2.02.4 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

When creating a new Aurora MySQL DB cluster, you can choose compatibility with either MySQL 5.7 or MySQL 5.6. When restoring a MySQL 5.6-compatible snapshot, you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

You can restore snapshots of Aurora MySQL 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 1.18.\$1, 2.01.\$1, and 2.02.\$1 into Aurora MySQL 2.02.4. You can also perform an in-place upgrade from Aurora MySQL 2.01.\$1 or 2.02.\$1 to Aurora MySQL 2.02.4.

We don't allow in-place upgrade of Aurora MySQL 1.\$1 clusters into Aurora MySQL 2.02.4 or restore to Aurora MySQL 2.02.4 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

The performance schema is disabled for this release of Aurora MySQL 5.7. Upgrade to Aurora 2.03 for performance schema support.

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

+ Fixed a stability issue related to Full Text Search indexes on tables restored from an Aurora MySQL 5.6 snapshot.

## Integration of MySQL community edition bug fixes

+  `BUG#13651665 INNODB MAY BE UNABLE TO LOAD TABLE DEFINITION AFTER RENAME` 
+  `BUG#21371070 INNODB: CANNOT ALLOCATE 0 BYTES.` 
+  `BUG#21378944 FTS ASSERT ENC.SRC_ILIST_PTR != NULL, FTS_OPTIMIZE_WORD(), OPTIMIZE TABLE` 
+  `BUG#21508537 ASSERTION FAILURE UT_A(!VICTIM_TRX->READ_ONLY)` 
+  `BUG#21983865 UNEXPECTED DEADLOCK WITH INNODB_AUTOINC_LOCK_MODE=0` 
+  `BUG#22679185 INVALID INNODB FTS DOC ID DURING INSERT` 
+  `BUG#22899305 GCOLS: ASSERTION: !(COL->PRTYPE & 256).` 
+  `BUG#22956469 MEMORY LEAK INTRODUCED IN 5.7.8 IN MEMORY/INNODB/OS0FILE` 
+  `BUG#22996488 CRASH IN FTS_SYNC_INDEX WHEN DOING DDL IN A LOOP` 
+  `BUG#23014521 GCOL:INNODB: ASSERTION: !IS_V` 
+  `BUG#23021168 REPLICATION STOPS AFTER TRX IS ROLLED BACK ASYNC` 
+  `BUG#23052231 ASSERTION: ADD_AUTOINC < DICT_TABLE_GET_N_USER_COLS` 
+  `BUG#23149683 ROTATE INNODB MASTER KEY WITH KEYRING_OKV_CONF_DIR MISSING: SIGSEGV; SIGNAL 11` 
+  `BUG#23762382 INSERT VALUES QUERY WITH JOIN IN A SELECT CAUSES INCORRECT BEHAVIOR` 
+  `BUG#25209512 CURRENT_TIMESTAMP PRODUCES ZEROS IN TRIGGER` 
+  `BUG#26626277 BUG IN "INSERT... ON DUPLICATE KEY UPDATE" QUERY` 
+  `BUG#26734162 INCORRECT BEHAVIOR WITH INSERT OF BLOB + ON DUPLICATE KEY UPDATE` 
+  `BUG#27460607 INCORRECT WHEN INSERT SELECT's SOURCE TABLE IS EMPTY` 

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

## MySQL 5.7 compatibility


Aurora MySQL 2.02.4 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.02.4 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

# Aurora MySQL database engine updates 2018-08-23 (version 2.02.3) (Deprecated)
Aurora MySQL updates: 2018-08-23 (version 2.02.3) (Deprecated)

**Version:** 2.02.3

Aurora MySQL 2.02.3 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

When creating a new Aurora MySQL DB cluster, you can choose compatibility with either MySQL 5.7 or MySQL 5.6. When restoring a MySQL 5.6-compatible snapshot, you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

You can restore snapshots of Aurora MySQL 1.14.\$1, 1.15.\$1, 1.16.\$1, 1.17.\$1, 2.01.\$1, and 2.02.\$1 into Aurora MySQL 2.02.3. You can also perform an in-place upgrade from Aurora MySQL 2.01.\$1 or 2.02.\$1 to Aurora MySQL 2.02.3.

We don't allow in-place upgrade of Aurora MySQL 1.\$1 clusters into Aurora MySQL 2.02.3 or restore to Aurora MySQL 2.02.3 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

The performance schema is disabled for this release of Aurora MySQL 5.7. Upgrade to Aurora 2.03 for performance schema support.

**Note**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] and China (Beijing) [cn-north-1] regions. There will be a separate announcement once it is made available. 

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*.

## Comparison with Aurora MySQL version 1


The following Amazon Aurora MySQL features are supported in Aurora MySQL version 1 (compatible with MySQL 5.6), but these features are currently not supported in Aurora MySQL version 2 (compatible with MySQL 5.7).
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

Currently, Aurora MySQL 2.01 does not support features added in Aurora MySQL version 1.16 and later. For information about Aurora MySQL version 1.16, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


Aurora MySQL 2.02.3 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.02.3 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

## CLI differences between Aurora MySQL 2.x and Aurora MySQL 1.x

+ The engine name for Aurora MySQL 2.x is `aurora-mysql`; the engine name for Aurora MySQL 1.x continues to be `aurora`.
+ The default parameter group for Aurora MySQL 2.x is `default.aurora-mysql5.7`; the default parameter group for Aurora MySQL 1.x continues to be `default.aurora5.6`.
+ The DB cluster parameter group family name for Aurora MySQL 2.x is `aurora-mysql5.7`; the DB cluster parameter group family name for Aurora MySQL 1.x continues to be `aurora5.6`.

Refer to the Aurora documentation for the full set of CLI commands and differences between Aurora MySQL 2.x and Aurora MySQL 1.x.

## Improvements

+ Fixed an issue where an Aurora Replica can restart when using optimistic cursor restores while reading records.
+ Updated the default value of the parameter `innodb_stats_persistent_sample_pages` to 128 to improve index statistics.
+ Fixed an issue where an Aurora Replica might restart when it accesses a small table that is being concurrently modified on the Aurora primary instance.
+ Fixed `ANALYZE TABLE` to stop flushing the table definition cache.
+ Fixed an issue where the Aurora primary instance or an Aurora Replica might restart when converting a point query for geospatial to a search range.

# Aurora MySQL database engine updates 2018-06-04 (version 2.02.2) (Deprecated)
Aurora MySQL updates: 2018-06-04 (version 2.02.2) (Deprecated)

**Version:** 2.02.2

Aurora MySQL 2.02.2 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

When creating a new Aurora MySQL DB cluster, you can choose compatibility with either MySQL 5.7 or MySQL 5.6. When restoring a MySQL 5.6-compatible snapshot, you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

You can restore snapshots of Aurora MySQL 1.14\$1, 1.15\$1, 1.16\$1, 1.17\$1, 2.01\$1, and 2.02 into Aurora MySQL 2.02.2. You can also perform an in-place upgrade from Aurora MySQL 2.01\$1 or 2.02 to Aurora MySQL 2.02.2.

We don't allow in-place upgrade of Aurora MySQL 1.\$1 clusters into Aurora MySQL 2.02.2 or restore to Aurora MySQL 2.02.2 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.\$1 release.

The performance schema is disabled for this release of Aurora MySQL 5.7. Upgrade to Aurora 2.03 for performance schema support.

**Note**  
 This version is currently not available in the AWS GovCloud (US-West) [us-gov-west-1] and China (Beijing) [cn-north-1] regions. There will be a separate announcement once it is made available. 

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


 **Critical fixes:** 
+ [CVE-2016-3486](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3486)

## Comparison with Aurora MySQL 5.6


The following Amazon Aurora MySQL features are supported in Aurora MySQL 5.6, but these features are currently not supported in Aurora MySQL 5.7.
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

Currently, Aurora MySQL 2.01 does not support features added in Aurora MySQL version 1.16 and later. For information about Aurora MySQL version 1.16, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


Aurora MySQL 2.02.2 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.02.2 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

## CLI differences between Aurora MySQL 2.x and Aurora MySQL 1.x

+ The engine name for Aurora MySQL 2.x is `aurora-mysql`; the engine name for Aurora MySQL 1.x continues to be `aurora`.
+ The default parameter group for Aurora MySQL 2.x is `default.aurora-mysql5.7`; the default parameter group for Aurora MySQL 1.x continues to be `default.aurora5.6`.
+ The DB cluster parameter group family name for Aurora MySQL 2.x is `aurora-mysql5.7`; the DB cluster parameter group family name for Aurora MySQL 1.x continues to be `aurora5.6`.

Refer to the Aurora documentation for the full set of CLI commands and differences between Aurora MySQL 2.x and Aurora MySQL 1.x.

## Improvements

+ Fixed an issue where an Aurora Writer can occasionally restart when tracking Aurora Replica progress.
+ Fixed an issue where an Aurora Replica restarts or throws an error when a partitioned table is accessed after running index create or drop statements on the table on the Aurora Writer.
+ Fixed an issue where a table on an Aurora Replica is inaccessible while it is applying the changes caused by running ALTER table ADD/DROP column statements on the Aurora Writer.

# Aurora MySQL database engine updates 2018-05-03 (version 2.02) (Deprecated)
Aurora MySQL updates: 2018-05-03 (version 2.02) (Deprecated)

**Version:** 2.02

Aurora MySQL 2.02 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

When creating a new Aurora MySQL DB cluster, you can choose compatibility with either MySQL 5.7 or MySQL 5.6. When restoring a MySQL 5.6-compatible snapshot, you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

You can restore snapshots of Aurora MySQL 1.14\$1, 1.15\$1, 1.16\$1, 1.17\$1 and 2.01\$1 into Aurora MySQL 2.02. You can also perform an in-place upgrade from Aurora MySQL 2.01\$1 to Aurora MySQL 2.02.

We don't allow in-place upgrade of Aurora MySQL 1.x clusters into Aurora MySQL 2.02 or restore to Aurora MySQL 2.02 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.x release.

The performance schema is disabled for this release of Aurora MySQL 5.7. Upgrade to Aurora 2.03 for performance schema support.

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*.

## Comparison with Aurora MySQL 5.6


The following Amazon Aurora MySQL features are supported in Aurora MySQL 5.6, but these features are currently not supported in Aurora MySQL 5.7.
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

Currently, Aurora MySQL 2.01 does not support features added in Aurora MySQL version 1.16 and later. For information about Aurora MySQL version 1.16, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


Aurora MySQL 2.02 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.02 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

## CLI differences between Aurora MySQL 2.x and Aurora MySQL 1.x

+ The engine name for Aurora MySQL 2.x is `aurora-mysql`; the engine name for Aurora MySQL 1.x continues to be `aurora`.
+ The default parameter group for Aurora MySQL 2.x is `default.aurora-mysql5.7`; the default parameter group for Aurora MySQL 1.x continues to be `default.aurora5.6`.
+ The DB cluster parameter group family name for Aurora MySQL 2.x is `aurora-mysql5.7`; the DB cluster parameter group family name for Aurora MySQL 1.x continues to be `aurora5.6`.

Refer to the Aurora documentation for the full set of CLI commands and differences between Aurora MySQL 2.x and Aurora MySQL 1.x.

## Improvements

+ Fixed an issue where an Aurora Writer restarts when running INSERT statements and exploiting the Fast Insert optimization.
+ Fixed an issue where an Aurora Replica restarts when running ALTER DATABASE statements on the Aurora Replica.
+ Fixed an issue where an Aurora Replica restarts when running queries on tables that have just been dropped on the Aurora Writer.
+ Fixed an issue where an Aurora Replica restarts when setting `innodb_adaptive_hash_index` to `OFF` on the Aurora Replica.
+ Fixed an issue where an Aurora Replica restarts when running TRUNCATE TABLE queries on the Aurora Writer.
+ Fixed an issue where the Aurora Writer freezes in certain circumstances when running INSERT statements. On a multi-node cluster, this can result in a failover. 
+ Fixed a memory leak associated with setting session variables.
+ Fixed an issue where the Aurora Writer freezes in certain circumstances associated with purging undo for tables with generated columns.
+ Fixed an issue where the Aurora Writer can sometimes restart when binary logging is enabled.

## Integration of MySQL bug fixes

+ Left join returns incorrect results on the outer side (Bug \$122833364).

# Aurora MySQL database engine updates 2018-03-13 (version 2.01.1) (Deprecated)
Aurora MySQL updates: 2018-03-13 (version 2.01.1) (Deprecated)

**Version:** 2.01.1

Aurora MySQL 2.01.1 is generally available. Aurora MySQL 2.x versions are compatible with MySQL 5.7 and Aurora MySQL 1.x versions are compatible with MySQL 5.6.

When creating a new Aurora MySQL DB cluster, you can choose compatibility with either MySQL 5.7 or MySQL 5.6. When restoring a MySQL 5.6-compatible snapshot, you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

You can restore snapshots of Aurora MySQL 1.14\$1, 1.15\$1, 1.16\$1, and 1.17\$1 into Aurora MySQL 2.01.1.

We don't allow in-place upgrade of Aurora MySQL 1.x clusters into Aurora MySQL 2.01.1 or restore to Aurora MySQL 2.01.1 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.x release.

The performance schema is disabled for this release of Aurora MySQL 5.7. Upgrade to Aurora 2.03 for performance schema support.

## Comparison with Aurora MySQL 5.6


The following Amazon Aurora MySQL features are supported in Aurora MySQL 5.6, but these features are currently not supported in Aurora MySQL 5.7.
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

Currently, Aurora MySQL 2.01.1 does not support features added in Aurora MySQL version 1.16 and later. For information about Aurora MySQL version 1.16, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


Aurora MySQL 2.01.1 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.01.1 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

## CLI differences between Aurora MySQL 2.x and Aurora MySQL 1.x

+ The engine name for Aurora MySQL 2.x is `aurora-mysql`; the engine name for Aurora MySQL 1.x continues to be `aurora`.
+ The default parameter group for Aurora MySQL 2.x is `default.aurora-mysql5.7`; the default parameter group for Aurora MySQL 1.x continues to be `default.aurora5.6`.
+ The DB cluster parameter group family name for Aurora MySQL 2.x is `aurora-mysql5.7`; the DB cluster parameter group family name for Aurora MySQL 1.x continues to be `aurora5.6`.

Refer to the Aurora documentation for the full set of CLI commands and differences between Aurora MySQL 2.x and Aurora MySQL 1.x.

## Improvements

+ Fixed an issue with snapshot restore where Aurora-specific database privileges were created incorrectly when a MySQL 5.6-compatible snapshot was restored with MySQL 5.7 compatibility.
+ Added support for 1.17 snapshot restores.

# Aurora MySQL database engine updates 2018-02-06 (version 2.01) (Deprecated)
Aurora MySQL updates: 2018-02-06 (version 2.01) (Deprecated)

**Version:** 2.01

Aurora MySQL 2.01 is generally available. Going forward, Aurora MySQL 2.x versions will be compatible with MySQL 5.7 and Aurora MySQL 1.x versions will be compatible with MySQL 5.6. 

When creating a new Aurora MySQL DB cluster, including those restored from snapshots, you can choose compatibility with either MySQL 5.7 or MySQL 5.6.

You can restore snapshots of Aurora MySQL 1.14\$1, 1.15\$1, and 1.16\$1 into Aurora MySQL 2.01.

We don't allow in-place upgrade of Aurora MySQL 1.x clusters into Aurora MySQL 2.01 or restore to Aurora MySQL 2.01 from an Amazon S3 backup. We plan to remove these restrictions in a later Aurora MySQL 2.x release.

The performance schema is disabled for this release of Aurora MySQL 5.7. Upgrade to Aurora 2.03 for performance schema support.

## Comparison with Aurora MySQL 5.6


The following Amazon Aurora MySQL features are supported in Aurora MySQL 5.6, but these features are currently not supported in Aurora MySQL 5.7.
+ Asynchronous key prefetch (AKP). For more information, see [ Optimizing Aurora indexed join queries with asynchronous key prefetch](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.AKP) in the *Amazon Aurora User Guide*. 
+ Hash joins. For more information, see [ Optimizing large Aurora MySQL join queries with hash joins](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.BestPractices.html#Aurora.BestPractices.HashJoin) in the *Amazon Aurora User Guide*.
+ Native functions for synchronously invoking AWS Lambda functions. For more information, see [ Invoking a Lambda function with an Aurora MySQL native function](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Integrating.Lambda.html#AuroraMySQL.Integrating.NativeLambda) in the *Amazon Aurora User Guide*.
+ Scan batching. For more information, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).
+ Migrating data from MySQL using an Amazon S3 bucket. For more information, see [ Migrating data from MySQL by using an Amazon S3 bucket](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Migrating.ExtMySQL.html#AuroraMySQL.Migrating.ExtMySQL.S3) in the *Amazon Aurora User Guide*.

Currently, Aurora MySQL 2.01 does not support features added in Aurora MySQL version 1.16 and later. For information about Aurora MySQL version 1.16, see [Aurora MySQL database engine updates 2017-12-11 (version 1.16) (Deprecated)](AuroraMySQL.Updates.20171211.md).

## MySQL 5.7 compatibility


Aurora MySQL 2.01 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Aurora MySQL uses a native implementation of spatial indexing using z-order curves to deliver >20x better write performance and >10x better read performance than MySQL 5.7 for spatial datasets.

Aurora MySQL 2.01 does not currently support the following MySQL 5.7 features:
+ Global transaction identifiers (GTIDs). Aurora MySQL supports GTIDs in version 2.04 and higher.
+ Group replication plugin
+ Increased page size
+ InnoDB buffer pool loading at startup
+ InnoDB full-text parser plugin
+ Multisource replication
+ Online buffer pool resizing
+ Password validation plugin
+ Query rewrite plugins
+ Replication filtering
+ The `CREATE TABLESPACE` SQL statement
+ X Protocol

## CLI differences between Aurora MySQL 2.x and Aurora MySQL 1.x

+ The engine name for Aurora MySQL 2.x is `aurora-mysql`; the engine name for Aurora MySQL 1.x continues to be `aurora`.
+ The default parameter group for Aurora MySQL 2.x is `default.aurora-mysql5.7`; the default parameter group for Aurora MySQL 1.x continues to be `default.aurora5.6`.
+ The DB cluster parameter group family name for Aurora MySQL 2.x is `aurora-mysql5.7`; the DB cluster parameter group family name for Aurora MySQL 1.x continues to be `aurora5.6`.

Refer to the Aurora documentation for the full set of CLI commands and differences between Aurora MySQL 2.x and Aurora MySQL 1.x.