AWS drs documentation change
Summary
Minor grammatical and clarity improvements in the cross-account failover/failback documentation. Changes include preposition correction ('on your EC2-based applications'), clarification of instruction ('by using information'), and verb agreement fix ('remains' to 'remain').
Security assessment
The changes are editorial and do not address security vulnerabilities or add security documentation. They improve readability but do not alter the security implications of the cross-account disaster recovery process described. No evidence of a security incident or vulnerability remediation is present.
Diff
diff --git a/drs/latest/userguide/failback-failover-cross-account.md b/drs/latest/userguide/failback-failover-cross-account.md index ac4eeac48..5f5baec00 100644 --- a//drs/latest/userguide/failback-failover-cross-account.md +++ b//drs/latest/userguide/failback-failover-cross-account.md @@ -11 +11 @@ Overview and prerequisitesPerforming cross-account failback -AWS Elastic Disaster Recovery (AWS DRS) allows you to perform failover and failback your EC2-based applications from one AWS account to another AWS account. The failover process is the same as failing over into an AWS account from a source outside of AWS, but the failback process is different. The instructions below describe the complete cross-account failover and failback process. +AWS Elastic Disaster Recovery (AWS DRS) allows you to perform failover and failback on your EC2-based applications from one AWS account to another AWS account. The failover process is the same as failing over into an AWS account from a source outside of AWS, but the failback process is different. The instructions below describe the complete cross-account failover and failback process. @@ -68 +68 @@ After the **Reversed direction launch state** is marked as **Ready** , take thes - 1. Find the relevant source servers (A2) in the source account and region by information in the **Replicating to source server** and **Replicating to account** columns of the recovery instance (B2) + 1. Find the relevant source servers (A2) in the source account and region by using information in the **Replicating to source server** and **Replicating to account** columns of the recovery instance (B2) @@ -126 +126 @@ Navigate to the **Recovery instances** in the AWS DRS console. Select the releva -If you have started reversed replication for the recovery instance (A3), you will not be able to disconnect it. To remove the recovery instances (A3) in the source account and region, simply delete the server. This will ensure that the newly launched failed-back instances (A4) remains protected. +If you have started reversed replication for the recovery instance (A3), you will not be able to disconnect it. To remove the recovery instances (A3) in the source account and region, simply delete the server. This will ensure that the newly launched failed-back instances (A4) remain protected.