AWS prescriptive-guidance documentation change
Summary
Updated navigation link, corrected typos ('Impement' to 'Implement'), improved table formatting with bold headers, updated AWS service names ('AWS Transform MGN' to 'AWS Application Migration Service'), and fixed punctuation.
Security assessment
Changes involve documentation corrections, formatting improvements, and service name updates without addressing security vulnerabilities or introducing security-specific content. No evidence of security incident remediation or vulnerability disclosure.
Diff
diff --git a/prescriptive-guidance/latest/large-migration-foundation-playbook/workstreams.md b/prescriptive-guidance/latest/large-migration-foundation-playbook/workstreams.md index 58113e1dc..cfd6ff6da 100644 --- a//prescriptive-guidance/latest/large-migration-foundation-playbook/workstreams.md +++ b//prescriptive-guidance/latest/large-migration-foundation-playbook/workstreams.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Foundation playbook for AWS large migrations](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Foundation playbook for AWS large migrations](introduction.html) @@ -47,2 +47,2 @@ The following are the primary functions of each core workstream in the phases of -**Phase 3: Migrate** | **Stage 1: Initialize** | Establish workstreams and review landing zone design. Prepare for change. Formalize migration principles, teams, and RACI matrix. Complete training. | Develop project management processes and communication and meeting plans. | Develop metadata, wave planning, and application prioritization runbooks. | Develop migration runbooks. -**Stage 2: Impement** | — | Facilitate and communicate the status of waves and the overall migration project. | Collect metadata for the migration, prioritize applications, and plan waves. | Migrate and cutover waves, and iterate the runbooks to increase velocity. +**Phase 3: Migrate**| Stage 1: Initialize| Establish workstreams and review landing zone design. Prepare for change.Formalize migration principles, teams, and RACI matrix. Complete training.| Develop project management processes and communication and meeting plans.| Develop metadata, wave planning, and application prioritization runbooks.| Develop migration runbooks. +Stage 2: Implement| —| Facilitate and communicate the status of waves and the overall migration project.| Collect metadata for the migration, prioritize applications, and plan waves.| Migrate and cutover waves, and iterate the runbooks to increase velocity. @@ -50 +50 @@ The following are the primary functions of each core workstream in the phases of -The following sections describe each of the core workstreams in more detail, including common tasks for each workstream, the expected outcome of each workstream, and the skills required in each workstream. It is not required that each individual in the workstream have every skill. A workstream consists of one more cross-functional teams, so each person contributes different skills. But as a team, they should have all the skills listed. +The following sections describe each of the core workstreams in more detail, including common tasks for each workstream, the expected outcome of each workstream, and the skills required in each workstream.**** It is not required that each individual in the workstream have every skill. A workstream consists of one more cross-functional teams, so each person contributes different skills. But as a team, they should have all the skills listed. @@ -66 +66 @@ Common tasks | -Expected outcome | +**Expected outcome**| @@ -73 +73 @@ Expected outcome | -Required skills | +**Required skills**| @@ -102 +102 @@ Common tasks | -Expected outcome | +**Expected outcome**| @@ -110 +110 @@ Expected outcome | -Required skills | +**Required skills**| @@ -134 +134 @@ Common tasks | -Expected outcome | +**Expected outcome**| @@ -139 +139 @@ Expected outcome | -Required skills | +**Required skills**| @@ -176 +176 @@ Common tasks | - * Use AWS migration services to transfer data, such as AWS Transform MGN (AWS MGN), AWS Database Migration Service (AWS DMS), and AWS DataSync + * Use AWS migration services to transfer data, such as AWS Application Migration Service (AWS MGN), AWS Database Migration Service (AWS DMS), and AWS DataSync @@ -187 +187 @@ Common tasks | -Expected outcome | +**Expected outcome**| @@ -192 +192 @@ Expected outcome | -Required skills | +**Required skills**| @@ -196 +196 @@ Required skills | - * Experience with AWS migration services, including MGN, AWS DMS, DataSync, and AWS Snow Family + * Experience with AWS migration services, including Application Migration Service, AWS DMS, DataSync, and AWS Snow Family @@ -228 +228 @@ Security and compliance | Supporting | — | Migration Portfolio -Cloud operation | Supporting | Migration Application testing Foundation | — +Cloud operations| Supporting| MigrationApplication testingFoundation| — @@ -245 +245 @@ Common tasks | -Expected outcome | +**Expected outcome**| @@ -250 +250 @@ Expected outcome | -Required skills | +**Required skills**| @@ -255 +255 @@ Required skills | - * Experience with AWS migration tools, including MGN, AWS DMS, DataSync, and AWS Snow Family + * Experience with AWS migration tools, including Application Migration Service, AWS DMS, DataSync, and AWS Snow Family @@ -274 +274 @@ Common tasks | -Expected outcome | +**Expected outcome**| @@ -280 +280 @@ Expected outcome | -Required skills | +**Required skills**| @@ -283 +283 @@ Required skills | - * Experience with common AWS operations services, such as Amazon CloudWatch, AWS Config, AWS CloudTrail, AWS Backup, Support + * Experience with common AWS operations services, such as Amazon CloudWatch, AWS Config, AWS CloudTrail, AWS Backup, AWS Support @@ -291 +291 @@ Required skills | -The application testing workstream supports application testing before and during the cutover. This workstream is more common in projects where system integrators manage the data centers because the application owners don’t have sufficient knowledge to perform the application tests. In most cases, the application owner performs these activities, and a dedicated application testing workstream is not required. +The application testing workstream supports application testing before and during the cutover. This workstream is more common in projects where system integrators manage the data centers because the application owners don't have sufficient knowledge to perform the application tests. In most cases, the application owner performs these activities, and a dedicated application testing workstream is not required. @@ -302 +302 @@ Common tasks | -Expected outcome | +**Expected outcome**| @@ -308 +308 @@ Expected outcome | -Required skills | +**Required skills**| @@ -333 +333 @@ Common tasks | -Expected outcome | +**Expected outcome**| @@ -338 +338 @@ Expected outcome | -Required skills | +**Required skills**| @@ -343 +343 @@ Required skills | - * Experience with AWS migration tools, including MGN, AWS DMS, DataSync, and AWS Snow Family + * Experience with AWS migration tools, including Application Migration Service, AWS DMS, DataSync, and AWS Snow Family