AWS AmazonRDS documentation change
Summary
Updated documentation to include upgrading from Aurora MySQL version 3 to version 8.4. Added new sections for prechecks, upgrade procedures, and security considerations for the new upgrade path. Updated supported upgrade paths and details for Aurora serverless and global databases.
Security assessment
The change adds a reference to security considerations during version upgrades ('For security considerations...see Security considerations for upgrading') but doesn't address any specific vulnerability. It's routine documentation for new version support.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.md b/AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.md index 0414a9514..00b1267f7 100644 --- a//AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.md +++ b//AmazonRDS/latest/AuroraUserGuide/AuroraMySQL.mysql80-upgrade-procedure.md @@ -7 +7 @@ -Upgrading from Aurora MySQL version 2 to version 3Aurora MySQL major version upgrade pathsHow the Aurora MySQL in-place major version upgrade worksPlanning a major version upgrade for an Aurora MySQL cluster +Upgrading from Aurora MySQL version 3 to version 8.4Upgrading from Aurora MySQL version 2 to version 3Aurora MySQL major version upgrade pathsHow the Aurora MySQL in-place major version upgrade worksPlanning a major version upgrade for an Aurora MySQL cluster @@ -11 +11 @@ Upgrading from Aurora MySQL version 2 to version 3Aurora MySQL major version upg -In an Aurora MySQL version number such as 3.04.1, the 3 represents the major version. Aurora MySQL version 2 is compatible with MySQL 5.7. Aurora MySQL version 3 is compatible with MySQL 8.0. +For Aurora MySQL version 2 and version 3, in a version number such as 3.04.1, the 3 represents the major version. Starting with version 8.4, in a version number such as 8.4.7, the 8.4 represents the major version. Aurora MySQL version 2 is compatible with MySQL 5.7. Aurora MySQL version 3 is compatible with MySQL 8.0. Aurora MySQL version 8.4 is compatible with MySQL 8.4. @@ -16,0 +17,2 @@ Upgrading between major versions requires more extensive planning and testing th + * [Upgrading from Aurora MySQL version 3 to version 8.4](./AuroraMySQL.Updates.MajorVersionUpgrade.html#AuroraMySQL.Updates.MajorVersionUpgrade.3to84) + @@ -39 +41,5 @@ Upgrading between major versions requires more extensive planning and testing th - * [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) + + * [Summary of Aurora MySQL upgrade prechecks for Aurora MySQL version 2 to version 3](./AuroraMySQL.upgrade-prechecks.html#AuroraMySQL.upgrade-prechecks.ams) + + * [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) @@ -41 +47 @@ Upgrading between major versions requires more extensive planning and testing th - * [Summary of Aurora MySQL upgrade prechecks](./AuroraMySQL.upgrade-prechecks.html#AuroraMySQL.upgrade-prechecks.ams) + * [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) @@ -43 +49 @@ Upgrading between major versions requires more extensive planning and testing th - * [Precheck descriptions reference for Aurora MySQL](./AuroraMySQL.upgrade-prechecks.descriptions.html) + * [Precheck descriptions for upgrading Aurora MySQL version 2 to version 3](./AuroraMySQL.upgrade-prechecks.descriptions.html) @@ -60,0 +67,18 @@ Upgrading between major versions requires more extensive planning and testing th + * [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) + @@ -83,0 +108,4 @@ Upgrading between major versions requires more extensive planning and testing th +## Upgrading from Aurora MySQL version 3 to version 8.4 + +For security considerations and new features when upgrading from Aurora MySQL version 3 to Aurora MySQL version 8.4, see [Security considerations for upgrading from Aurora MySQL version 3 to version 8.4](./AuroraMySQL.Upgrade-v3-v84-security.html). + @@ -116,3 +144,4 @@ Aurora MySQL provisioned cluster, version 2 | Yes | In-place upgrade is suppor -Aurora MySQL provisioned cluster, version 3 | Not applicable | Use a minor version upgrade procedure to upgrade between Aurora MySQL version 3 versions. -Aurora serverless cluster | Not applicable | Aurora serverless is supported for Aurora MySQL only on version 3. -Cluster in an Aurora global database | Yes | To upgrade Aurora MySQL from version 2 to version 3, follow the [procedure for doing an in-place upgrade](./AuroraMySQL.Upgrading.Procedure.html) for clusters in an Aurora global database. Perform the upgrade on the global cluster. Aurora upgrades the primary cluster and all the secondary clusters in the global database at the same time. If you use the AWS CLI or RDS API, call the `modify-global-cluster` command or `ModifyGlobalCluster` operation instead of `modify-db-cluster` or `ModifyDBCluster`. You can perform an in-place upgrade from Aurora MySQL version 2 to version 3 only if the `lower_case_table_names` parameter is set to default and you reboot your global database. For more information, see [Major version upgrades](./aurora-global-database-upgrade.html#aurora-global-database-upgrade.major). +Aurora MySQL provisioned cluster, version 3 | Yes | In-place upgrade is supported for MySQL 8.0–compatible Aurora MySQL clusters. For information about upgrading to Aurora MySQL version 8.4, see Planning a major version upgrade for an Aurora MySQL cluster and [How to perform an in-place upgrade](./AuroraMySQL.Upgrading.Procedure.html). +Aurora MySQL provisioned cluster, version 8.4 | Not applicable | Use a minor version upgrade procedure to upgrade between Aurora MySQL version 8.4 minor versions. +Aurora serverless cluster | Yes | Aurora serverless is supported for Aurora MySQL on version 3 and higher. +Cluster in an Aurora global database | Yes | To upgrade Aurora MySQL in an Aurora global database (version 2 to version 3, or version 3 to version 8.4), follow the [procedure for doing an in-place upgrade](./AuroraMySQL.Upgrading.Procedure.html) for clusters in an Aurora global database. Perform the upgrade on the global cluster. Aurora upgrades the primary cluster and all the secondary clusters in the global database at the same time. If you use the AWS CLI or RDS API, call the `modify-global-cluster` command or `ModifyGlobalCluster` operation instead of `modify-db-cluster` or `ModifyDBCluster`. You can perform an in-place major version upgrade only if the `lower_case_table_names` parameter is set to default and you reboot your global database. For more information, see [Major version upgrades](./aurora-global-database-upgrade.html#aurora-global-database-upgrade.major). @@ -158 +187 @@ This snapshot is a manual snapshot. However, Aurora can create it and continue w - * Aurora uses the writer DB instance to upgrade your data to MySQL 5.7-compatible format. During this stage, Aurora modifies the system tables and performs other conversions that affect the data in your cluster volume. In particular, Aurora upgrades the partition metadata in the system tables to be compatible with the MySQL 5.7 partition format. This stage can take a long time if the tables in your cluster have a large number of partitions. + * Aurora uses the writer DB instance to upgrade your data to the Aurora MySQL target version compatible format. During this stage, Aurora modifies the system tables and performs other conversions that affect the data in your cluster volume. For version 2 to version 3 upgrades, in particular, Aurora upgrades the partition metadata in the system tables to be compatible with the MySQL 8.0 partition format. This stage can take a long time if the tables in your cluster have a large number of partitions. @@ -171 +200,3 @@ If any errors occur during this stage, you can find the details in the MySQL err -To help you decide the right time and approach to upgrade, you can learn the differences between Aurora MySQL version 3 and your current environment: +To help you decide the right time and approach to upgrade, you can learn the differences between the target Aurora MySQL version and your current environment: + +**Upgrading from Aurora MySQL version 2 to version 3** @@ -184 +215,14 @@ To help you decide the right time and approach to upgrade, you can learn the dif -You can also find more MySQL-specific upgrade considerations and tips in [Changes in MySQL 8.0](https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html) in the _MySQL Reference Manual_. For example, you can use the command `mysqlcheck --check-upgrade` to analyze your existing Aurora MySQL databases and identify potential upgrade issues. +**Upgrading from Aurora MySQL version 3 to version 8.4** + + * If you're converting from RDS for MySQL 8.4 or MySQL 8.4 Community Edition, see [Comparing Aurora MySQL version 8.4 and MySQL 8.4 Community Edition](./AuroraMySQL.Compare-v84-community.html). + + * If you're upgrading from Aurora MySQL version 3, RDS for MySQL 8.0, or community MySQL 8.0, see [Comparing Aurora MySQL version 3 and Aurora MySQL version 8.4](./AuroraMySQL.Compare-v3-v84.html). + + * Create new MySQL 8.4-compatible versions of any custom parameter groups. Apply any necessary custom parameter values to the new parameter groups. Consult [Parameter changes for Aurora MySQL version 8.4](./AuroraMySQL.Compare-v3-v84.html#AuroraMySQL.Compare-v3-v84.parameters) to learn about parameter changes. + + * Review your Aurora MySQL version 3 database schema and object definitions for the usage of new or changed reserved keywords introduced in MySQL 8.4 Community Edition. Do so before you upgrade. For more information, see [MySQL 8.4 New Keywords and Reserved Words](https://dev.mysql.com/doc/mysqld-version-reference/en/keywords-8-4.html#keywords-new-in-8-4) in the MySQL documentation. + + + + +You can also find more MySQL-specific upgrade considerations and tips in [Changes in MySQL 8.0](https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html) and [Changes in MySQL 8.4](https://dev.mysql.com/doc/refman/8.4/en/upgrading-from-previous-series.html) in the _MySQL Reference Manual_. For example, you can use the command `mysqlcheck --check-upgrade` to analyze your existing Aurora MySQL databases and identify potential upgrade issues.