AWS prescriptive-guidance documentation change
Summary
Updated navigation links, replaced references to external template downloads with 'attached' templates, corrected blog post URL, improved heading structure, and consolidated automation recommendation content.
Security assessment
Changes involve navigation updates, content restructuring, and broken link fixes without addressing security vulnerabilities or weaknesses. No security advisories, vulnerability mitigations, or security feature enhancements were introduced.
Diff
diff --git a/prescriptive-guidance/latest/large-migration-migration-playbook/task-two-drafts-runbooks.md b/prescriptive-guidance/latest/large-migration-migration-playbook/task-two-drafts-runbooks.md index 1d6d7ae6e..934106bc5 100644 --- a//prescriptive-guidance/latest/large-migration-migration-playbook/task-two-drafts-runbooks.md +++ b//prescriptive-guidance/latest/large-migration-migration-playbook/task-two-drafts-runbooks.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migration playbook for AWS large migrations](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migration playbook for AWS large migrations](introduction.html) @@ -13 +13 @@ In this task, you draft and review migration runbooks for each migration pattern -You can use the provided runbook templates available in the [migration playbook templates](samples/migration-playbook-templates.zip) and customize them for your environment. For migration patterns that are repeated frequently, we recommend using the _Rehost migration runbook template_ (Microsoft Word format), and for patterns that are one-off or very simple, we recommend the _Rehost migration task list template_ (Microsoft Excel format). You can also use a task list to track the status of tasks that are documented in a runbook. For more information, see [About the runbooks, tools, and templates](./welcome.html#about-components). +You can use the attached runbook templates and customize them for your environment. For migration patterns that are repeated frequently, we recommend using the _Rehost migration runbook template_ (Microsoft Word format), and for patterns that are one-off or very simple, we recommend the _Rehost migration task list template_ (Microsoft Excel format). You can also use a task list to track the status of tasks that are documented in a runbook. For more information, see [About the runbooks, tools, and templates](./introduction.html#about-components). @@ -28 +28 @@ In this step, you draft runbooks for each of your migration patterns. A complete - 1. Open the _Rehost migration runbook template_ (Microsoft Word format), available in the [migration playbook templates](samples/migration-playbook-templates.zip). + 1. Open the attached _Rehost migration runbook template_ (Microsoft Word format). @@ -32 +32 @@ In this step, you draft runbooks for each of your migration patterns. A complete - * Standard migration instructions for the selected service – You can typically find the information needed to complete your template in AWS documentation. For example, see the following: + * **Standard migration instructions for the selected service** – You can typically find the information needed to complete your template in [AWS documentation](https://docs.aws.amazon.com/index.html). For example, see the following: @@ -34 +34 @@ In this step, you draft runbooks for each of your migration patterns. A complete - * [How to use the new AWS Transform MGN for lift-and-shift migrations](https://aws.amazon.com/blogs/aws/how-to-use-the-new-aws-application-migration-service-for-lift-and-shift-migrations/) + * [How to use the new AWS Application Migration Service for lift-and-shift migrations](https://aws.amazon.com/blogs/aws/how-to-use-the-new-aws-application-migration-service-for-lift-and-shift-migrations/) @@ -40 +40 @@ In this step, you draft runbooks for each of your migration patterns. A complete - * Tasks that are unique to your IT environment – Record the tasks that are unique to your IT operations and environment. The goal is that a new person joining your migration teams can follow the runbook with minimal learning curve. For example, what monitoring software do you need to install on the target machine after cutover? Which Domain Name System (DNS) server do you use for that subnet? How do you submit a request for change (RFC)? + * **Tasks that are unique to your IT environment** – Record the tasks that are unique to your IT operations and environment. The goal is that a new person joining your migration teams can follow the runbook with minimal learning curve. For example, what monitoring software do you need to install on the target machine after cutover? Which Domain Name System (DNS) server do you use for that subnet? How do you submit a request for change (RFC)? @@ -42 +42 @@ In this step, you draft runbooks for each of your migration patterns. A complete - * Cutover tasks – Every environment has a slightly different cutover process. It is important to document all the steps for cutover in your environment because you want everyone to follow the same process. Documenting these steps minimizes time spent in the cutover window and helps you plan the amount of time needed to complete the cutover. + * **Cutover tasks** – Every environment has a slightly different cutover process. It is important to document all the steps for cutover in your environment because you want everyone to follow the same process. Documenting these steps minimizes time spent in the cutover window and helps you plan the amount of time needed to complete the cutover. @@ -51 +51 @@ Runbook and task list templates cover the majority of the migration tasks, or th -**Connectivity** +### Connectivity @@ -78 +66 @@ Runbook and task list templates cover the majority of the migration tasks, or th -**Permissions and change management** +### Permissions and change management @@ -110 +83 @@ Runbook and task list templates cover the majority of the migration tasks, or th -**Migration implementation and cutover** +### Migration implementation and cutover @@ -151,3 +106 @@ Some of these tasks might sound trivial, but knowledge and permissions vary in a -We highly recommend using automation to accelerate your large migration. Using a migration factory model simplifies and reduces the number of issues with repetitive tasks, especially for rehost and replatform migration patterns. - -[AWS Cloud Migration Factory Solution](https://aws.amazon.com//solutions/implementations/aws-cloudendure-migration-factory-solution/) was designed to help customers migrate at scale with automation. You can deploy the solution and use predefined automation scripts in your runbook. +We highly recommend using automation to accelerate your large migration. Using a migration factory model simplifies and reduces the number of issues with repetitive tasks, especially for rehost and replatform migration patterns. [AWS Cloud Migration Factory Solution](https://aws.amazon.com/solutions/implementations/aws-cloudendure-migration-factory-solution/) was designed to help customers migrate at scale with automation. You can deploy the solution and use predefined automation scripts in your runbook.