AWS drs documentation change
Summary
Minor grammatical corrections and wording improvements in DRS launch settings documentation
Security assessment
Changes are purely editorial (grammar, spelling, clarity) with no indication of addressing security vulnerabilities or adding security features. The content about VPN subnet conflicts and instance tagging remains unchanged in substance.
Diff
diff --git a/drs/latest/userguide/launch-general-settings.md b/drs/latest/userguide/launch-general-settings.md index 814e7be92..f9ae507f4 100644 --- a//drs/latest/userguide/launch-general-settings.md +++ b//drs/latest/userguide/launch-general-settings.md @@ -73 +73 @@ Choose **Yes** if you want to use a private IP. The IP will be shown in brackets - * If the both the source server and the drill or recovery instance share the same subnet though a VPN, then the source private IP is already in use, and the **Copy private IP** option should not be used. + * If both the source server and the drill or recovery instance share the same subnet through a VPN, then the source private IP is already in use, and the **Copy private IP** option should not be used. @@ -103 +103 @@ You can always add tags from the Amazon EC2 console as described in [this Amazon - * **Launch into instance ID** \- Configure an existing instance ID to launch into, instead of creating a new instance. This field allows to select an EC2 instance from the list of EC2 instances available in this region. The EC2 instance to launch into must have a tag with key _AWSDRS_ and value _AllowLaunchingIntoThisInstance_ to appear in the list, and it must be stopped prior to launching into it. When this value is set, the **Transfer server tags** and **Copy private IP** settings will be deactivated, as they cannot apply to an already launched instance. + * **Launch into instance ID** \- Configure an existing instance ID to launch into, instead of creating a new instance. This field allows you to select an EC2 instance from the list of EC2 instances available in this region. The EC2 instance to launch into must have a tag with key _AWSDRS_ and value _AllowLaunchingIntoThisInstance_ to appear in the list, and it must be stopped prior to launching into it. When this value is set, the **Transfer server tags** and **Copy private IP** settings will be deactivated, as they cannot apply to an already launched instance. @@ -107 +107 @@ You can always add tags from the Amazon EC2 console as described in [this Amazon -For the instance to appear and perform as a recovery instance in DRS and allow to run post-launch actions on it, it needs to have an instance profile that includes the policies **AWSElasticDisasterRecoveryRecoveryInstancePolicy** and **AmazonSSMManagedInstanceCore**. The role **AWSElasticDisasterRecoveryRecoveryInstanceWithLaunchActionsRole** , installed from the Default post-launch actions settings page if not already present, contains these policies and can be used as an instance profile. +For the instance to appear and perform as a recovery instance in DRS and allow you to run post-launch actions on it, it needs to have an instance profile that includes the policies **AWSElasticDisasterRecoveryRecoveryInstancePolicy** and **AmazonSSMManagedInstanceCore**. The role **AWSElasticDisasterRecoveryRecoveryInstanceWithLaunchActionsRole** , installed from the Default post-launch actions settings page if not already present, contains these policies and can be used as an instance profile. @@ -115 +115 @@ The launch into an instance will fail if the following pre-requisites are not me - 3. The instance to launch into must have the same operating systems platform (Linux or Windows) as that of the server it is protecting. + 3. The instance to launch into must have the same operating system platform (Linux or Windows) as that of the server it is protecting.