AWS mgn documentation change
Summary
Updated verb tenses and phrasing for consistency (e.g., changing 'will show' to 'shows', 'will be' to 'is'), removed redundant wording, and improved clarity in migration lifecycle documentation
Security assessment
Changes are grammatical improvements and consistency updates without any mention of security vulnerabilities, mitigations, or new security features. No evidence of addressing security issues or documenting security controls.
Diff
diff --git a/mgn/latest/ug/migration-dashboard.md b/mgn/latest/ug/migration-dashboard.md index a9be6094c..874cca667 100644 --- a//mgn/latest/ug/migration-dashboard.md +++ b//mgn/latest/ug/migration-dashboard.md @@ -68 +68 @@ The **Not ready** lifecycle state represents several possible scenarios: -A source server that has been added to AWS Application Migration Service will automatically begin the initial sync process after AWS Replication Agent installation. +A source server that has been added to AWS Application Migration Service automatically begins the initial sync process after AWS Replication Agent installation. @@ -70 +70 @@ A source server that has been added to AWS Application Migration Service will au -Data replication can only commence after all of the initial sync steps have been completed. The server will be in the **Not ready** lifecycle state until initial sync has been successfully completed. +Data replication can only commence after all of the initial sync steps have been completed. The server is in the **Not ready** lifecycle state until initial sync has been successfully completed. @@ -109 +109 @@ You can tell that a server has successfully completed the initial sync process t -On the main **Source servers** page, a newly added server that has completed initial sync for the first time will show **Ready for testing** under the **Migration lifecycle** column and **Healthy** under the **Data replication status** column. +On the main **Source servers** page, a newly added server that has completed initial sync for the first time shows **Ready for testing** under the **Migration lifecycle** column and **Healthy** under the **Data replication status** column. @@ -111 +111 @@ On the main **Source servers** page, a newly added server that has completed ini -On the individual server view, under the **Migration dashboard** tab, the **Lifecycle** section will show the **Ready for testing** status. The **Data replication status** section will show the **Healthy** status. +On the individual server view, under the **Migration dashboard** tab, the **Lifecycle** section shows the **Ready for testing** status. The **Data replication status** section shows the **Healthy** status. @@ -115 +115 @@ On the individual server view, under the **Migration dashboard** tab, the **Life -Servers will automatically undergo initial sync every time there is a network disconnect. +Servers automatically undergo initial sync every time there is a network disconnect. @@ -119 +119 @@ Servers will automatically undergo initial sync every time there is a network di -The server will be in the **Not ready** Lifecycle state until Initial Sync has been successfully completed. +The server is in the **Not ready** Lifecycle state until Initial Sync has been successfully completed. @@ -121 +121 @@ The server will be in the **Not ready** Lifecycle state until Initial Sync has b -If the Initial Sync process is stalled for any reason, the **Data replication status** section will indicate that replication has stalled. +If the Initial Sync process is stalled for any reason, the **Data replication status** section indicates that replication has stalled. @@ -123 +123 @@ If the Initial Sync process is stalled for any reason, the **Data replication st -Scroll down to the Replication initiation steps to see the step on which the error occurred. The step on which initial sync failed will be marked with a red "x". +Scroll down to the Replication initiation steps to see the step on which the error occurred. The step on which initial sync failed is marked with a red "x". @@ -125 +125 @@ Scroll down to the Replication initiation steps to see the step on which the err -You must fix the indicated issue before the initial sync process can continue. You will not be able to migrate your server and the server will remain in the **Not ready** state until the issue is resolved. +You must fix the indicated issue before the initial sync process can continue. You are not able to migrate your server and the server remains in the **Not ready** state until the issue is resolved. @@ -127 +127 @@ You must fix the indicated issue before the initial sync process can continue. Y -Each step has unique troubleshooting methods. +Each step has troubleshooting methods. @@ -131 +131 @@ Each step has unique troubleshooting methods. -Once the server has successfully completed the Initial Sync process, it will enter the **Ready for testing** lifecycle state. +Once the server has successfully completed the Initial Sync process, it enters the **Ready for testing** lifecycle state. @@ -133 +133 @@ Once the server has successfully completed the Initial Sync process, it will ent -The **Data replication status** box will show a **Healthy** state, indicating that the server is healthy. +The **Data replication status** box shows a **Healthy** state, indicating that the server is healthy. @@ -135 +135 @@ The **Data replication status** box will show a **Healthy** state, indicating th -You can now launch a test instance for this server. The server will stay in the **Ready for testing** lifecycle state until you launch a Test instance for the server. +You can now launch a test instance for this server. The server stays in the **Ready for testing** lifecycle state until you launch a Test instance for the server. @@ -139 +139 @@ You can now launch a test instance for this server. The server will stay in the -Once you have launched a Test instance for your server, the migration dashboard will show the **Test in progress** lifecycle state. +Once you have launched a Test instance for your server, the migration dashboard shows the **Test in progress** lifecycle state. @@ -143 +143 @@ Within the **Lifecycle** box, you can review the **Launch status** and **Last te - * The **Launch status** field will show the time of the test instance launch. While the Testing instance is being launched, the **Launch status** field will show **Waiting**. + * The **Launch status** field shows the time of the test instance launch. While the Testing instance is being launched, the **Launch status** field shows **Waiting**. @@ -145 +145 @@ Within the **Lifecycle** box, you can review the **Launch status** and **Last te - * Once the test instance has been launched, the Launch status will show **Launched**. Wait for the instance to boot and then choose **View in EC2 console** link to open the EC2 Console in a new tab, in order to view and monitor your launched test instance. + * Once the test instance has been launched, the Launch status shows **Launched**. Wait for the instance to boot and then choose **View in EC2 console** link to open the EC2 console in a new tab, in order to view and monitor your launched test instance. @@ -147 +147 @@ Within the **Lifecycle** box, you can review the **Launch status** and **Last te - * The AWS EC2 Console will open in a new tab and will automatically search for and display your test instance. + * The AWS EC2 console opens in a new tab and automatically searches for and displays your test instance. @@ -149 +149 @@ Within the **Lifecycle** box, you can review the **Launch status** and **Last te - * The **Last test** field will show the date of the last test. To review the test launch details, click **Job ID** , which will open the job within the **Launch History** page in a new tab. + * The **Last test** field shows the date of the last test. To review the test launch details, click **Job ID** , which opens the job within the **Launch History** page in a new tab. @@ -151 +151 @@ Within the **Lifecycle** box, you can review the **Launch status** and **Last te - * On the main **Source servers** page, the **Migration lifecycle** column will show **Ready for testing** and the **Next step** column will show **Launch test instance**. + * On the main **Source servers** page, the **Migration lifecycle** column shows **Ready for testing** and the **Next step** column shows **Launch test instance**. @@ -153 +153 @@ Within the **Lifecycle** box, you can review the **Launch status** and **Last te - * The server will stay in the **Test in progress** Lifecycle state until you finalize your testing and mark the server as **Ready for cutover**. + * The server stays in the **Test in progress** Lifecycle state until you finalize your testing and mark the server as **Ready for cutover**. @@ -160 +160 @@ You can use these indicators to verify that your test instance was successfully - * On the **Server Details > Lifecycle** pane, the Launch status will state **Launched**. + * On the **Server Details > Lifecycle** pane, the Launch status states **Launched**. @@ -162 +162 @@ You can use these indicators to verify that your test instance was successfully - * On the main **Source servers** page, the **Alerts** column will show the **Launched** status. + * On the main **Source servers** page, the **Alerts** column shows the **Launched** status. @@ -169 +169 @@ You can use these indicators to verify that your test instance was successfully -After you have finalized your testing, the Migration dashboard will show the **Ready for cutover** lifecycle state. +After you have finalized your testing, the Migration dashboard shows the **Ready for cutover** lifecycle state. @@ -171 +171 @@ After you have finalized your testing, the Migration dashboard will show the **R - * The **Launch status** field will show the time of the last test instance launch. Click on the **View in EC2 console** link to open the EC2 Console in a new tab in order to view and monitor your launched Test instance. + * The **Launch status** field shows the time of the last test instance launch. Click on the **View in EC2 console** link to open the EC2 console in a new tab in order to view and monitor your launched Test instance. @@ -173 +173 @@ After you have finalized your testing, the Migration dashboard will show the **R - * The **Last test** field will show the date the last test was started. You can review the test launch details by clicking on the **Job ID**. This will open the relevant Job. + * The **Last test** field shows the date the last test was started. You can review the test launch details by clicking on the **Job ID**. This opens the relevant Job. @@ -175 +175 @@ After you have finalized your testing, the Migration dashboard will show the **R - * The **Cutover** field will show the date of the last cutover instance launch, if applicable. You can review the cutover launch details by clicking on the **Job ID**. This will open the relevant Job. + * The **Cutover** field shows the date of the last cutover instance launch, if applicable. You can review the cutover launch details by clicking on the **Job ID**. This opens the relevant Job. @@ -177 +177 @@ After you have finalized your testing, the Migration dashboard will show the **R - * On the **Source servers** page, the **Migration lifecycle** column will show **Ready for cutover** and the**Next step** column will show **Terminate test instance; Launch cutover instance**. + * On the **Source servers** page, the **Migration lifecycle** column shows **Ready for cutover** and the**Next step** column shows **Terminate test instance; Launch cutover instance**. @@ -182 +182 @@ After you have finalized your testing, the Migration dashboard will show the **R -The server will stay in the **Ready for cutover** Lifecycle state until you launch a cutover instance. +The server stays in the **Ready for cutover** Lifecycle state until you launch a cutover instance. @@ -186 +186 @@ The server will stay in the **Ready for cutover** Lifecycle state until you laun -Once you have launched a cutover instance for your server, the Migration dashboard will show the **Cutover in progress** Lifecycle state. +Once you have launched a cutover instance for your server, the Migration dashboard shows the **Cutover in progress** Lifecycle state. @@ -188 +188 @@ Once you have launched a cutover instance for your server, the Migration dashboa - * The **Launch status** field will show the last time of cutover launch. Click on the **View in EC2 console** link to open the EC2 Console in a new tab in order to view and monitor your launched cutover instance. + * The **Launch status** field shows the last time of cutover launch. Click on the **View in EC2 console** link to open the EC2 console in a new tab in order to view and monitor your launched cutover instance. @@ -190 +190 @@ Once you have launched a cutover instance for your server, the Migration dashboa - * The **Last test** field will show the date the last test was started. You can review the test launch details by clicking on the **Job ID**. This will open the Job. + * The **Last test** field shows the date the last test was started. You can review the test launch details by clicking on the **Job ID**. This opens the Job. @@ -192 +192 @@ Once you have launched a cutover instance for your server, the Migration dashboa - * The **Cutover** field will show the date of the last cutover instance launch. You can review the cutover launch details by clicking on the **Job ID**. This will open the Job. + * The **Cutover** field shows the date of the last cutover instance launch. You can review the cutover launch details by clicking on the **Job ID**. This opens the Job. @@ -194 +194 @@ Once you have launched a cutover instance for your server, the Migration dashboa - * On the **Source servers** page, the **Migration lifecycle** column will show **Cutover in progress** and the **Next step** column will show **Complete the cutover**. + * On the **Source servers** page, the **Migration lifecycle** column shows **Cutover in progress** and the **Next step** column shows **Complete the cutover**. @@ -199 +199 @@ Once you have launched a cutover instance for your server, the Migration dashboa -The server will stay in the **Cutover in progress** Lifecycle state until you complete the cutover. +The server stays in the **Cutover in progress** Lifecycle state until you complete the cutover. @@ -203 +203 @@ The server will stay in the **Cutover in progress** Lifecycle state until you co -Once you have completed your cutover instance launch for your server, the Migration dashboard will show the **Cutover complete** lifecycle state. This is the final state in the migration lifecycle. This state indicates that you have successfully migrated your source server to AWS. +Once you have completed your cutover instance launch for your server, the Migration dashboard shows the **Cutover complete** lifecycle state. This is the final state in the migration lifecycle. This state indicates that you have successfully migrated your source server to AWS. @@ -205 +205 @@ Once you have completed your cutover instance launch for your server, the Migrat - * The **Launch status** field will show **Launched**. Click on the **View in EC2 console** link to open the EC2 Console in a new tab in order to view and monitor your launched cutover instance. + * The **Launch status** field shows **Launched**. Click on the **View in EC2 console** link to open the EC2 console in a new tab in order to view and monitor your launched cutover instance. @@ -207 +207 @@ Once you have completed your cutover instance launch for your server, the Migrat - * The **Last test** field will show the date the last test was started. You can review the test launch details by clicking on the **Job ID**. This will open the Job. + * The **Last test** field shows the date the last test was started. You can review the test launch details by clicking on the **Job ID**. This opens the Job. @@ -209 +209 @@ Once you have completed your cutover instance launch for your server, the Migrat - * The **Cutover** field will show the date you finalized your Cutover instance launch. You can review the cutover launch details by clicking on the **Job ID**. This will open the Job. + * The **Cutover** field shows the date you finalized your Cutover instance launch. You can review the cutover launch details by clicking on the **Job ID**. This opens the Job. @@ -211 +211 @@ Once you have completed your cutover instance launch for your server, the Migrat - * The AWS Application Migration Service Console will automatically stop data replication for the source servers that were cutover in order to save resource costs. + * The AWS Application Migration Service console automatically stops data replication for the source servers that were cutover in order to save resource costs. @@ -213 +213 @@ Once you have completed your cutover instance launch for your server, the Migrat - * On the **Source servers** page, the selected source servers' **Migration lifecycle** column will show the **Cutover complete** status, the **Data replication status** column will show **Disconnected** and the **Next step** column will show **Mark as archived**. + * On the **Source servers** page, the selected source servers' **Migration lifecycle** column shows the **Cutover complete** status, the **Data replication status** column shows **Disconnected** and the **Next step** column shows **Mark as archived**. @@ -245 +245 @@ 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. @@ -247 +247 @@ Data replication can be in one of several states, as indicated in the panel titl - * **Healthy:** all data has been copied and any changes at source are continuously being replicated (data is flowing). + * **Healthy:** all data has been copied and any changes at the source are continuously being replicated (data is flowing). @@ -249 +249 @@ 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 of the blocks on all of the replicated disks. This is similar to the initial sync but faster because only changed blocks are copied. A rescan progress bar is displayed. @@ -251 +251 @@ 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. You may need to intervene. When stalled, either the initial sync never completes, or the difference between the state of the replicated data and that of the source server will continue to grow. When the state is stalled, then the replication initiation checklist is shown and indicates where the error occurred that caused the stall. @@ -260 +260 @@ 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 will be from state at source. Normally this should be none. @@ -269 +269 @@ 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 shows a **Healthy** status. @@ -271 +271 @@ 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 there are initialization, replication, or connectivity errors, the **Data replication status** section shows the cause of the issue (for example, a stall). @@ -273 +273 @@ If there are initialization, replication, or connectivity errors, the **Data rep -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 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**. @@ -285 +285 @@ The status includes: - * Start time – the start time of the execution of the action script. This column will be empty for actions that have not yet started execution. + * Start time – the start time of the execution of the action script. This column is empty for actions that have not yet started execution. @@ -287 +287 @@ The status includes: - * End time – the end time of the execution of the action script. This column will be empty for actions that have not yet completed execution. + * End time – the end time of the execution of the action script. This column is empty for actions that have not yet completed execution. @@ -289 +289 @@ The status includes: - * Details – error messages will be shown in this column. + * Details – error messages are shown in this column. @@ -325 +325 @@ The **Actions** menu allows you to perform these actions: - * **Add servers** – Choosing the **Add servers** option will open the Add servers prompt, through which you can construct a custom installation command to use when adding Linux or Windows source servers. + * **Add servers** – Choosing the **Add servers** option opens the Add servers prompt, through which you can construct a custom installation command to use when adding Linux or Windows source servers. @@ -333 +333 @@ To construct a custom installation command, take these steps: -If you want to install the AWS Replication Agent on a legacy Windows OS (Windows Server 2003, Windows Server 2008 or Windows Server 2008 R2), you must choose the**Legacy OS: Windows Server 2003 or Windows Server 2008** box. This will download a unique version of the AWS Replication Agent installer that is only valid for legacy Windows OSs (`AwsReplicationWindowsLegacyInstaller.exe`). **Do not** use this installer file to install the agent on any other OS types. +If you want to install the AWS Replication Agent on a legacy Windows OS (Windows Server 2003, Windows Server 2008 or Windows Server 2008 R2), you must choose the**Legacy OS: Windows Server 2003 or Windows Server 2008** box. This downloads a unique version of the AWS Replication Agent installer that is only valid for legacy Windows OSs (`AwsReplicationWindowsLegacyInstaller.exe`). **Do not** use this installer file to install the agent on any other OS types. @@ -335 +335 @@ If you want to install the AWS Replication Agent on a legacy Windows OS (Windows - 2. Select your replication preferences for the source server. The selected preferences will be added as installation prompts to the custom installation command that will be generated by this form. + 2. Select your replication preferences for the source server. The selected preferences are added as installation prompts to the custom installation command that are generated by this form. @@ -339 +339 @@ Choose the **Replicate all disks** option to replicate all of the disks of the s -Select the **Choose which disks to replicate** option to choose which specific disks you want to replicate. You will be prompted to select which disks to replicate during agent installation. +Select the **Choose which disks to replicate** option to choose which specific disks you want to replicate. You are prompted to select which disks to replicate during agent installation. @@ -341 +341 @@ Select the **Choose which disks to replicate** option to choose which specific d - 3. Enter the credentials that [you previously generated for AWS Replication Agent installation](./credentials.html). The form will not send the secret, but will add it to the installation command. + 3. Enter the credentials that [you previously generated for AWS Replication Agent installation](./credentials.html). The form does not send the secret, but does add it to the installation command. @@ -345 +345 @@ Select the **Choose which disks to replicate** option to choose which specific d - 5. If you are adding a Windows source server to AWS MGN, download the installer onto the source server. The installer will be downloaded from the AWS Region of your account. If you're adding a Linux source server, skip this step. + 5. If you are adding a Windows source server to AWS MGN, download the installer onto the source server. The installer is downloaded from the AWS Region of your account. If you're adding a Linux source server, skip this step. @@ -357 +357 @@ 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. If you need to restart data replication for this server, you will need to reinstall the agent. This action will not affect any test or cutover 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. If you need to restart data replication for this server, you need to reinstall the agent. This action does not affect any test or cutover 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. @@ -359 +359 @@ This will uninstall the AWS Replication Agent from the source server and data re - * **Mark as archived** – Choose this option to archive the server. You should only archive servers for which you have already performed a cutover. Archived servers will be removed from the main **Source servers** page, but can still be accessed through filtering options. + * **Mark as archived** – Choose this option to archive the server. You should only archive servers for which you have already performed a cutover. Archived servers are removed from the main **Source servers** page, but can still be accessed through filtering options. @@ -363 +363 @@ On the **Archive X servers** dialog, select **Archive**. -To see your archived servers, open the **Preferences** menu by clicking the gear button. Select the **Show only archived servers** option and click **Confirm**. You will now be able to see all of your archived servers. Unselect this option to see your non-archived servers. +To see your archived servers, open the **Preferences** menu by clicking the gear button. Select the **Show only archived servers** option and click **Confirm**. You can now see all of your archived servers. Unselect this option to see your non-archived servers. @@ -385 +385 @@ When the **Launch test instances for X** servers dialog appears, click **Launch* -The AWS Application Migration Service Console will indicate **1 launch job complete** after the test has been completed successfully. +The AWS Application Migration Service console indicates **1 launch job complete** after the test has been completed successfully. @@ -391 +391 @@ When the **Mark X servers as "Ready for cutover"** dialog appears, select whethe -The AWS Application Migration Service Console will indicate that testing has been finalized. The selected source servers' **Migration lifecycle** column will show the **Ready for cutover** status and the launched Test instances will be deleted if that option was selected. +The AWS Application Migration Service console indicates that testing has been finalized. The selected source servers' **Migration lifecycle** column shows the **Ready for cutover** status and the launched test instances are deleted if that option was selected. @@ -397 +397 @@ When the **Revert testing for X servers** dialog appears, select whether you wan -The AWS Application Migration Service Console will indicate that testing has been reverted. The selected source servers' **Migration lifecycle** column will show the **Ready for testing** status and the launched Test instances will be deleted if that option was selected. +The AWS Application Migration Service console indicates that testing has been reverted. The selected source servers' **Migration lifecycle** column shows the **Ready for testing** status and the launched test instances are deleted if that option was selected. @@ -403 +403 @@ When the **Launch cutover instances for X** **servers** dialog appears, click ** -The AWS Application Migration Service Console will indicate **1 launch job complete** after the cutover has been completed successfully. +The AWS Application Migration Service console indicates **1 launch job complete** after the cutover has been completed successfully. @@ -405 +405 @@ The AWS Application Migration Service Console will indicate **1 launch job compl -This will change your source servers' **Migration lifecycle** status to **Cutover in progress** , indicating that the cutover is in progress but has not yet been finalized. +This changes your source servers' **Migration lifecycle** status to **Cutover in progress** , indicating that the cutover is in progress but has not yet been finalized. @@ -409 +409 @@ This will change your source servers' **Migration lifecycle** status to **Cutove