AWS drs documentation change
Summary
Updated documentation structure and wording for clarity, removed redundant images, condensed instructions, and improved flow of AWS Elastic Disaster Recovery setup steps.
Security assessment
The changes are primarily editorial improvements to enhance clarity and conciseness. While security-related topics like security groups and service-linked roles are mentioned, there is no evidence of addressing a specific vulnerability or adding new security features. The security group section clarifies existing functionality ('attach to and monitor' vs 'attach and monitor') but does not introduce new security controls or address a known issue.
Diff
diff --git a/drs/latest/userguide/quick-start-guide-gs.md b/drs/latest/userguide/quick-start-guide-gs.md index 02505d6c5..9fab7cc44 100644 --- a//drs/latest/userguide/quick-start-guide-gs.md +++ b//drs/latest/userguide/quick-start-guide-gs.md @@ -9 +9 @@ First time setupAdding source serversConfiguring launch settingsLaunching a dril -This section will guide you through first time Elastic Disaster Recovery setup, including: +This section guides you through your initial Elastic Disaster Recovery setup, including: @@ -36,11 +36 @@ You need to be the admin user of the AWS account, or have a role with the AWSEla -The first setup step for AWS DRS is setting the default replication settings. Choose **Set default replication settings** on the AWS Elastic Disaster Recovery landing page. - - - -You will be guided through the steps of setting up your default replication settings, default launch settings, and EC2 template. These default settings will be applied to every source server that is added to AWS Elastic Disaster Recovery. You can change both the default settings and individual source server settings for one or more source servers at any time. Learn more about editing [ your replication settings](./default-replication-settings.html) and [ launch settings](./launch-settings-overview.html). - -###### Note - -You can use the default setting, by simply choosing **Next** on each of the pages in this wizard or modify any of the setting to best fit your needs. To learn more about each setting, click the **Info** links next to each section. - - +The first setup step for AWS DRS is setting the default replication settings. Choose **Set default replication settings** on the AWS Elastic Disaster Recovery landing page. You are guided through the steps of setting up your default replication settings, default launch settings, and EC2 template. These default settings are applied to every source server that is added to AWS Elastic Disaster Recovery. You can change both the default settings and individual source server settings for one or more source servers at any time. Learn more about editing [ your replication settings](./default-replication-settings.html) and [ launch settings](./launch-settings-overview.html). To learn more about each setting, select the **Info** links next to each section. @@ -52,3 +42 @@ Before configuring your default settings, ensure that you meet the [Network requ -On the first page of the wizard, you will be asked to **Set up replication servers**. Replication servers are lightweight Amazon EC2 instances that are used to replicate data between your source servers and AWS. Replication servers are automatically launched and terminated as needed. You can start using AWS Elastic Disaster Recovery with the default replication server settings or you can configure your own settings. [Learn more about replication server settings.](./individual-replication-settings.html#replication-server-settings) - - +On the first page of the wizard, you are asked to **Set up replication servers**. Replication servers are lightweight Amazon EC2 instances that are used to replicate data between your source servers and AWS. Replication servers are automatically launched and terminated as needed. You can start using AWS Elastic Disaster Recovery with the default replication server settings or you can configure your own settings. [Learn more about replication server settings.](./individual-replication-settings.html#replication-server-settings) @@ -65,13 +53 @@ On the first page of the wizard, you will be asked to **Set up replication serve -###### Note - -During this step you will also be able to review the service linked role and additional policies created during Elastic Disaster Recovery initialization. Choose **View details** to learn more. - - - -Click **Next** to proceed to the second page of the wizard. - -On the second page of the wizard you will be asked to **Specify volumes and security groups**. - - - -For each disk on an added source server there is an identically-sized EBS volume attached to a replication server, and each replication server can handle replication of disks from multiple source servers. [Learn more about volumes.](./volumes-drs.html) +During this step you can review the service linked role and additional policies created during Elastic Disaster Recovery initialization. Choose **View details** to learn more. the service linked role and additional policies created during Elastic Disaster Recovery initialization @@ -79 +55 @@ For each disk on an added source server there is an identically-sized EBS volume - +On the second page of the wizard you are asked to **Specify volumes and security groups**. For each disk on an added source server there is an identically-sized EBS volume attached to a replication server, and each replication server can handle replication of disks from multiple source servers. [Learn more about volumes.](./volumes-drs.html) @@ -81,3 +57 @@ For each disk on an added source server there is an identically-sized EBS volume -A security group acts as a virtual firewall, which controls the inbound and outbound traffic of the staging area. The best practice is to have AWS Elastic Disaster Recovery automatically attach and monitor the default AWS Elastic Disaster Recovery security group. This group opens inbound TCP Port 1500 for receiving the transferred replicated data. [Learn more about security groups.](./drs-security-group.html) - - +A security group acts as a virtual firewall, which controls the inbound and outbound traffic of the staging area. The best practice is to have AWS Elastic Disaster Recovery automatically attach to and monitor the default AWS Elastic Disaster Recovery security group. This group opens inbound TCP Port 1500 for receiving the transferred replicated data. [Learn more about security groups.](./drs-security-group.html) @@ -96,3 +70 @@ Configurable volumes and security groups settings include: -Click **Next** to proceed to the third page of the wizard. - -On the third page of the wizard you will be asked to **Configure additional replication settings**. These include **Data routing and throttling** , **Point in time (PIT) policy** , and **Tags**. +On the third page of the wizard you can **Configure additional replication settings**. These include **Data routing and throttling** , **Point in time (PIT) policy** , and **Tags**. @@ -100 +72 @@ On the third page of the wizard you will be asked to **Configure additional repl - + * **Data routing and throttling** controls how data flows from the external server to the replication servers. If you choose not to use a private IP, your replication servers are automatically assigned a public IP and data flows over the public internet. [Learn more about data routing and throttling.](./data-routing.html) @@ -102 +74 @@ On the third page of the wizard you will be asked to **Configure additional repl -**Data routing and throttling** controls how data flows from the external server to the replication servers. If you choose not to use a private IP, your replication servers will be automatically assigned a public IP and data will flow over the public internet. [Learn more about data routing and throttling.](./data-routing.html) + * Point in Time (PIT) is a disaster recovery feature which allows launching an instance from a snapshot captured at a specific point in time. As source servers are replicated, snapshots are taken over time. The **Point in time (PIT) policy** section allows to configure a retention policy that determines which snapshots are not required after a defined duration. @@ -104 +76 @@ On the third page of the wizard you will be asked to **Configure additional repl - + * The **Tags** section allows you to add custom tags to resources created by AWS Elastic Disaster Recovery in your AWS account. @@ -106 +77,0 @@ On the third page of the wizard you will be asked to **Configure additional repl -Point in Time (PIT) is a disaster recovery feature which allows launching an instance from a snapshot captured at a specific point in time. As source servers are replicated, snapshots are taken over time. The **Point in time (PIT) policy** section allows to configure a retention policy that will determine which snapshots are not required after a defined duration. @@ -108 +78,0 @@ Point in Time (PIT) is a disaster recovery feature which allows launching an ins - @@ -110 +79,0 @@ Point in Time (PIT) is a disaster recovery feature which allows launching an ins -The **Tags** section allows you to add custom tags to resources created by AWS Elastic Disaster Recovery in your AWS account. @@ -112,3 +81 @@ The **Tags** section allows you to add custom tags to resources created by AWS E - - -Configurable additional settings include: +Additional configurable settings include: @@ -129 +96 @@ Configurable additional settings include: -Click Next to proceed to the fourth page of the wizard: **Set default DRS launch settings**. +On the fourth page of the wizard you can**Set default DRS launch settings**. @@ -133,2 +99,0 @@ Default launch settings define how drill or recovery instances are launched in A - - @@ -150,3 +115 @@ Configurable options include: -Click **Next** to proceed to the fifth page of the wizard: **Set default EC2 launch settings**. This page allows you to configure the default EC2 launch template which defines how instances are launched in AWS. Changes you make to the template will only affect new servers, but you can edit the template for multiple servers according to your preferences. [Learn more about default EC2 launch template.](./default-ec2-launch-template.html) The EC2 launch template includes basic and advanced settings. - - +The fifth page of the wizard: **Set default EC2 launch settings** is where you configure the default Amazon EC2 launch template which defines how instances are launched in AWS. Changes you make to the template only affect new servers, but you can edit the template for multiple servers according to your preferences. [Learn more about default EC2 launch template.](./default-ec2-launch-template.html) The EC2 launch template includes basic and advanced settings. @@ -167 +130 @@ Basic configurable options include: -Advance configurable options only need to change in specific operational scenarios. They include: +You only need to change advance configurable options in specific operational scenarios. They include: @@ -176,3 +139 @@ Advance configurable options only need to change in specific operational scenari -Choose **Next** to proceed to the sixth and final page of the wizard, where you will be asked to **Review and initialize**. - - +The sixth page is where you**Review and initialize**. @@ -180 +141 @@ Choose **Next** to proceed to the sixth and final page of the wizard, where you -Review the settings you configured. To change a specific setting, click **Edit**. +Review the settings you configured. To change a specific setting select **Edit** , which redirects you to the page in the wizard on which the setting appears. Go through the remaining pages to return to the **Review and create** page. @@ -182 +143 @@ Review the settings you configured. To change a specific setting, click **Edit** - +Once you have reviewed all of the settings you chose, select **Configure and initialize**. The default template is created and you return to the AWS Elastic Disaster Recovery console. @@ -186,9 +147 @@ Review the settings you configured. To change a specific setting, click **Edit** -Choosing **Edit** will redirect you to the page in the wizard on which the setting appears. You will then need to go through the remaining pages to return to the **Review and create** page. - -Once you have reviewed all of the settings you chose, click **Configure and initialize**. - -The default template will be created and you will be redirected to the AWS Elastic Disaster Recovery console. - -###### Note - -You can always edit the default replication settings by choosing **Settings** from the left-hand navigation menu. Remember that any new settings changes made will only be applied to newly added servers and not to existing servers. +You can always edit the default replication or launch settings by choosing the appropriate item from the **Settings** page, which you can open from the left-hand navigation menu. Remember that changes you make are only applied to newly added servers and not to existing servers. @@ -208 +161 @@ DRS agents can only be installed on instances that are in AWS Regions that are s -After you have added your source servers to the AWS Elastic Disaster Recovery console, you will need to configure the launch settings for each server. The launch settings are a set of instructions that determine how a recovery instance will be launched for each source server on AWS. You must configure the launch settings prior to launching test or recovery instances. You can use the default settings or configure the settings to fit your requirements. +After you have added your source servers to the AWS Elastic Disaster Recovery console, you need to configure the launch settings for each server. The launch settings are a set of instructions that determine how a recovery instance is launched for each source server on AWS. You must configure the launch settings prior to launching test or recovery instances. You can use the default settings or configure the settings to fit your requirements. @@ -212,3 +165 @@ After you have added your source servers to the AWS Elastic Disaster Recovery co -You can change the launch settings after a drill or recovery instance has been launched. You will need to launch a new Drill or Recovery instance for the new settings to take effect. - -You can access the launch settings by clicking on the hostname of a source server on the **Source servers** page. +You can change the launch settings after a drill or recovery instance has been launched. You need to launch a new Drill or Recovery instance for the new settings to take effect. @@ -216 +167 @@ You can access the launch settings by clicking on the hostname of a source serve - +You can access the launch settings by selecting the hostname of a source server on the **Source servers** page. @@ -220,3 +171 @@ Within the individual server view, navigate to the **Launch settings** tab. -Here you can see your **General launch settings** and your **EC2 launch template**. Click **Edit** to edit your launch settings or your EC2 launch template. - - +Here you can see your **General launch settings** and your **EC2 launch template**. Select **Edit** to edit your launch settings or your EC2 launch template. @@ -224 +173 @@ Here you can see your **General launch settings** and your **EC2 launch template -Launch settings are composed of the following: +Launch settings include: @@ -254 +203 @@ After you have added all of your source servers and configured their launch sett -You can drill one source server at a time, or simultaneously drill multiple source servers. For each source server, you will be informed of the success or failure of the drill. You can drill your source server as many times as you want. Each new drill first deletes any previously launched drill or recovery instance and dependent resources. Then, a new Drill instance is launched, which reflects the chosen Point-in-time state of the source server. After the drill, data replication continues as before. The new and modified data on the source server is transferred to the Staging Area Subnet and not to the Recovery instances that were launched during the test. +You can drill one source server at a time, or simultaneously drill multiple source servers. For each source server, you are informed of the success or failure of the drill. You can drill your source server as many times as you want. Each new drill first deletes any previously launched drill or recovery instance and dependent resources. Then, a new Drill instance is launched, which reflects the chosen Point-in-time state of the source server. After the drill, data replication continues as before. The new and modified data on the source server is transferred to the Staging Area Subnet and not to the Recovery instances that were launched during the test. @@ -260 +209 @@ You can drill one source server at a time, or simultaneously drill multiple sour - * Take into consideration that once a drill instance is launched, actual resources will be used in your AWS account and you will be billed for these resources. You can terminate the operation of launched Recovery instances once you verify that they are working properly without impact in order to data replication. + * Take into consideration that once a drill instance is launched, actual resources are used in your AWS account and you will be billed for these resources. You can terminate the operation of launched Recovery instances once you verify that they are working properly without impact in order to data replication. @@ -269 +218 @@ You can drill one source server at a time, or simultaneously drill multiple sour -Once you have finalized the testing of all of your source servers, you are ready for recovery. You should perform the recovery at a set date and time. The recovery will migrate your source servers to the recovery instances on AWS. +Once you have finalized the testing of all of your source servers, you are ready for recovery. You should perform the recovery at a set date and time. The recovery migrates your source servers to the recovery instances on AWS. @@ -271 +220 @@ Once you have finalized the testing of all of your source servers, you are ready -You can recover one source server at a time, or simultaneously recover multiple source servers. For each source server, you will be informed of the success or failure of the Recovery. For each new recovery, AWS Elastic Disaster Recovery first deletes any previously launched recovery instance and dependent resources. Then, it launches a new Recovery instance which reflects the most up-to-date state of the source server. After the Recovery, data replication continues as before. The new and modified data on the source server is transferred to the Staging Area Subnet, and not to the recovery instances that were launched during the recovery. +You can recover one source server at a time, or simultaneously recover multiple source servers. For each source server you are informed of the success or failure of the Recovery. For each new recovery, AWS Elastic Disaster Recovery first deletes any previously launched recovery instance and dependent resources. Then, it launches a new Recovery instance which reflects the most up-to-date state of the source server. After the Recovery, data replication continues as before. The new and modified data on the source server is transferred to the Staging Area Subnet, and not to the recovery instances that were launched during the recovery.