AWS aurora-dsql: Restructure Aurora DSQL console cluster creation steps (single/multi-Region)
Summary
Rewrites the getting-started console walkthrough for creating Aurora DSQL clusters. Single-Region creation is reorganized into Cluster topology, Cluster configuration (Quick create vs. Advanced configuration), and optional settings. The multi-Region procedure is simplified to a single console flow (2 active Regions + Witness) that creates and peers both clusters. Existing security-related options (KMS encryption settings, deletion protection, resource-based policy) are retained but reworded and relocated under the Advanced configuration path.
Security assessment
The diff is primarily a UI/UX restructure of the cluster-creation walkthrough. It carries forward existing hardening guidance (customer managed KMS key policy requirements, default-on deletion protection, and resource-based access control policies) without adding new security controls or referencing any vulnerability. No evidence of a specific flaw or incident being fixed, so security_issue_related is false; it merely restates security-relevant configuration options, hence adds_security_documentation is true and severity is low.
Evidence
+ * In **Cluster settings** , keep **Enable deletion protection** selected to prevent a delete operation from removing your cluster. The console selects it by default.
Diff
diff --git a/aurora-dsql/latest/userguide/getting-started.md b/aurora-dsql/latest/userguide/getting-started.md index ee031fb..d4f94a0 100644 --- a//aurora-dsql/latest/userguide/getting-started.md +++ b//aurora-dsql/latest/userguide/getting-started.md @@ -53 +53 @@ The basic unit of Aurora DSQL is the cluster, which is where you store your data - 2. Choose **Create cluster** and then **Single-Region**. + 2. Choose **Create cluster**. @@ -55 +55 @@ The basic unit of Aurora DSQL is the cluster, which is where you store your data - 3. (Optional) change the value of the default **Name** tag. + 3. In **Cluster topology** , choose **Single Region**. @@ -57 +57 @@ The basic unit of Aurora DSQL is the cluster, which is where you store your data - 4. (Optional) Add additional **Tags** for this cluster. + 4. In **Cluster configuration** , choose one of the following: @@ -59 +59 @@ The basic unit of Aurora DSQL is the cluster, which is where you store your data - 5. (Optional) In **Cluster settings** , select any of the following options: + * **Quick create** to create the cluster with recommended settings. You can change some settings, such as **Tag: Name** and deletion protection, before you create the cluster. @@ -61 +61 @@ The basic unit of Aurora DSQL is the cluster, which is where you store your data - * Select **Customize encryption settings (advanced)** to choose or create an AWS KMS key. If you use a customer managed key, ensure that the key policy grants Aurora DSQL the required permissions. For more information, see [Key policy for a customer managed key](./data-encryption.html#key-policy-customer-managed-key). + * **Advanced configuration** to control all settings, including encryption and resource-based policies. @@ -63 +63 @@ The basic unit of Aurora DSQL is the cluster, which is where you store your data - * Select **Enable deletion protection** to prevent a delete operation from removing your cluster. By default, deletion protection is selected. + 5. (Optional) If you chose **Advanced configuration** , do any of the following: @@ -65 +65 @@ The basic unit of Aurora DSQL is the cluster, which is where you store your data - * Select **Resource-based policy (advanced)** to specify access control policies for this cluster. + * In **Name and tags** , change the value of the default **Name** tag, or choose **Add additional tags**. @@ -67 +67 @@ The basic unit of Aurora DSQL is the cluster, which is where you store your data - 6. Choose **Create cluster**. + * In **Cluster settings** , select **Customize encryption settings (advanced)** to choose or create an AWS KMS key. If you use a customer managed key, make sure that the key policy grants Aurora DSQL the required permissions. For more information, see [Key policy for a customer managed key](./data-encryption.html#key-policy-customer-managed-key). @@ -69 +69,5 @@ The basic unit of Aurora DSQL is the cluster, which is where you store your data - 7. The console returns you to the **Clusters** page. A notification banner appears indicating that the cluster is being created. Select the **Cluster ID** to open the cluster details view. + * In **Cluster settings** , keep **Enable deletion protection** selected to prevent a delete operation from removing your cluster. The console selects it by default. + + * In **Cluster settings** , select **Add resource-based policy** to specify access control policies for this cluster. + + 6. Choose **Create cluster**. The console opens the details page for your new cluster. @@ -142 +146 @@ This Region receives all data that is written to the multi-Region cluster. Howev -Use the following procedure to create an initial cluster, create a second cluster in a different Region, and then peer the two clusters to create a multi-Region cluster. It also demonstrates cross-Region write replication and consistent reads from both Regional endpoints. +Use the following procedure to create a multi-Region cluster. The console creates a cluster in each of the two Regions and peers them for you. The procedures after it show cross-Region write replication and consistent reads from both Regional endpoints. @@ -150,27 +154 @@ Use the following procedure to create an initial cluster, create a second cluste - 3. Choose **Create cluster** and then **Multi-Region**. - - 4. (Optional) change the value of the default **Name** tag. - - 5. (Optional) Add additional **Tags** for this cluster. - - 6. In **Multi-Region settings** , choose the following options for your initial cluster: - - * In **Witness Region** , choose a Region. - - * (Optional) In **Remote Region cluster ARN** , enter an ARN for an existing cluster in another Region. If no cluster exists to serve as the second cluster in your multi-Region cluster, complete setup after you create the initial cluster. - - 7. (Optional) In **Cluster settings** , select any of the following options for your initial cluster: - - * Select **Customize encryption settings (advanced)** to choose or create an AWS KMS key. If you use a customer managed key, ensure that the key policy grants Aurora DSQL the required permissions. For more information, see [Key policy for a customer managed key](./data-encryption.html#key-policy-customer-managed-key). - - * Select **Enable deletion protection** to prevent a delete operation from removing your cluster. By default, deletion protection is selected. - - * Select **Resource-based policy (advanced)** to specify access control policies for this cluster. - - 8. Choose **Create cluster** to create your initial cluster. If you didn't enter an ARN in the previous step, the console shows the **Cluster setup pending** notification. - - 9. In the **Cluster setup pending** notification, choose **Complete multi-Region cluster setup**. This action initiates creation of a second cluster in another Region. - - 10. Choose one of the following options for your second cluster: - - * **Add remote Region cluster ARN** – Choose this option if a cluster exists, and you want it to be the second cluster in your multi-Region cluster. + 3. Choose **Create cluster**. @@ -178 +156 @@ Use the following procedure to create an initial cluster, create a second cluste - * **Create cluster in another Region** – Choose this option to create a second cluster. In **Remote Region** , choose the Region for this second cluster. + 4. In **Cluster topology** , choose **2 active Regions + Witness**. @@ -180 +158 @@ Use the following procedure to create an initial cluster, create a second cluste - 11. Choose **Create cluster in`your-second-region`**, where `your-second-region` is the location of your second cluster. The console opens in your second Region. + 5. In **Cluster configuration** , choose one of the following: @@ -182 +160 @@ Use the following procedure to create an initial cluster, create a second cluste - 12. (Optional) Choose cluster settings for your second cluster. For example, you can choose an AWS KMS key. If you use a customer managed key, ensure that the key policy grants Aurora DSQL the required permissions. For more information, see [Key policy for a customer managed key](./data-encryption.html#key-policy-customer-managed-key). + * **Quick create** to create the clusters with recommended settings. **Peer cluster 1** is in your current Region. To change the Region for **Peer cluster 2** or **Witness peer** , choose a Region in the **Region** row of the table. @@ -184 +162 @@ Use the following procedure to create an initial cluster, create a second cluste - 13. Choose **Create cluster** to create your second cluster. + * **Advanced configuration** to control all settings for each Region. In **Regions** , choose the **Peer cluster 2 Region** and the **Witness Region**. @@ -186 +164 @@ Use the following procedure to create an initial cluster, create a second cluste - 14. Choose **Peer in`initial-cluster-region`**, where `initial-cluster-region` is the Region that hosts the first cluster that you created. + 6. (Optional) If you chose **Advanced configuration** , change the settings for each Region in **Name and tags** , **Encryption key** , **Deletion protection** , and **Resource-based policy - optional**. If you use a customer managed key, make sure that the key policy grants Aurora DSQL the required permissions. For more information, see [Key policy for a customer managed key](./data-encryption.html#key-policy-customer-managed-key). @@ -188 +166 @@ Use the following procedure to create an initial cluster, create a second cluste - 15. When prompted, choose **Confirm**. This step completes the creation of your multi-Region cluster. + 7. Choose **Create cluster**. The console creates the cluster in your current Region and opens its details page. A notification shows the progress while the console creates the second cluster and peers the two clusters.