Amazon Aurora
User Guide for Aurora (API Version 2014-10-31)

Amazon Aurora MySQL Database Engine Updates 2018-08-23

Version: 2.02.3

Amazon Aurora MySQL 2.02.3 is generally available. Please note that 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 have the option of choosing compatibility with either MySQL 5.7 or MySQL 5.6. When restoring a MySQL 5.6-compatible snapshot, you have the option of choosing compatibility with either MySQL 5.7 or MySQL 5.6.

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

We do not allow in-place upgrade of Aurora MySQL 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.* 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 regions AWS GovCloud (US-West) [us-gov-west-1] and China (Beijing) [cn-north-1]. There will be a separate announcement once it is made available.

Should you have any questions or concerns, the AWS Support Team is available on the community forums and through AWS Premium Support. For more information, see Maintaining an Amazon Aurora DB Cluster.

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.

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 Amazon Aurora MySQL Database Engine Updates 2017-12-11.

MySQL 5.7 compatibility

Amazon Aurora MySQL 2.01 is wire-compatible with MySQL 5.7 and includes features such as JSON support, spatial indexes, and generated columns. Amazon 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.

Amazon Aurora MySQL 2.01 does not currently support the following MySQL 5.7 features:

  • Global transaction identifiers (GTIDs)

  • 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 engine version for Aurora MySQL 2.x is 5.7.12; the engine version for Aurora MySQL 1.x continues to be 5.6.10ann.

  • 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 may 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 may restart when converting a point query for geospatial to a search range.