AWS drs documentation change
Summary
Clarified failover guidance, improved wording for recovery instance instructions, and fixed typos in operational procedures
Security assessment
Changes involve grammatical improvements, clarification of existing procedures, and typo fixes. No specific security vulnerabilities or security feature additions are mentioned.
Diff
diff --git a/drs/latest/userguide/best_practices_drs.md b/drs/latest/userguide/best_practices_drs.md index 950009090..28d981c62 100644 --- a//drs/latest/userguide/best_practices_drs.md +++ b//drs/latest/userguide/best_practices_drs.md @@ -61 +61 @@ You should control who can install the AWS Replication Agent in your account. On - 4. **Failover dos and don’ts:** Do not use the **Disconnect from AWS** action in the DRS console for servers for which you launched Recovery instances, even in the case of a real recovery event. Performing a disconnect will terminate all replication resources related to these source servers, including your Point-In-Time (PIT) recovery points. You may need these PITs while you are in failover state, for regulatory reasons, or to re-launch a Recovery instances for any reason (for instance if you discover that the PIT from which you launched includes corrupt or malicious data, and you want to relaunch from an earlier PIT). You should realize that while you you use your Recovery instances as your primary, and new data is presumably written to them, these recovery instances are not themselves being replicated, and you are not creating any new PITs for these changes. It is possible to configure the Recovery instances as new source servers and [replicate them cross-Region](https://docs.aws.amazon.com/drs/latest/userguide/failback-failover-region-region.html), so as to have DR for your recovery site (this carries with it additional costs, as is detailed in the linked page). + 4. **Failover dos and don’ts:** Do not use the **Disconnect from AWS** action in the DRS console for servers for which you launched Recovery instances, even in the case of a real recovery event. Performing a disconnect will terminate all replication resources related to these source servers, including your Point-In-Time (PIT) recovery points. You may need these PITs while you are in failover state, for regulatory reasons, or to re-launch a Recovery instances for any reason (for instance if you discover that the PIT from which you launched includes corrupt or malicious data, and you want to relaunch from an earlier PIT). While you use your Recovery instances as your primary, and new data is presumably written to them, these recovery instances are not themselves being replicated, and you are not creating any new PITs for these changes. It is possible to configure the recovery instances as new source servers and [replicate them cross-Region](https://docs.aws.amazon.com/drs/latest/userguide/failback-failover-region-region.html), to have disaster recovery for your recovery site. This carries with it additional costs, as noted in [Performing a cross-Region failback](https://docs.aws.amazon.com/drs/latest/userguide/failback-failover-region-region.html) @@ -71 +71 @@ You should control who can install the AWS Replication Agent in your account. On - 6. **Recover into existing instance:** In case you would like to recover into an instance that already exists, instead of launching a new one for recovery, drill or failback. Instance to recover into must be of the same operating system platform (Linux or Windows) as the source instance, it must be stopped and it must have the tag key _AWSDRS_ and tag value _AllowLaunchingIntoThisInstance_. [Learn more about recover into existing instance](./launch-general-settings.html#server-launch-settings-parameters). + 6. **Recover into existing instance:** Use if you want to recover into an instance that already exists instead of launching a new one for recovery, drill or failback. The instance to recover into must be of the same operating system platform (Linux or Windows) as the source instance, it must be stopped and it must have the tag key _AWSDRS_ and tag value _AllowLaunchingIntoThisInstance_. [Learn more about recover into existing instance](./launch-general-settings.html#server-launch-settings-parameters). @@ -80 +80 @@ You should control who can install the AWS Replication Agent in your account. On - 2. **Return to normal operation:** make sure that the failed-back servers at the source are replicating back to AWS, and appear as source servers in the DRS console. If they do appear in the DRS console and are not replicating, explore the reason (such as firewall settings, etc.) If they do not appear in the DRS console you may need to install / re-install the AWS Replication Agent on them. Make that you do not end up with two source server entities in the DRS console, one representing the original server, and one the failed-back server. + 2. **Return to normal operation:** make sure that the failed-back servers at the source are replicating back to AWS, and appear as source servers in the DRS console. If they do appear in the DRS console and are not replicating, explore the reason (such as firewall settings, etc.) If they do not appear in the DRS console you may need to install / re-install the AWS Replication Agent on them. Make sure that you do not end up with two source server entities in the DRS console, one representing the original server, and one the failed-back server.