AWS solutions documentation change
Summary
Formatting changes including adding bold headers before images, fixing image alt text casing, correcting apostrophes in text, standardizing command-line argument syntax (hyphen consistency), adjusting list numbering, and minor title capitalization change
Security assessment
Changes are purely documentation formatting improvements and command syntax corrections. No security-related content additions or vulnerability references found.
Diff
diff --git a/solutions/latest/cloud-migration-factory-on-aws/list-of-automated-migration-activities-using-command-prompt.md index 55f5ce660..94e475437 100644 --- a/solutions/latest/cloud-migration-factory-on-aws/list-of-automated-migration-activities-using-command-prompt.md +++ b/solutions/latest/cloud-migration-factory-on-aws/list-of-automated-migration-activities-using-command-prompt.md @@ -68 +65,3 @@ Once the checks are completed, the script will return a final result for each se - +**Script final result** + + @@ -107 +106,3 @@ The installation starts on the Windows, then proceeds to the Linux for each AWS - +**Install replication agents** + + @@ -118 +119,3 @@ Results are displayed after the script finishes installing the replication agent - +**Agent install result** + + @@ -183 +186,3 @@ The following screenshot of an example wave shows that all servers in the curren - +**Agent install result** + + @@ -226 +231 @@ If your target instances fail the 2/2 health checks the first time, it may be du -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. @@ -234 +239 @@ Use the following procedure from the migration automation server to shut down al - Python 3-Shutdown-all-servers.py –Waveid <wave-id> + Python 3-Shutdown-all-servers.py -Waveid <wave-id> @@ -259 +264 @@ Use the following procedure from the migration automation server to retrieve the - Python 4-Get-instance-IP.py -–Waveid <wave-id> + Python 4-Get-instance-IP.py --Waveid <wave-id> @@ -265,4 +270 @@ Replace `<wave-id>` with the appropriate Wave ID value to get the new IP address - - - - 1. The script will then return the target server IP. + 2. The script will then return the target server IP. @@ -291 +293 @@ Use the following procedure from the migration automation server to verify the c - Python 4-Verify-server-connection.py -–Waveid <wave-id> + Python 4-Verify-server-connection.py --Waveid <wave-id> @@ -312 +314 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -List of automated migration activities using factory web console +List of automated migration activities using Migration Factory web console