AWS prescriptive-guidance documentation change
Summary
Updated documentation links, simplified section headers, fixed apostrophe formatting, clarified migration pattern names (e.g. AWS DataSync -> AWS DataSync Discovery), and improved stage/task naming consistency
Security assessment
Changes are primarily editorial improvements, formatting fixes, and documentation structure updates. No security vulnerabilities, controls, or security-specific features are mentioned or modified. The addition of 'Discovery' to AWS DataSync appears to be a product name clarification rather than a security-related update.
Diff
diff --git a/prescriptive-guidance/latest/large-migration-portfolio-playbook/discovery.md b/prescriptive-guidance/latest/large-migration-portfolio-playbook/discovery.md index 320d8b97d..633d9d81e 100644 --- a//prescriptive-guidance/latest/large-migration-portfolio-playbook/discovery.md +++ b//prescriptive-guidance/latest/large-migration-portfolio-playbook/discovery.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Portfolio playbook for AWS large migrations](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Portfolio playbook for AWS large migrations](introduction.html) @@ -9 +9 @@ Step 1: Validate the discovery dataStep 2: Identify the business and technical d -# Task 1: Performing the initial discovery and validating the migration strategy +# Task 1: Performing the initial discovery @@ -26 +26 @@ The first step of portfolio assessment in a large migration project is to unders -In the mobilize phase, you might have completed your initial portfolio assessment, and if so, you can reuse that discovery data in the migrate phase. If not, don’t worry. This playbook will walk you through what is needed to support your large migration. +In the mobilize phase, you might have completed your initial portfolio assessment, and if so, you can reuse that discovery data in the migrate phase. If not, don't worry. This playbook will walk you through what is needed to support your large migration. @@ -112 +112 @@ The following are the three primary types of metadata that are required to suppo -It is important to understand your current discovery data before making any decisions. You likely don’t have all of the information at this stage of the migration. This playbook helps you define the metadata requirements and helps you collect the metadata efficiently. Ask yourself the following questions to identify what metadata is currently available and where it might be located: +It is important to understand your current discovery data before making any decisions. You likely don't have all of the information at this stage of the migration. This playbook helps you define the metadata requirements and helps you collect the metadata efficiently. Ask yourself the following questions to identify what metadata is currently available and where it might be located: @@ -149 +149 @@ _Business drivers_ are factors related to business goals or limitations that you - * **Flexibility** – You need to move to the cloud as a strategic direction in order to prepare for change in the business’s future. + * **Flexibility** –You need to move to the cloud as a strategic direction in order to prepare for change in the business's future. @@ -153 +153 @@ _Business drivers_ are factors related to business goals or limitations that you - * **Using data intelligently** – You want to take advantage of cloud-based artificial intelligence, machine learning, and Internet of Things (IoT) that can forecast your company’s growth and provide insights into customer behavior. + * **Using data intelligently** – You want to take advantage of cloud-based artificial intelligence, machine learning, and Internet of Things (IoT) that can forecast your company's growth and provide insights into customer behavior. @@ -183 +183 @@ _Technical drivers_ are factors related to technical goals or limitations that y - 1. In the [portfolio playbook templates](samples/portfolio-playbook-templates.zip), open the _Runbook template for application prioritization_ (Microsoft Word format). + 1. Open the attached _Runbook template for application prioritization_ (Microsoft Word format). @@ -194 +194 @@ _Technical drivers_ are factors related to technical goals or limitations that y -Selecting migration strategies is critical to a large migration. You must verify that the migration strategies you select meet organizational expectations, limitations, and requirements. For more information about the available migration strategies, see the [Guide for AWS large migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-guide/). +Selecting migration strategies is critical to a large migration. You must verify that the migration strategies you select meet organizational expectations, limitations, and requirements. For more information about the available migration strategies, see the [Guide for AWS large migrations](https://docs.aws.amazon.com/prescriptive-guidance/latest/large-migration-guide/welcome.html). @@ -271 +271 @@ A _migration pattern_ is a repeatable migration task that details the migration - * AWS DataSync + * AWS DataSync Discovery @@ -296 +296 @@ ID | Strategy | Pattern -3 | Replatform | Replatform to Amazon EC2 using CloudFormation +3| Replatform| Replatform to Amazon EC2 using AWS CloudFormation @@ -301 +301 @@ CloudFormation templates build new infrastructure in the AWS Cloud. -4 | Replatform | Replatform to Amazon EFS using AWS DataSync or AWS Transfer Family +4| Replatform| Replatform to Amazon EFS using AWS DataSync Discovery or AWS Transfer Family @@ -356 +356 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Stage 1: Initializing +Stage 1: Initializing a large migration @@ -358 +358 @@ Stage 1: Initializing -Task 2: Defining processes for identifying, collecting, and storing metadata +Task 2: Defining metadata processes