AWS solutions documentation change
Summary
Updated links from './step7.html' to './configure-migration-automation-server.html' and changed 'make sure you' to 'make sure that you' in multiple places
Security assessment
The changes are editorial improvements and link updates without any security context. There's no evidence of addressing vulnerabilities or security features.
Diff
diff --git a/solutions/latest/cloud-migration-factory-on-aws/list-of-automated-migration-activities-using-factory-web-console.md b/solutions/latest/cloud-migration-factory-on-aws/list-of-automated-migration-activities-using-factory-web-console.md index f40fdfe39..cac2e3e9d 100644 --- a//solutions/latest/cloud-migration-factory-on-aws/list-of-automated-migration-activities-using-factory-web-console.md +++ b//solutions/latest/cloud-migration-factory-on-aws/list-of-automated-migration-activities-using-factory-web-console.md @@ -13 +13 @@ The Cloud Migration Factory on AWS solution deploys automated migration activiti -Before starting any of the activities, make sure you read [User Guide - Run Automation from console](./run-automation-from-console.html) to understand how this works. Also, you must [Build an Automation server](./step7.html) and [create Windows and Linux users](./credentials-management.html) to run automation from the console. +Before starting any of the activities, make sure that you read [User Guide - Run Automation from console](./run-automation-from-console.html) to understand how this works. Also, you must [Build an Automation server](./configure-migration-automation-server.html) and [create Windows and Linux users](./credentials-management.html) to run automation from the console. @@ -27 +27 @@ Use the following procedure while signed in to the migration factory web console - 2. Enter **Job Name** , select **0-Check MGN Prerequisites** script and your automation server to run the script. If automation server does not exist, make sure you complete [Build a migration automation server](./step7.html). + 2. Enter **Job Name** , select **0-Check MGN Prerequisites** script and your automation server to run the script. If automation server does not exist, make sure that you complete [Build a migration automation server](./configure-migration-automation-server.html). @@ -46 +46 @@ Use the following procedure while signed in to the migration factory web console -Before you install the agent, make sure [AWS MGN is initialized in each target account](https://docs.aws.amazon.com/mgn/latest/ug/mgn-initialize.html) and region. +Before you install the agent, make sure that [AWS MGN is initialized in each target account](https://docs.aws.amazon.com/mgn/latest/ug/mgn-initialize.html) and region. @@ -52 +52 @@ Use the following procedure to automatically install the Replication agents in t - 2. Enter **Job Name** , select **1-Install MGN Agents** script and your automation server to run the script. If automation server does not exist, make sure you complete [Build a migration automation server](./step7.html). + 2. Enter **Job Name** , select **1-Install MGN Agents** script and your automation server to run the script. If automation server does not exist, make sure that you complete [Build a migration automation server](./configure-migration-automation-server.html). @@ -79 +79 @@ Use the following procedure to push the post-launch scripts to Windows machines. - 2. Enter Job Name, select **1-Copy Post Launch Scripts** script and your automation server to run the script. If automation server does not exist, make sure you complete [Build a migration automation server](./step7.html). + 2. Enter Job Name, select **1-Copy Post Launch Scripts** script and your automation server to run the script. If automation server does not exist, make sure that you complete [Build a migration automation server](./configure-migration-automation-server.html). @@ -98 +98 @@ Use the following procedure to verify the replication status. - 2. Enter Job Name, select **2-Verify Replication Status** script and your automation server to run the script. If automation server does not exist, make sure you complete [Build a migration automation server](./step7.html). + 2. Enter Job Name, select **2-Verify Replication Status** script and your automation server to run the script. If automation server does not exist, make sure that you complete [Build a migration automation server](./configure-migration-automation-server.html). @@ -181 +181 @@ Use the following procedure to verify the status of the target instance. - 3. Enter **Job Name** , select **3-Verify Instance Status** script and your automation server to run the script. If automation server does not exist, ensure you complete [Build a migration automation server](./step7.html). + 3. Enter **Job Name** , select **3-Verify Instance Status** script and your automation server to run the script. If automation server does not exist, ensure that you complete [Build a migration automation server](./configure-migration-automation-server.html). @@ -233 +233 @@ Use the following procedure to shut down all the source servers involved with th - 2. Enter Job Name, select **3-Shutdown All Servers** script and your automation server to run the script. If automation server does not exist, make sure you complete [Build a migration automation server](./step7.html). + 2. Enter Job Name, select **3-Shutdown All Servers** script and your automation server to run the script. If automation server does not exist, make sure that you complete [Build a migration automation server](./configure-migration-automation-server.html).