The new major version, Aurora MySQL 8.4, has been released!
This is Yuta Kikai (@fat47) from the Service Reliability Group (SRG) of the Media Management Division.
#SRGThe Service Reliability Group primarily provides comprehensive support for the infrastructure surrounding our media services, focusing on improving existing services, launching new ones, and contributing to open-source software (OSS).
This article summarizes the newly released Aurora MySQL 8.4.
I hope this is of some help.
Aurora MySQL 8.4 suddenly appeared.Here are some points I noticed that differed from Aurora MySQL version 3.Enable require_secure_transport by defaultChanging the default value of temptable_max_mmapChanging the default authentication plugin for the master userPlease note the standard support period.Future release rules for Aurora MySQL engine versionsIn conclusion
Aurora MySQL 8.4 suddenly appeared.
The next major version of Aurora MySQL version 3 will be released on May 21, 2026 (May 22 in Japan time).Aurora MySQL version 8.4.7 It has been released.
The naming convention has changed from the previous Aurora MySQL version 2 (MySQL 5.7 compatible) and Aurora MySQL version 3 (MySQL 8.0 compatible). It appears that instead of being called Aurora MySQL version 4, it now uses the same naming convention as MySQL 8.4.
Here are some points I noticed that differed from Aurora MySQL version 3.
The differences from version 3 are summarized on the following page.
Here are a few excerpts that caught my attention.
Enable require_secure_transport by default
This requires you to connect using an encrypted connection.
| version | Default value |
|---|---|
| version 3 | OFF |
| version 8.4.7 | ON |
If you try to connect directly using mysql-client, you will get the following error:
—You can connect by adding the SSL option.
Changing the default value of temptable_max_mmap
The default value has changed from being fixed at 1 GiB to being dynamically set based on the storage allocated to the cluster.
| version | Default value |
|---|---|
| version 3 | 1 GiB ( 1073741824) |
| version 8.4.7 | LEAST(4294967296, {AllocatedStorage*3/100}) |
Changing the default authentication plugin for the master user
Similar to the changes from MySQL 8.0 to MySQL 8.4, the default authentication plugin has been changed.
Make sure that the connecting client/driver supports caching_sha2_password.
| version | Default value |
|---|---|
| version 3 | mysql_native_password |
| version 8.4.7 | caching_sha2_password |
Please note the standard support period.
The standard support period is summarized on the following page.
[Note] The standard support period for version 8.4.7 is until November 2027, which is shorter than the support period for v3.10 (LTS) until April 2028.
Currently, version 8.4.7 is not an LTS (Long-Term Support) version, so its support period is approximately one and a half years.
First, let's proceed with the testing so that we can migrate once the LTS version of 8.4 is released.
Future release rules for Aurora MySQL engine versions
The AWS blog post mentioned above published the Aurora version update schedule.
Regarding Aurora MySQL,
- Minor version
- Within 3 months of the community edition release
- Major version
<major>.1
- Aurora LTS
- Within 12 months of Aurora's major version GA
In other words,Aurora MySQL 8.4 LTS will be released within a year from today.It seems so.
In conclusion
The long-awaited new major version of Aurora MySQL has finally been released!
We've already confirmed that this version can be specified as the target for in-place upgrades and RDS Blue/Green upgrades, so you can try it out right away.
It has also been announced that an LTS version will be released within a year, so let's start testing it out!
If you are interested in SRG, please contact us here.