AWS solutions documentation change
Summary
Formatting updates including adding bold headers before images, fixing markdown syntax for emphasis, correcting image paths, improving list formatting, and fixing apostrophe usage
Security assessment
Changes focus on documentation presentation and markdown syntax. No security-related content additions or references to security vulnerabilities detected in the diff.
Diff
diff --git a/solutions/latest/cloud-migration-factory-on-aws/list-of-automated-migration-activities-using-factory-web-console.md index 3654f7629..51ded7459 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 @@ -11 +11 @@ 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 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. @@ -36 +36,3 @@ Use the following procedure while signed in to the migration factory web console - +**Migration status** + + @@ -56 +58,3 @@ Use the following procedure to automatically install the Replication agents in t - +**Migration status** + + @@ -101 +105,3 @@ Use the following procedure to verify the replication status. - +**Data replication status** + + @@ -117 +123 @@ Use the following procedure to validate EC2 launch template. - 3. Select **Validate Launch Template** for the **Action** , then select All**applications.** + 3. Select **Validate Launch Template *for the *Action** , then select All* applications.* @@ -153 +159,3 @@ Use the following procedure to launch test instances. - +**Wave action success** + + @@ -180 +188,3 @@ Use the following procedure to verify the status of the target instance. - +**AWS Migration Management dashboard showing server list with migration status for 5 servers.** + + @@ -209 +219,3 @@ After some time, the validation will return a successful result. - +**Wave action ready for cutover** + + @@ -213 +225 @@ After some time, the validation will return a successful result. -This activity shuts down the in-scope source servers involved with the migration. After you verify the source servers’ replication status, you are ready to shut down the source servers to stop transactions from the client applications to the servers. You can shut down the source servers in the cutover window. Shutting down the source servers manually could take five minutes per server, and, for large waves, it could take a few hours in total. Instead, you can run this automation script to shut down all your servers in the given wave. +This activity shuts down the in-scope source servers involved with the migration. After you verify the source servers' replication status, you are ready to shut down the source servers to stop transactions from the client applications to the servers. You can shut down the source servers in the cutover window. Shutting down the source servers manually could take five minutes per server, and, for large waves, it could take a few hours in total. Instead, you can run this automation script to shut down all your servers in the given wave.