Aurora MySQL database engine updates 2025-12-16 (version 3.11.1, compatible with MySQL 8.0.43) - Amazon Aurora
Improvements
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Aurora MySQL database engine updates 2025-12-16 (version 3.11.1, compatible with MySQL 8.0.43)

Version: 3.11.1

Aurora MySQL 3.11.1 is generally available. Aurora MySQL 3.11 versions are compatible with MySQL 8.0.43. For more information on the community changes that have occurred, see MySQL 8.0 Release Notes.

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

You can perform an in-place upgrade leveraging Zero Downtime Patching (ZDP), restore a snapshot, or initiate a managed blue/green upgrade using Amazon RDS Blue/Green Deployments from any currently supported Aurora MySQL version 2 cluster into an Aurora MySQL version 3.11.1 cluster.

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

For troubleshooting information, see Troubleshooting for Aurora MySQL in-place upgrade in the Amazon Aurora User Guide.

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

Improvements

General improvements

  • Fixed an issue which can cause database cluster creates or restores to take a long time to complete.

  • Reduced CPU usage overhead while establishing Encryption in Transit between the database instance and the storage layer.

  • Fixed an issue which can cause some SQL statements to not get logged in the audit log.