AWS AmazonRDS documentation change
Summary
Updated Aurora MySQL version documentation to include new simplified versioning format starting with version 8.4, added examples for new format, and clarified version mapping.
Security assessment
Changes only describe version number formatting updates and MySQL compatibility mappings. No security vulnerabilities, patches, or security features are mentioned. The existing reference to security vulnerabilities (CVE list) remains unchanged.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Versions.md b/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Versions.md index 515036891..ba59393e1 100644 --- a//AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Versions.md +++ b//AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.Updates.Versions.md @@ -26 +26 @@ When you perform administrative tasks using the AWS Management Console, AWS CLI, -Starting with Aurora MySQL version 2, Aurora engine versions have the following syntax. +For Aurora MySQL version 2 and version 3, Aurora engine versions have the following syntax. @@ -42,0 +43,10 @@ For example, the engine versions for Aurora MySQL 3.04.0 and 2.11.2 are the foll +Starting with Aurora MySQL version 8.4, the engine version format is simplified. The version number uses a ``major-version`.`minor-version`` scheme, where the major version (such as `8.4`) represents MySQL compatibility and the minor version represents the feature and bug fix release. There is no separate patch level visible to customers, and the Aurora version number directly matches the MySQL compatibility version without a separate internal-to-external version mapping. + + + mysql-major-version.mysql_aurora.major-version.minor-version + +For example, the engine version for Aurora MySQL 8.4.7 is the following. + + + 8.4.mysql_aurora.8.4.7 + @@ -45 +55 @@ For example, the engine versions for Aurora MySQL 3.04.0 and 2.11.2 are the foll -There isn't a one-to-one correspondence between community MySQL versions and the Aurora MySQL 2.x versions. For Aurora MySQL version 3, there is a more direct mapping. To check which bug fixes and new features are in a particular Aurora MySQL release, see [ Database engine updates for Amazon Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.30Updates.html) and [ Database engine updates for Amazon Aurora MySQL version 2](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.20Updates.html) in the _Release Notes for Aurora MySQL_. For a chronological list of new features and releases, see [Document history](./WhatsNew.html). To check the minimum version required for a security-related fix, see [ Security vulnerabilities fixed in Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.CVE_list.html)in the _Release Notes for Aurora MySQL_. +There isn't a one-to-one correspondence between community MySQL versions and the Aurora MySQL 2.x versions. For Aurora MySQL version 3, there is a more direct mapping. Starting with Aurora MySQL version 8.4, the Aurora version number directly matches the MySQL compatibility version. To check which bug fixes and new features are in a particular Aurora MySQL release, see [ Database engine updates for Amazon Aurora MySQL version 3](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.30Updates.html) and [ Database engine updates for Amazon Aurora MySQL version 2](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.Updates.20Updates.html) in the _Release Notes for Aurora MySQL_. For a chronological list of new features and releases, see [Document history](./WhatsNew.html). To check the minimum version required for a security-related fix, see [ Security vulnerabilities fixed in Aurora MySQL](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraMySQLReleaseNotes/AuroraMySQL.CVE_list.html)in the _Release Notes for Aurora MySQL_. @@ -57 +67 @@ For Aurora clusters managed through CloudFormation, this change in the `EngineVe -The Aurora version numbers that you can retrieve in your application using SQL queries use the format ``<major version>`.`<minor version>`.`<patch version>``. You can get this version number for any DB instance in your Aurora MySQL cluster by querying the `AURORA_VERSION` system variable. To get this version number, use one of the following queries. +The Aurora version numbers that you can retrieve in your application using SQL queries use the format ``<major version>`.`<minor version>`.`<patch version>`` for version 2 and version 3. For version 8.4 and higher, the format is ``<major version>`.`<minor version>`` (for example, `8.4.7`), where the major version such as `8.4` represents MySQL compatibility. You can get this version number for any DB instance in your Aurora MySQL cluster by querying the `AURORA_VERSION` system variable. To get this version number, use one of the following queries. @@ -64 +74 @@ The Aurora version numbers that you can retrieve in your application using SQL q -Those queries produce output similar to the following. +For version 2 and version 3, the output looks similar to the following. @@ -71,0 +82,11 @@ Those queries produce output similar to the following. + +------------------+------------------+ + + +For version 8.4 and higher, the output uses the simplified numbering scheme. + + + mysql> select aurora_version(), @@aurora_version; + +------------------+------------------+ + | aurora_version() | @@aurora_version | + +------------------+------------------+ + | 8.4.7 | 8.4.7 |