AWS drs documentation change
Summary
Editorial improvements including grammatical corrections, tense consistency fixes, image removals, and UI text simplifications in recovery dashboard documentation
Security assessment
Changes focus on grammatical improvements (e.g., changing 'will be blank' to 'is blank'), tense consistency, and image removals. No security vulnerabilities, mitigations, or security feature enhancements are mentioned. The modifications to stalled state descriptions and replication status explanations improve clarity but don't address security aspects. CloudTrail reference remains unchanged in security context.
Diff
diff --git a/drs/latest/userguide/recovery-dashboard.md b/drs/latest/userguide/recovery-dashboard.md index 561102c02..ea66815d1 100644 --- a//drs/latest/userguide/recovery-dashboard.md +++ b//drs/latest/userguide/recovery-dashboard.md @@ -40 +40 @@ Here, you can see the following: - * **Job finished** – The date and time the last recovery job was finished. This field will be blank if the job is still ongoing. + * **Job finished** – The date and time the last recovery job was finished. This field is blank if the job is still ongoing. @@ -53,2 +52,0 @@ The **Data replication status** section provides an overview of the overall sour - - @@ -57 +55 @@ The **Data replication status** section provides an overview of the overall sour - * **Rescan progress** – The percentage of the server's storage that was rescanned (in the event of a rescan) + * **Rescan progress** – In the event of of a rescan, the percentage of the server's storage that was rescanned. @@ -76 +74 @@ Data replication can be in one of several states, as indicated in the panel titl - * **Initial sync** : initial copying of data from external servers is not done. Progress bar and **Total replicated storage** fields will indicate how far along the process is. + * **Initial sync** : initial copying of data from external servers is not done. Progress bar and **Total replicated storage** fields indicate how far along the process is. @@ -80 +78 @@ Data replication can be in one of several states, as indicated in the panel titl - * **Rescan** : an event happened that forced the agent on the external server to rescan all blocks on all replicated disks (same as initial sync but faster because only changed blocks need to be copied; a rescan progress bar will also appear). + * **Rescan** : an event happened that forced the agent on the external server to rescan all blocks on all replicated disks. This is the same as an initial sync but is faster because only changed blocks need to be copied; a rescan progress bar appears. @@ -82 +80 @@ Data replication can be in one of several states, as indicated in the panel titl - * **Stalled** : data is not flowing and user intervention is required (either initial sync will never complete, or state at source will become further and further the state at AWS). When the state is stalled, then the replication initiation checklist is also shown, indicating where the error occurred that caused the stalled state. + * **Stalled** : data is not flowing and user intervention is required (either initial sync never completes, or the state at the source becomes increasingly different from the state at AWS). When the state is stalled, then the replication initiation checklist is also shown, indicating where the error occurred that caused the stalled state. @@ -91 +89 @@ This panel also shows: -**Lag** : if you launch a recovery instance now, how far behind will it be from state at source. Normally this should be none. +**Lag** : if you launch a recovery instance now, how far behind it is from the state at the source. Normally this should be none. @@ -100,3 +98 @@ This panel also shows: -If everything is working as it should and replication has finished initializing, the Data replication progress section will show a **Healthy** status. - - +If everything is working as it should and replication has finished initializing, the Data replication progress section displays a **Healthy** status. @@ -104,3 +100 @@ If everything is working as it should and replication has finished initializing, -If there are initialization, replication, or connectivity errors, the **Data replication status** section will show the cause of the issue (for example, a stall). If the error occurred during the initialization process, then the exact step during which the error occurred will be marked with a red "x" under **Replication initiation steps.** - - +If there are initialization, replication, or connectivity errors, the **Data replication status** section displays the cause of the issue, for example, a stall. If the error occurred during the initialization process, then the exact step during which the error occurred is marked with a red "x" under **Replication initiation steps**. @@ -110,5 +104 @@ If there are initialization, replication, or connectivity errors, the **Data rep -You can review AWS Elastic Disaster Recovery events and metrics in AWS CloudTrail. Click on **View CloudTrail event history** to open AWS CloudTrail in a new tab. - - - -Learn more about AWS CloudTrail events in the [AWS CloudTrail user guide](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-concepts.html). +You can review AWS Elastic Disaster Recovery events and metrics in AWS CloudTrail. Choose **View CloudTrail event history** to open AWS CloudTrail in a new tab. Learn more about AWS CloudTrail events in the [AWS CloudTrail user guide](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-concepts.html). @@ -135,3 +125 @@ The **Actions** menu allows you to perform the following actions: - - - * **Add servers** – Choosing this option will redirect you to the AWS Replication Agent installation instructions. + * **Add servers** – Choosing this option redirects you to the AWS Replication Agent installation instructions. @@ -151 +139 @@ On the **Disconnect X server/s from service** dialog, choose **Disconnect**. -This will uninstall the AWS Replication Agent from the source server, and data replication will stop for the source server. This action will not affect any drill or recovery instances that have been launched for this source server, but you will no longer be able to identify which source servers your Amazon EC2 instances correspond to. +This uninstalls the AWS Replication Agent from the source server, and data replication stops for the source server. This action does not affect any drill or recovery instances that have been launched for this source server, but you are no longer able to identify which source servers your Amazon EC2 instances correspond to. @@ -153 +141 @@ This will uninstall the AWS Replication Agent from the source server, and data r - * **Delete server** – Choose this option to permanently delete a source server from AWS Elastic Disaster Recovery. This will remove all information related to the server from the AWS Elastic Disaster Recovery service. You can only delete servers that have been disconnected from AWS. You will need to reinstall the AWS Replication Agent on a deleted source server to add it back to AWS Elastic Disaster Recovery. + * **Delete server** – Choose this option to permanently delete a source server from AWS Elastic Disaster Recovery. This removes all information related to the server from the AWS Elastic Disaster Recovery service. You can only delete servers that have been disconnected from AWS. You need to reinstall the AWS Replication Agent on a deleted source server to add it back to AWS Elastic Disaster Recovery. @@ -164,2 +151,0 @@ The Initiate recovery job menu allows you to start drills and recoveries by laun - - @@ -175,15 +161 @@ The Initiate recovery job menu allows you to start drills and recoveries by laun -You can easily distinguish between healthy servers and servers that are experiencing issues on the **Recovery dashboard** in several ways. - -The entire AWS Elastic Disaster Recovery Console is color-coded for ease of use. - -Healthy servers with no errors are characterized by the color blue. The **Data replication status** boxes will display all steps and information in blue if the server is healthy. - -The following are examples of healthy servers: - - - -Servers that are experiencing temporary issues will be characterized by the color yellow. This can include issues such as lag or a rescan. These issues will not break replication, but may delay replication or indicate a bigger problem. - -The following are examples of servers experiencing temporary issues: - -Lagging server: +You can distinguish between healthy servers and servers that are experiencing issues on the **Recovery dashboard** in several ways. The AWS Elastic Disaster Recovery console is color-coded for ease of use. @@ -191 +163 @@ Lagging server: - + * Healthy servers with no errors are characterized by the color blue. The **Data replication status** boxes displays steps and information in blue if the server is healthy. @@ -193 +165 @@ Lagging server: -Rescanning server: + * Servers that are experiencing temporary issues are characterized by the color yellow. This can include issues such as lag or a rescan. These issues do not break replication, but may delay replication or indicate a bigger problem. @@ -195 +167 @@ Rescanning server: - + * Servers that are experiencing serious issues are characterized by the color red. These issues can include a loss of connection, a stall, or other issues. You have to fix these issues in order for data replication to resume. @@ -197 +169 @@ Rescanning server: -Servers that are experiencing serious issues will be characterized by the color red. These issues can include a loss of connection, a stall, or other issues. You will have to fix these issues in order for data replication to resume. +The **Data replication status** box includes details of the issue. @@ -199 +171 @@ Servers that are experiencing serious issues will be characterized by the color -The **Data replication status** box will include details of the issue. +If the stall occurred during initiation, scroll down to **Replication initiation steps**. The step where the issue arose is marked with a red "x". @@ -201 +172,0 @@ The **Data replication status** box will include details of the issue. - @@ -203 +173,0 @@ The **Data replication status** box will include details of the issue. -If the stall occurred during initiation, scroll down to **Replication initiation steps**. The exact step where the issue arose will be marked with a red "x". @@ -205 +174,0 @@ If the stall occurred during initiation, scroll down to **Replication initiation -