AWS documentdb documentation change
Summary
Updated image references, reordered steps, clarified security group configuration instructions, and added details about instance configuration and authentication options.
Security assessment
Changes primarily involve documentation clarity improvements and image path updates. The correction from 'Destination' to 'Source' in security group configuration fixes a potential misconfiguration but doesn't address a specific disclosed vulnerability. Security-related content (e.g., security groups, authentication) was already present and only receives formatting/emphasis changes.
Diff
diff --git a/documentdb/latest/developerguide/connect-ec2-manual.md b/documentdb/latest/developerguide/connect-ec2-manual.md index 2fb2efd81..98dde8638 100644 --- a//documentdb/latest/developerguide/connect-ec2-manual.md +++ b//documentdb/latest/developerguide/connect-ec2-manual.md @@ -46 +46 @@ In this step, you will create an Amazon EC2 instance in the same Region and Amaz - + @@ -50,2 +49,0 @@ In this step, you will create an Amazon EC2 instance in the same Region and Amaz - - @@ -82 +80 @@ For security purposes, we highly recommend using a key-pair for both SSH and int - + @@ -96,2 +93,0 @@ If you chose to create a new security group, perform the following: - - @@ -111 +107 @@ You will now create a new security group in your default Amazon VPC. The securit - + @@ -113 +109 @@ You will now create a new security group in your default Amazon VPC. The securit - 3. In the Basic details section: + 3. In the **Basic details** section: @@ -121,2 +116,0 @@ You will now create a new security group in your default Amazon VPC. The securit - - @@ -125 +119 @@ You will now create a new security group in your default Amazon VPC. The securit - 1. For **Type** , choose **Custom TCP Rule**. + 1. For **Type** , choose **Custom TCP Rule** (default). @@ -129 +123 @@ You will now create a new security group in your default Amazon VPC. The securit - 3. For Destination, choose **Custom**. In the field next to it, search for the security group you just created in step 1. You may need to refresh your browser for the Amazon EC2 console to auto-populate the source name. + 3. For **Source** , choose **Custom**. In the field next to it, search for the security group you just created in step 1. You may need to refresh your browser for the Amazon EC2 console to auto-populate the source name. @@ -131 +125 @@ You will now create a new security group in your default Amazon VPC. The securit - + @@ -146,2 +139,0 @@ While the Amazon EC2 instance is being provisioned, you will create your Amazon - - @@ -150 +142 @@ While the Amazon EC2 instance is being provisioned, you will create your Amazon - + 3. Leave the **Cluster type** setting at it's default of **Instance Based Cluster**. @@ -152 +144 @@ While the Amazon EC2 instance is being provisioned, you will create your Amazon - 3. Leave the **Cluster type** setting at its default of **Instance Based Cluster**. + 4. In **Cluster configuration** , for **Cluster identifier** , enter a unique name. Note that the console will change all cluster names into lower-case regardless of how they are entered. @@ -154 +146 @@ While the Amazon EC2 instance is being provisioned, you will create your Amazon - +Leave the **Engine version** at it's default value of **5.0.0**. @@ -156 +148 @@ While the Amazon EC2 instance is being provisioned, you will create your Amazon - 4. For **Number of instances** , choose **1**. This will minimize cost. Leave the other settings at their default. + 5. For **Cluster storage configuration** , leave the default setting of **Amazon DocumentDB Standard**. @@ -158 +150 @@ While the Amazon EC2 instance is being provisioned, you will create your Amazon - + 6. In **Instance configuration** : @@ -160 +152 @@ While the Amazon EC2 instance is being provisioned, you will create your Amazon - 5. For **Connectivity** , leave the default setting of **Don't connect to an EC2 compute resource**. + * For **DB instance class** , choose **Memory optimized classes (include r classes)** (this is default). @@ -162 +154 @@ While the Amazon EC2 instance is being provisioned, you will create your Amazon - +The other instance option is **NVMe-backed classes**. To learn more, see [NVMe-backed instances](./db-instance-nvme.html). @@ -164 +156 @@ While the Amazon EC2 instance is being provisioned, you will create your Amazon -###### Note + * For **Instance class** , choose the instance type that suits your needs. For a more detailed explanation of instance classes, see [Instance class specifications](./db-instance-classes.html#db-instance-class-specs). @@ -166 +158 @@ While the Amazon EC2 instance is being provisioned, you will create your Amazon -Connecting to an EC2 compute resource automatically creates security groups for your EC2 compute resource connection to your cluster. Since you manually created these security groups in the previous step, you should select **Don't connect to an EC2 compute resource** so as not to create a second set of security groups. + * For **number of instances** , choose a number that best reflects your needs. Remember, the lower the number, the lower the cost, and the lower the read/write volume that can be managed by the cluster. @@ -168 +160 @@ Connecting to an EC2 compute resource automatically creates security groups for - 6. In the **Authentication** section, enter a username for the primary user, and then choose **Self managed**. Enter a password, then confirm it. + @@ -170 +162,3 @@ Connecting to an EC2 compute resource automatically creates security groups for -If you instead chose **Managed in AWS Secrets Manager** , see [Password management with Amazon DocumentDB and AWS Secrets Manager](./docdb-secrets-manager.html) for more information. + 7. For **Connectivity** , leave the default setting of **Don't connect to an EC2 compute resource**. + +###### Note @@ -172 +166 @@ If you instead chose **Managed in AWS Secrets Manager** , see [Password manageme - +Connecting to an EC2 compute resource automatically creates security groups for your connection to your cluster. Since you manually created these security groups in the previous step, you should select **Don't connect to an EC2 compute resource** so as not to create a second set of security groups. @@ -174 +168,3 @@ If you instead chose **Managed in AWS Secrets Manager** , see [Password manageme - 7. Choose **Create cluster**. + 8. In the **Authentication** section, enter a username for the primary user, and then choose **Self managed**. Enter a password, then confirm it. + +If you instead chose **Managed in AWS Secrets Manager** , see [Password management with Amazon DocumentDB and AWS Secrets Manager](./docdb-secrets-manager.html) for more information. @@ -176 +172 @@ If you instead chose **Managed in AWS Secrets Manager** , see [Password manageme - + 9. Choose **Create cluster**.