AWS drs documentation change
Summary
Updated documentation for recovery instance details view with revised text flow, removed images, clarified navigation steps, and added details about private IP security benefits in failback settings
Security assessment
The change adds explicit documentation about security benefits of using private IP for data replication ('Add another layer of security'), but does not address a specific security vulnerability. The encryption-in-transit mention is retained from previous documentation.
Diff
diff --git a/drs/latest/userguide/recovery-instances-details.md b/drs/latest/userguide/recovery-instances-details.md index 4746c971b..7eeb6e008 100644 --- a//drs/latest/userguide/recovery-instances-details.md +++ b//drs/latest/userguide/recovery-instances-details.md @@ -9 +9 @@ Launch dashboardInstance informationTagsFailback replication settings Post-launc -The recovery instance details view provides an in-depth overview of the recovery instance, including the instance's reversed direction launch process, post-launch action runs and data replication status while allowing you to control instance tags and the instance's failback settings. +The recovery instance details view provides an overview of the recovery instance, including the instance's reversed direction launch process, post-launch action runs and data replication status. It allows you to control instance tags and the instance's failback settings. @@ -11 +11 @@ The recovery instance details view provides an in-depth overview of the recovery - +You can access the recovery instance details view by choosing the instance ID of a recovery instance under the **Instance ID** column. @@ -13 +13 @@ The recovery instance details view provides an in-depth overview of the recovery -You can access the recovery instance details view by choosing the instance ID of the recovery instance you wish to access under the **Instance ID** column. +You can also access the recovery instance details view by selecting a recovery instance and choosing the **View instance details** option under the **Actions** menu. @@ -15,9 +15 @@ You can access the recovery instance details view by choosing the instance ID of - - -You can also access the recovery instance details view by selecting the checkbox to the left of the recovery instance and choosing the **View instance details** option under the **Actions** menu. - - - -The recovery instance information page shows the **Instance ID** at the top. - - +The recovery instance information page displays the **Instance ID** at the top. @@ -27,3 +19 @@ The **Overview** panel provides an overview of the failback process, including: - - - * **EC2 instance** – the ID of the recovery instance in EC2. Choose the **View in EC2** option to open the AWS EC2 Console. + * **EC2 instance** – the ID of the recovery instance in EC2. Choose **View in EC2** to open the AWS EC2 Console. @@ -35,3 +25 @@ The **Overview** panel provides an overview of the failback process, including: - * **Launched from source server** – the source server source server from which the recovery instance was launched. Choose the source server ID to open the **Source server details view** page for the specific source server. - - * **Post-launch actions status** – shows the status of the last post-launch actions run on this instance. + * **Launched from source server** – the source server from which the recovery instance was launched. Choose the source server ID to open the **Source server details view** page for the specific source server. @@ -38,0 +27 @@ The **Overview** panel provides an overview of the failback process, including: + * **Post-launch actions status** – displays the status of the last post-launch actions run on this instance. @@ -42 +30,0 @@ The **Overview** panel provides an overview of the failback process, including: -The recovery instance details page is divided into the following sections: @@ -44 +32 @@ The recovery instance details page is divided into the following sections: - +The recovery instance details page is divided into these sections: @@ -67,2 +54,0 @@ The **Reversed direction launch state** panel provides an overview of the revers - - @@ -71 +57 @@ The **Reversed direction launch state** panel provides an overview of the revers - * **Launch target** – the server onto which the recovery instance is launching into. This will indicate whether the recovery instance is launching into the original server or to a new server. Note that for in-AWS flows, this value is always a new server. + * **Launch target** – the server into which the recovery instance is launching. This indicates whether the recovery instance is launching into the original server or to a new server. Note that for in-AWS flows this value is always a new server, unless your are using the **Launch into existing instance** capability. @@ -73 +59 @@ The **Reversed direction launch state** panel provides an overview of the revers - * **Last job ID** – the date and time of the last failback Job was started for the recovery instance. + * **Last job ID** – the ID of the last failback job started for the recovery instance. @@ -86,3 +72 @@ The **Reversed direction launch state** panel provides an overview of the revers -The Data replication status panel shows the current data replication status state for the recovery instance, including: - - +The Data replication status panel displays the current data replication status state for the recovery instance, including: @@ -111,3 +95 @@ The Data replication status panel shows the current data replication status stat -The Events and metrics section contains external links to monitor your recovery instance in AWS CloudTrail. Learn more about monitoring DRS with CloudTrail. - - +The Events and metrics section contains external links to monitor your recovery instance in AWS CloudTrail. [Learn more about monitoring DRS with CloudTrail](https://docs.aws.amazon.com/drs/latest/userguide/logging-using-cloudtrail.html#logging-using-cloudtrail-). @@ -117,5 +99 @@ The Events and metrics section contains external links to monitor your recovery -The **Instance information** tab shows a variety of general server information, hardware, and network information. - - - -Information shown includes: +The **Instance information** tab displays general server information, hardware, and network information: @@ -146,5 +124 @@ Information shown includes: -The Tags section shows any tags that have been assigned to the server. A tag is a label that you assign to an AWS resource. Each tag consists of a key and an optional value. You can use tags to search and filter your resources or track your AWS costs. Learn more about AWS tags in [this Amazon EC2 article](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html). - - - -Choose **Manage tags** to add or remove tags. +The Tags section displays tags that have been assigned to the server. A tag is a label that you assign to an AWS resource. Each tag consists of a key and an optional value. You can use tags to search and filter your resources or track your AWS costs. Learn more about AWS tags in [Tag your Amazon EC2 resources](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html). @@ -152,9 +126 @@ Choose **Manage tags** to add or remove tags. - - -The **Manage tags** page will open. Choose **Add new tag** to add a new tag. - - - -Add a tag **Key** and an optional tag **Value**. Choose **Save** to save your added tags. - - +Choose **Manage tags** to add or remove tags. On the **Manage tags** page choose **Add new tag** to add a new tag. Add a tag **Key** and an optional tag **Value**. **Save** your added tags. @@ -164,2 +129,0 @@ To remove a tag, choose **Remove** to the right of the tag you want to remove, a - - @@ -172,5 +136 @@ Choose **Edit** to edit the settings. - - -You can configure the failback replication settings for multiple recovery instances at once. The **Selected recovery instances** box shows for which recovery instances you are updating the settings. - - +You can configure the failback replication settings for multiple recovery instances at once. The **Selected recovery instances** box displays the recovery instances for which you are updating the settings. @@ -180 +140 @@ You can configure the failback replication settings for multiple recovery instan -You can control the amount of network bandwidth used for data replication per server. By default, Elastic Disaster Recovery will use all available network bandwidth utilizing five concurrent connections. +You can control the amount of network bandwidth used for data replication per server. By default, Elastic Disaster Recovery uses all available network bandwidth on five concurrent connections. Choose **Throttle bandwidth** if you want to control the transfer rate over TCP Port 1500 of data sent from your recovery instances to your source servers during failback. On the the **Throttle network bandwidth (per instance, in Mbps)** enter the bandwidth in Mbps. @@ -182,7 +142 @@ You can control the amount of network bandwidth used for data replication per se - - -Choose **Throttle bandwidth** if you want to control the transfer rate of data sent from your recovery instances to your source servers during failback over TCP Port 1500. Otherwise, choose **Do not throttle bandwidth**. - -If you chose to throttle bandwidth, then the **Throttle network bandwidth (per instance, in Mbps) box will appear**. Enter your desired bandwidth in Mbps. - - +Otherwise, choose **Do not throttle bandwidth**. @@ -192 +146 @@ If you chose to throttle bandwidth, then the **Throttle network bandwidth (per i -By default, data is sent from the recovery instance to the source servers over the public internet, using the public IP that was automatically assigned to the Replication Servers. Transferred data is always encrypted in transit. +By default, data is sent from the recovery instance to the source servers over the public internet, using the public IP that was automatically assigned to the replication servers. Transferred data is always encrypted in transit. @@ -194 +148 @@ By default, data is sent from the recovery instance to the source servers over t - +Choose the **Use private IP** option if you want to route the replicated data from your recovery instance to your source servers through a private network with a VPN, AWS Direct Connect, VPC peering, or another type of existing private connection. Use this option if you want to: @@ -196 +150 @@ By default, data is sent from the recovery instance to the source servers over t -Choose the **Use private IP** option if you want to route the replicated data from your recovery instance to your source servers through a private network with a VPN, AWS Direct Connect, VPC peering, or another type of existing private connection. You should use this option if you want to: + * Allocate a dedicated bandwidth for replication @@ -198 +152 @@ Choose the **Use private IP** option if you want to route the replicated data fr - * Allocate a dedicated bandwidth for replication; + * Use another level of encryption @@ -200,3 +154 @@ Choose the **Use private IP** option if you want to route the replicated data fr - * Use another level of encryption; - - * Add another layer of security by transferring the replicated data from one private IP address (source) to another private IP address (on AWS). + * Add another layer of security by transferring the replicated data from one private IP address (source) to another private IP address (on AWS) @@ -209 +161 @@ Choose the **Use private IP** option if you want to route the replicated data fr -Data replication will not work unless you have already set up the VPN, AWS Direct Connect, or VPC peering in the AWS Console. +Data replication does not work unless you have already set up the VPN, AWS Direct Connect, or VPC peering in the AWS Console. @@ -213 +165 @@ Data replication will not work unless you have already set up the VPN, AWS Direc - * If you selected the default subnet, it is highly unlikely that the private IP is activated for that subnet. Ensure that Private IP (VPN, AWS Direct Connect, or VPC peering) is activated for your chosen subnet if you wish to use this option. + * If you selected the default subnet, it is highly unlikely that the private IP is activated for that subnet. Ensure that Private IP (VPN, AWS Direct Connect, or VPC peering) is activated for your chosen subnet to use this option. @@ -215 +167 @@ Data replication will not work unless you have already set up the VPN, AWS Direc - * Choosing the **Use Private IP** option will not create a new private connection. + * Choosing the **Use Private IP** option does not create a new private connection. @@ -224,2 +175,0 @@ Once you have configured your failback replication settings, choose **Save failb - - @@ -228,3 +178 @@ Once you have configured your failback replication settings, choose **Save failb -The **Post-launch actions** view shows the current run status of post-launch actions. - - +The **Post-launch actions** view displays the current run status of post-launch actions. @@ -240 +188 @@ The status includes: - * **Start time** – the time when the action script started to run. This column will be empty for actions that have not yet started running. + * **Start time** – the time when the action script started to run. This column is empty for actions that have not yet started running. @@ -242 +190 @@ The status includes: - * **End time** – the time when the action script run ended. This column will be empty for actions that have not yet completed running. + * **End time** – the time when the action script run ended. This column is empty for actions that have not yet completed running. @@ -244 +192 @@ The status includes: - * **Details** – error messages will be shown in this column. + * **Details** – error messages are displayed in this column.