For certain critical fixes, Amazon might perform a managed upgrade to a patch level You can choose whether to apply such patches to DB clusters Patch levels don't include any new features. Way, the cluster doesn't need to be upgraded again for a long time.ĭuring the lifetime of an Aurora MySQL LTS release, new patch levels introduce fixes to important issues. When a DBĬluster that's on an LTS release is required to upgrade, Aurora upgrades it to the next LTS release. Aurora supports each LTS release for at least three years after that release becomes available. Releases can stay on the same version longer and undergo fewer upgrade cycles than clusters that use non-LTS Upgrade your cluster before the support period ends, or Aurora can automatically upgrade it for you when itsĪurora MySQL version is no longer supported.Īurora designates certain Aurora MySQL versions as long-term support (LTS) releases. After this period, you must upgrade any clusters that use that version. Aurora MySQL long-term support (LTS) releasesĮach new Aurora MySQL version remains available for a certain amount of time for you to use when you create or The version numbers that the console, CLI, and RDS API return by using the techniques described in Checking or specifying Aurora MySQL engine versions through AWS are typically moreĭescriptive. Mysql> select aurora_version(), aurora_version() | | This change helps you to specify and check the precise Aurora MySQL versions, without the need toĬonnect to the cluster or run any SQL commands. Upgrading the clusterĬhanges the displayed value. In Aurora MySQL version 2 and higher, the engine version in the AWS Management Console also includes the Aurora version. The EngineVersion parameter when you run the RDS API operations CreateDBCluster and ModifyDBCluster. engine-version option when you run the AWS CLI commands create-db-cluster and modify-db-cluster. You specify the Aurora MySQL engine version in some AWS CLI commands and RDS API operations. Security-related fix, see Security vulnerabilities fixed inĪurora MySQLin the Release Notes for Aurora MySQL. To check the minimum version required for a For a chronological list of new featuresĪnd releases, see Document history. To check which bug fixes and new features are in a particular Aurora MySQL release,Įngine updates for Amazon Aurora MySQL version 3 and Database engine updates forĪmazon Aurora MySQL version 2 in the Release Notes for Aurora MySQL. Version 3, there is a more direct mapping. There isn't a one-to-one correspondence between community MySQL versions and the Aurora MySQL 2.x versions. You can refer to release notes of the specific 3.x version to find the correspondingįor example, the engine versions for Aurora MySQL 3.02.0 and 2.03.2 are the following. Wire-compatible with MySQL 8.0.23 onwards.
In these cases, the feature undergoes fine-tuning and is made public in a later patch level.Īll 2.x Aurora MySQL engine versions are wire-compatible with Community MySQL 5.7.12. Occasionally, a new feature is incorporated into a minor version but not made visible The patch level begins at 0 for each minor version, and represents the set of subsequent bugįixes that apply to the minor version. The minor version represents the feature release within theĢ.x or 3.x series. Represent Aurora MySQL compatible with MySQL 5.7 or 8.0, respectively. Version, the Aurora MySQL minor version, and the patch level. The aurora-mysql-version is a dotted value with three parts: the Aurora MySQL major Represents the version of the client protocol and general level of MySQL feature support for the corresponding Aurora MySQL The mysql-major-version- portion is 5.7 or 8.0.
0 kommentar(er)
