AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb link, fixed apostrophes, converted relative link to absolute URL, changed UI element formatting from bold to code style
Security assessment
All changes are editorial or presentational. The absolute URL improves link reliability, and UI reference formatting changes don't alter security procedures. No security-related content was added or modified in migration steps.
Diff
diff --git a/prescriptive-guidance/latest/migration-factory-cloudendure/step5.md b/prescriptive-guidance/latest/migration-factory-cloudendure/step5.md index b87baf4cc..8f288e729 100644 --- a//prescriptive-guidance/latest/migration-factory-cloudendure/step5.md +++ b//prescriptive-guidance/latest/migration-factory-cloudendure/step5.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) @@ -23 +23 @@ For detailed instructions, see [Verify the replication status](https://docs.aws. -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. Usually, you can shut down the source servers in the cutover window. Shutting down the source servers manually could take you 5 minutes per server, and, for large waves, it could take a few hours in total. Instead, you can run a Cloud Migration Factory automation script to shut down all your servers in the given wave. +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. Usually, you can shut down the source servers in the cutover window. Shutting down the source servers manually could take you 5 minutes per server, and, for large waves, it could take a few hours in total. Instead, you can run a Cloud Migration Factory automation script to shut down all your servers in the given wave. @@ -29 +29 @@ For detailed instructions, see [Shut down the in-scope source servers](https://d -After shutting down the source servers, you can launch the target EC2 server instances. As in [step 4](./step4.html), you can use a single **Launch servers** button to launch all the servers in the given wave in cutover mode. The only difference here is that you choose **Cutover** as the launch type. As in boot-up testing, the **Launch servers** button automates the following processes: +After shutting down the source servers, you can launch the target EC2 server instances. As in [step 4](https://docs.aws.amazon.com/prescriptive-guidance/latest/migration-factory-cloudendure/step4.html), you can use a single Launch servers button to launch all the servers in the given wave in cutover mode. The only difference here is that you choose `Cutover` as the launch type. As in boot-up testing, the Launch servers button automates the following processes: @@ -77 +77 @@ After the migration team completes operating system level testing, the applicati -Application testing, which takes place after the updates described in the previous section, is generally handled by the application owner or support team. It involves logging in to the new servers and confirming that the application works as expected. If it doesn’t, the application owner or support team works with the migration team to troubleshoot and fix issues. +Application testing, which takes place after the updates described in the previous section, is generally handled by the application owner or support team. It involves logging in to the new servers and confirming that the application works as expected. If it doesn't, the application owner or support team works with the migration team to troubleshoot and fix issues.