AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb link, fixed apostrophe formatting, changed button reference formatting, updated image path, and reworded instance status verification process
Security assessment
Changes include typographical fixes, image path updates, and UI reference formatting. No security concepts were added or modified. The instance status verification process remains functionally identical without security implications.
Diff
diff --git a/prescriptive-guidance/latest/migration-factory-cloudendure/step4.md b/prescriptive-guidance/latest/migration-factory-cloudendure/step4.md index dd353eef2..381433786 100644 --- a//prescriptive-guidance/latest/migration-factory-cloudendure/step4.md +++ b//prescriptive-guidance/latest/migration-factory-cloudendure/step4.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Automating large-scale server migrations with Cloud Migration Factory](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Automating large-scale server migrations with Cloud Migration Factory](introduction.html) @@ -15 +15 @@ After data replication is complete on all servers, you need to test the instance -If you’re migrating a small number of servers, you can select the server and launch it directly from the MGN console. However, for large-scale migrations, it’s more efficient to launch all the servers together from the Cloud Migration Factory web console. This console provides a single **Launch servers** button to automate the following processes: +If you're migrating a small number of servers, you can select the server and launch it directly from the MGN console. However, for large-scale migrations, it's more efficient to launch all the servers together from the Cloud Migration Factory web console. This console provides a single Launch servers button to automate the following processes: @@ -30 +30 @@ For detailed instructions, see [Launch instances for testing](https://docs.aws.a -It will take 15–30 minutes for the server instances to boot up. You can check the status manually by logging into the Amazon EC2 console, searching for the server name, and checking the status. You will see a “2/2 checks passed” message, which indicates that the instance is healthy from an infrastructure perspective. +It will take 15–30 minutes for the server instances to boot up. You can check the status manually by logging into the Amazon EC2 console, searching for the server name, and checking the status. You will see a "2/2 checks passed" message, which indicates that the instance is healthy from an infrastructure perspective. @@ -32 +32 @@ It will take 15–30 minutes for the server instances to boot up. You can check - + @@ -34 +34 @@ It will take 15–30 minutes for the server instances to boot up. You can check -However, for a large-scale migration, it’s time-consuming to check the status of each instance, so Cloud Migration Factory provides a single automation script to verify the 2/2 status for all machines in a given wave. +However, for a large-scale migration, it's time-consuming to check the status of each instance, so Cloud Migration Factory provides a single automation script to verify the 2/2 status for all machines in a given wave.