AWS AmazonRDS documentation change
Summary
Added documentation for Aurora MySQL version 3 to 8.4 upgrade prechecks, including new sections for Community and Aurora-specific prechecks, updated references, and expanded structure to cover both v2-v3 and v3-v8.4 upgrade paths.
Security assessment
The changes focus on documenting version upgrade compatibility checks without addressing security vulnerabilities. While one precheck mentions replacing the deprecated validate_password plugin with a component, this is presented as a compatibility requirement rather than a security fix.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.upgrade-prechecks.md b/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.upgrade-prechecks.md index 9b5c52b1f..0f3f51673 100644 --- a//AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.upgrade-prechecks.md +++ b//AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.upgrade-prechecks.md @@ -7 +7 @@ -Precheck process for Aurora MySQLPrecheck log format for Aurora MySQLPrecheck log output examples for Aurora MySQLPrecheck performance for Aurora MySQLSummary of Community MySQL upgrade prechecksSummary of Aurora MySQL upgrade prechecks +Precheck process for Aurora MySQLPrecheck log format for Aurora MySQLPrecheck log output examples for Aurora MySQLPrecheck performance for Aurora MySQLSummary of Community MySQL upgrade prechecks for Aurora MySQL version 2 to version 3Summary of Aurora MySQL upgrade prechecks for Aurora MySQL version 2 to version 3Summary of Community MySQL upgrade prechecks for Aurora MySQL version 3 to version 8.4Summary of Aurora MySQL upgrade prechecks for Aurora MySQL version 3 to version 8.4 @@ -13 +13 @@ Upgrading MySQL from one major version to another, such as going from MySQL 5.7 -To assist you in identifying such incompatibilities, when upgrading from Aurora MySQL version 2 to version 3, Aurora runs upgrade compatibility checks (prechecks) automatically to examine objects in your database cluster and identify known incompatibilities that can block the upgrade from proceeding. For details about the Aurora MySQL prechecks, see [Precheck descriptions reference for Aurora MySQL](./AuroraMySQL.upgrade-prechecks.descriptions.html). The Aurora prechecks run in addition to those run by the Community MySQL [upgrade checker utility](https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-utilities-upgrade.html). +To assist you in identifying such incompatibilities, Aurora runs upgrade compatibility checks (prechecks) automatically to examine objects in your database cluster and identify known incompatibilities that can block the upgrade from proceeding. These prechecks run for all major version upgrades, including version 2 to version 3 and version 3 to version 8.4. For details about the Aurora MySQL prechecks, see [Precheck descriptions for upgrading Aurora MySQL version 2 to version 3](./AuroraMySQL.upgrade-prechecks.descriptions.html) and [Precheck descriptions for upgrading Aurora MySQL version 3 to version 8.4](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html). The Aurora prechecks run in addition to those run by the Community MySQL [upgrade checker utility](https://dev.mysql.com/doc/mysql-shell/8.0/en/mysql-shell-utilities-upgrade.html). @@ -44 +44 @@ Due to the nature of the prechecks, they analyze the objects in your database. T - * [Summary of Community MySQL upgrade prechecks](./AuroraMySQL.upgrade-prechecks.html#AuroraMySQL.upgrade-prechecks.community) + * [Summary of Community MySQL upgrade prechecks for Aurora MySQL version 2 to version 3](./AuroraMySQL.upgrade-prechecks.html#AuroraMySQL.upgrade-prechecks.community) @@ -46 +46 @@ Due to the nature of the prechecks, they analyze the objects in your database. T - * [Summary of Aurora MySQL upgrade prechecks](./AuroraMySQL.upgrade-prechecks.html#AuroraMySQL.upgrade-prechecks.ams) + * [Summary of Aurora MySQL upgrade prechecks for Aurora MySQL version 2 to version 3](./AuroraMySQL.upgrade-prechecks.html#AuroraMySQL.upgrade-prechecks.ams) @@ -48 +48,5 @@ Due to the nature of the prechecks, they analyze the objects in your database. T - * [Precheck descriptions reference for Aurora MySQL](./AuroraMySQL.upgrade-prechecks.descriptions.html) + * [Summary of Community MySQL upgrade prechecks for Aurora MySQL version 3 to version 8.4](./AuroraMySQL.upgrade-prechecks.html#AuroraMySQL.upgrade-prechecks.community-v3-to-v84) + + * [Summary of Aurora MySQL upgrade prechecks for Aurora MySQL version 3 to version 8.4](./AuroraMySQL.upgrade-prechecks.html#AuroraMySQL.upgrade-prechecks.ams-v3-to-v84) + + * [Precheck descriptions for upgrading Aurora MySQL version 2 to version 3](./AuroraMySQL.upgrade-prechecks.descriptions.html) @@ -65,0 +70,18 @@ Due to the nature of the prechecks, they analyze the objects in your database. T + * [Precheck descriptions for upgrading Aurora MySQL version 3 to version 8.4](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html) + + * [Errors](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html#precheck-v84-errors) + + * [MySQL prechecks that report errors](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html#precheck-v84-errors.mysql) + + * [Aurora MySQL prechecks that report errors](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html#precheck-v84-errors.aurora) + + * [Warnings](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html#precheck-v84-warnings) + + * [MySQL prechecks that report warnings](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html#precheck-v84-warnings.mysql) + + * [Aurora MySQL prechecks that report warnings](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html#precheck-v84-warnings.aurora) + + * [Notices](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html#precheck-v84-notices) + + * [Errors, warnings, or notices](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html#precheck-v84-all) + @@ -77 +99 @@ For snapshot-restore upgrades, the precheck runs during the restore process. If -For more information, see [Finding the reasons for Aurora MySQL major version upgrade failures](./AuroraMySQL.Upgrading.failure-events.html) and [Precheck descriptions reference for Aurora MySQL](./AuroraMySQL.upgrade-prechecks.descriptions.html). +For more information, see [Finding the reasons for Aurora MySQL major version upgrade failures](./AuroraMySQL.Upgrading.failure-events.html) and [Precheck descriptions for upgrading Aurora MySQL version 2 to version 3](./AuroraMySQL.upgrade-prechecks.descriptions.html). @@ -121 +143 @@ For more information, see this example. - * `documentationLink` – Where applicable, a link to relevant Aurora MySQL or MySQL documentation is noted here. For more information, see [Precheck descriptions reference for Aurora MySQL](./AuroraMySQL.upgrade-prechecks.descriptions.html). + * `documentationLink` – Where applicable, a link to relevant Aurora MySQL or MySQL documentation is noted here. For more information, see [Precheck descriptions for upgrading Aurora MySQL version 2 to version 3](./AuroraMySQL.upgrade-prechecks.descriptions.html). @@ -150 +172 @@ For more information, see this example. -The following examples show the precheck log output that you might see. For details of the prechecks that are run, see [Precheck descriptions reference for Aurora MySQL](./AuroraMySQL.upgrade-prechecks.descriptions.html). +The following examples show the precheck log output that you might see. For details of the prechecks that are run, see [Precheck descriptions for upgrading Aurora MySQL version 2 to version 3](./AuroraMySQL.upgrade-prechecks.descriptions.html). @@ -322 +344 @@ For more information, see [How the Aurora MySQL in-place major version upgrade w -## Summary of Community MySQL upgrade prechecks +## Summary of Community MySQL upgrade prechecks for Aurora MySQL version 2 to version 3 @@ -375 +397 @@ For more information, see [ The utf8mb3 character set (3-byte UTF-8 unicode enco -For details of the prechecks that are run, see [Precheck descriptions reference for Aurora MySQL](./AuroraMySQL.upgrade-prechecks.descriptions.html). +For details of the prechecks that are run, see [Precheck descriptions for upgrading Aurora MySQL version 2 to version 3](./AuroraMySQL.upgrade-prechecks.descriptions.html). @@ -379 +401 @@ For more information about upgrading to MySQL 8.0, see [Upgrading MySQL](https:/ -## Summary of Aurora MySQL upgrade prechecks +## Summary of Aurora MySQL upgrade prechecks for Aurora MySQL version 2 to version 3 @@ -418 +440,35 @@ A larger prefix length was allowed in MySQL 5.7 using the `innodb_large_prefix` -For details of the prechecks that are run, see [Precheck descriptions reference for Aurora MySQL](./AuroraMySQL.upgrade-prechecks.descriptions.html). +For details of the prechecks that are run, see [Precheck descriptions for upgrading Aurora MySQL version 2 to version 3](./AuroraMySQL.upgrade-prechecks.descriptions.html). + +## Summary of Community MySQL upgrade prechecks for Aurora MySQL version 3 to version 8.4 + +The following is a general list of incompatibilities between MySQL 8.0 and 8.4: + + * There must be no partitioned tables that use `KEY` partitioning on columns with prefix key indexes. Prefix indexes are ignored by the partition function and are not allowed as of MySQL 8.4.0. + + * There must be no columns of type `FLOAT` or `DOUBLE` with the `AUTO_INCREMENT` flag set. This is no longer supported in MySQL 8.4. + + * Foreign key constraints should reference a full unique or primary key index on the parent table. Starting with MySQL 8.4.0, creating a foreign key that references a non-unique or partial parent index is forbidden by default. + + + + +For details of the prechecks that are run, see [Precheck descriptions for upgrading Aurora MySQL version 3 to version 8.4](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html). + +For more information about upgrading to MySQL 8.4, see [Upgrading MySQL](https://dev.mysql.com/doc/refman/8.4/en/upgrading.html) in the MySQL 8.4 documentation. For a general description of changes in MySQL 8.4, see [What is new in MySQL 8.4](https://dev.mysql.com/doc/refman/8.4/en/mysql-nutshell.html) in the MySQL 8.4 documentation. + +## Summary of Aurora MySQL upgrade prechecks for Aurora MySQL version 3 to version 8.4 + +Aurora MySQL has its own specific requirements when upgrading from version 3 to version 8.4, including the following: + + * There must be no plugins installed that are unsupported in Aurora MySQL version 8.4. Uninstall any unsupported plugins before upgrading. + + * There must be no MySQL components installed that are unsupported in Aurora MySQL version 8.4. Uninstall any unsupported components before upgrading. + + * Replace the deprecated `validate_password` plugin with the `component_validate_password` component. The `validate_password` plugin is deprecated in Aurora MySQL version 8.4 and will be removed in a future release. For more information, see [Using the validate_password component](./AuroraMySQL.PasswordPolicies.html#AuroraMySQL.PasswordPolicies.validate-password). + + * All objects in the `sys` schema must have the correct object types. Mismatches can occur if the schema was manually modified. For more information, see [auroraUpgradeCheckForSysSchemaObjectTypeMismatch](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html#v84-auroraUpgradeCheckForSysSchemaObjectTypeMismatch). + + + + +For details of the prechecks that are run, see [Precheck descriptions for upgrading Aurora MySQL version 3 to version 8.4](./AuroraMySQL.upgrade-prechecks-v3-to-v84.descriptions.html). @@ -428 +484 @@ Upgrading the major version of an Aurora MySQL DB cluster -Precheck descriptions reference for Aurora MySQL +Precheck descriptions for upgrading Aurora MySQL version 2 to version 3