AWS AmazonRDS documentation change
Summary
Removed extensive documentation for Aurora Serverless v1 cloning capabilities, limitations, and CLI parameters. Updated references to focus on Aurora Serverless v2 and provisioned clusters. Removed sections about cloning between different engine modes (Serverless v1 and provisioned).
Security assessment
The changes are feature deprecation updates removing Aurora Serverless v1 documentation. No security vulnerabilities, patches, or security feature additions are mentioned. The removal of the note about Aurora Serverless v1 clusters always being encrypted and encryption requirements for cloning is part of the feature deprecation, not a security fix.
Diff
diff --git a/AmazonRDS/latest/AuroraUserGuide/Aurora.Managing.Clone.md b/AmazonRDS/latest/AuroraUserGuide/Aurora.Managing.Clone.md index 4b690b4d2..6dea74434 100644 --- a//AmazonRDS/latest/AuroraUserGuide/Aurora.Managing.Clone.md +++ b//AmazonRDS/latest/AuroraUserGuide/Aurora.Managing.Clone.md @@ -75,14 +74,0 @@ Aurora cloning currently has the following limitations: - * For Aurora Serverless v1: - - * You can create a provisioned clone from an Aurora Serverless v1 DB cluster. - - * You can create an Aurora Serverless v1 clone from an Aurora Serverless v1 or provisioned DB cluster. - - * You can't create an Aurora Serverless v1 clone from an unencrypted, provisioned Aurora DB cluster. - - * Cross-account cloning currently doesn't support cloning Aurora Serverless v1 DB clusters. For more information, see [Limitations of cross-account cloning](./Aurora.Managing.Clone.Cross-Account.html#Aurora.Managing.Clone.CrossAccount.Limitations). - - * A cloned Aurora Serverless v1 DB cluster has the same behavior and limitations as any Aurora Serverless v1 DB cluster. For more information, see [Using Amazon Aurora Serverless v1](./aurora-serverless.html). - - * Aurora Serverless v1 DB clusters are always encrypted. When you clone an Aurora Serverless v1 DB cluster into a provisioned Aurora DB cluster, the provisioned Aurora DB cluster is encrypted. You can choose the encryption key, but you can't disable the encryption. To clone from a provisioned Aurora DB cluster to an Aurora Serverless v1, you must start with an encrypted provisioned Aurora DB cluster. - @@ -165,5 +151 @@ The Create clone page opens, where you can configure **Settings** , **Connectivi - 5. For Aurora Serverless v1 DB clusters, choose **Provisioned** or **Serverless** for **Capacity type**. - -You can choose **Serverless** only if the source Aurora DB cluster is an Aurora Serverless v1 DB cluster or is a provisioned Aurora DB cluster that is encrypted. - - 6. For Aurora Serverless v2 or provisioned DB clusters, choose either **Aurora I/O-Optimized** or **Aurora Standard** for **Cluster storage configuration**. + 5. For Aurora Serverless v2 or provisioned DB clusters, choose either **Aurora I/O-Optimized** or **Aurora Standard** for **Cluster storage configuration**. @@ -173 +155 @@ For more information, see [Storage configurations for Amazon Aurora DB clusters] - 7. Choose the DB instance size or DB cluster capacity: + 6. Choose the DB instance size or DB cluster capacity: @@ -181 +163 @@ You can accept the provided setting, or you can use a different DB instance clas - * For an Aurora Serverless v1 or Aurora Serverless v2 clone, choose the **Capacity settings**. + * For an Aurora Serverless v2 clone, choose the **Capacity settings**. @@ -187 +169 @@ You can accept the provided settings, or you can change them for your clone. - 8. Choose other settings as needed for your clone. To learn more about Aurora DB cluster and instance settings, see [Creating an Amazon Aurora DB cluster](./Aurora.CreateInstance.html). + 7. Choose other settings as needed for your clone. To learn more about Aurora DB cluster and instance settings, see [Creating an Amazon Aurora DB cluster](./Aurora.CreateInstance.html). @@ -189 +171 @@ You can accept the provided settings, or you can change them for your clone. - 9. Choose **Create clone**. + 8. Choose **Create clone**. @@ -228 +210 @@ Use the `[restore-db-cluster-to-point-in-time](https://docs.aws.amazon.com/cli/l - * Use the `[restore-db-cluster-to-point-in-time](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-cluster-to-point-in-time.html)` CLI command. Specify values for the following parameters. In this typical case, the clone uses the same engine mode as the original cluster, either provisioned or Aurora Serverless v1. + * Use the `[restore-db-cluster-to-point-in-time](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-cluster-to-point-in-time.html)` CLI command. Specify values for the following parameters. In this typical case, the clone uses the same engine mode as the original cluster, either provisioned or Aurora Serverless v2. @@ -296,51 +277,0 @@ This example also includes the `--serverless-v2-scaling-configuration` option wh -###### To create a clone with a different engine mode from the source Aurora DB cluster - - * This procedure only applies to older engine versions that support Aurora Serverless v1. Suppose that you have an Aurora Serverless v1 cluster and you want to create a clone that's a provisioned cluster. In that case, use the `[restore-db-cluster-to-point-in-time](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-cluster-to-point-in-time.html)` CLI command and specify values similar parameter values as in the previous example, plus these additional parameters: - - * `--engine-mode` – Use this parameter only to create clones that are of a different engine mode from the source Aurora DB cluster. This parameter only applies to the older engine versions that support Aurora Serverless v1. Choose the value to pass with `--engine-mode` as follows: - - * Use `--engine-mode provisioned` to create a provisioned Aurora DB cluster clone from an Aurora Serverless DB cluster. - -###### Note - -If you intend to use Aurora Serverless v2 with a cluster that was cloned from Aurora Serverless v1, you still specify the engine mode for the clone as `provisioned`. Then you perform additional upgrade and migration steps afterward. - - * Use `--engine-mode serverless` to create an Aurora Serverless v1 clone from a provisioned Aurora DB cluster. When you specify the `serverless` engine mode, you can also choose the `--scaling-configuration`. - - * `--scaling-configuration` – (Optional) Use with `--engine-mode serverless` to configure the minimum and maximum capacity for an Aurora Serverless v1 clone. If you don't use this parameter, Aurora creates an Aurora Serverless v1 clone using the default Aurora Serverless v1 capacity values for the DB engine. - - - - -The following example creates a provisioned clone named `my-clone`, from an Aurora Serverless v1 DB cluster named `my-source-cluster`. - -For Linux, macOS, or Unix: - - - aws rds restore-db-cluster-to-point-in-time \ - --source-db-cluster-identifier my-source-cluster \ - --db-cluster-identifier my-clone \ - --engine-mode provisioned \ - --restore-type copy-on-write \ - --use-latest-restorable-time - - -For Windows: - - - aws rds restore-db-cluster-to-point-in-time ^ - --source-db-cluster-identifier my-source-cluster ^ - --db-cluster-identifier my-clone ^ - --engine-mode provisioned ^ - --restore-type copy-on-write ^ - --use-latest-restorable-time - - -These commands return the JSON object containing details of the clone that you need to create the DB instance. You can't do that until the status of the clone (the empty Aurora DB cluster) has the status **Available**. - -###### Note - -The [restore-db-cluster-to-point-in-time](https://docs.aws.amazon.com/cli/latest/reference/rds/restore-db-cluster-to-point-in-time.html) AWS CLI command only restores the DB cluster, not the DB instances for that DB cluster. You run the [create-db-instance](https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-instance.html) command to create DB instances for the restored DB cluster. With that command, you specify the identifier of the restored DB cluster as the `--db-cluster-identifier` parameter. You can create DB instances only after the `restore-db-cluster-to-point-in-time` command has completed and the DB cluster is available. - -Suppose that you start with an Aurora Serverless v1 cluster and intend to migrate it to an Aurora Serverless v2 cluster. You create a provisioned clone of the Aurora Serverless v1 cluster as the initial step in the migration. For the full procedure, including any required version upgrades, see [Upgrading from an Aurora Serverless v1 cluster to Aurora Serverless v2](./aurora-serverless-v2.upgrade.html#aurora-serverless-v2.upgrade-from-serverless-v1-procedure). - @@ -382 +313 @@ This query returns output similar to the following. -Use the [create-db-instance](https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-instance.html) CLI command to create the DB instance for your Aurora Serverless v2 or provisioned clone. You don't create a DB instance for an Aurora Serverless v1 clone. +Use the [create-db-instance](https://docs.aws.amazon.com/cli/latest/reference/rds/create-db-instance.html) CLI command to create the DB instance for your Aurora Serverless v2 or provisioned clone. @@ -441,7 +371,0 @@ Parameter | Description -`--engine-mode` | (Older versions that support Aurora Serverless v1 only) Use this parameter to create clones that are of a different type from the source Aurora DB cluster, with one of the following values: - - * Use `provisioned` to create a provisioned clone from an Aurora Serverless v1 DB cluster. - * Use `serverless` to create an Aurora Serverless v1 clone from a provisioned or Aurora Serverless v2 DB cluster. When you specify the `serverless` engine mode, you can also choose the `--scaling-configuration`. - - -`--scaling-configuration` | (Older versions that support Aurora Serverless v1 only) Use this parameter to configure the minimum and maximum capacity for an Aurora Serverless v1 clone. If you don't specify this parameter, Aurora creates the clone using the default capacity values for the DB engine.