AWS prescriptive-guidance documentation change
Summary
Updated navigation links, formatting fixes (hyphen escaping and apostrophe correction), removed subsection headers, simplified bullet point formatting, and made minor wording adjustments
Security assessment
Changes are primarily formatting improvements, navigation updates, and grammatical corrections. No security vulnerabilities or security-specific content changes were identified. The mention of security team representation in the Cloud Enablement Engine was already present in previous versions.
Diff
diff --git a/prescriptive-guidance/latest/strategy-large-scale-migrations/people.md b/prescriptive-guidance/latest/strategy-large-scale-migrations/people.md index 543169283..825ac70c4 100644 --- a//prescriptive-guidance/latest/strategy-large-scale-migrations/people.md +++ b//prescriptive-guidance/latest/strategy-large-scale-migrations/people.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Strategy and best practices for AWS large migrations](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Strategy and best practices for AWS large migrations](introduction.html) @@ -13 +13 @@ This section focuses on the following key areas of the people perspective: - * Executive support – Identifying a single-threaded leader who’s empowered to make decisions + * Executive support \- Identifying a single-threaded leader who's empowered to make decisions @@ -15 +15 @@ This section focuses on the following key areas of the people perspective: - * Team collaboration and ownership – Collaborating among various teams + * Team collaboration and ownership \- Collaborating among various teams @@ -17 +17 @@ This section focuses on the following key areas of the people perspective: - * Training – Proactively training teams on the various tooling + * Training \- Proactively training teams on the various tooling @@ -24 +24 @@ This section focuses on the following key areas of the people perspective: -###### In this section: +In this section: @@ -26 +26 @@ This section focuses on the following key areas of the people perspective: - * [Identify a single-threaded leader](./people.html#leader) + * Identify a single-threaded leader @@ -28 +28 @@ This section focuses on the following key areas of the people perspective: - * [Align the senior leadership team](./people.html#align-leadership) + * Align the senior leadership team @@ -35 +35 @@ This section focuses on the following key areas of the people perspective: -When starting a large migration, it’s important to identify a single-threaded technical leader who is 100 percent dedicated to the project and accountable. That leader is empowered to make decisions, help avoid silos, and streamline work-streams by maintaining consistent priorities. +When starting a large migration, it's important to identify a single-threaded technical leader who is 100 percent dedicated to the project and accountable. That leader is empowered to make decisions, help avoid silos, and streamline work-streams by maintaining consistent priorities. @@ -37 +37 @@ When starting a large migration, it’s important to identify a single-threaded -A large migration global customer was able to scale from one server each week at the outset of the program to more than 80 servers each week at the start of the second month. The CIO‘s full support as a single-threaded leader was critical to the rapid scale up of servers being migrated. The CIO attended weekly migration cutover calls with the migration team to ensure real-time escalation and resolution of issues, which accelerated the migration velocity. +A large migration global customer was able to scale from one server each week at the outset of the program to more than 80 servers each week at the start of the second month. The CIO's full support as a single-threaded leader was critical to the rapid scale up of servers being migrated. The CIO attended weekly migration cutover calls with the migration team to ensure real-time escalation and resolution of issues, which accelerated the migration velocity. @@ -41 +41 @@ A large migration global customer was able to scale from one server each week at -It’s important to create alignment between the various teams regarding the success criteria of the migration. While migration planning and implementation can be accomplished by a small, dedicated team, challenges arise when defining the strategy and performing peripheral activities. These potential obstacles might require actions or escalations from different areas of the IT organization, including the following: +It's important to create alignment between the various teams regarding the success criteria of the migration. While migration planning and implementation can be accomplished by a small, dedicated team, challenges arise when defining the strategy and performing peripheral activities. These potential obstacles might require actions or escalations from different areas of the IT organization, including the following: @@ -62 +62 @@ Direct action from application owners, leadership, alignment, and a clear escala -###### In this section: +In this section: @@ -64 +64 @@ Direct action from application owners, leadership, alignment, and a clear escala - * [Create a cross-functional cloud-enablement team](./people.html#cross-function) + * Create a cross-functional team cloud-enablement team @@ -66 +66 @@ Direct action from application owners, leadership, alignment, and a clear escala - * [Define requirements for teams and individuals outside the core migration team in advance](./people.html#define-reqs) + * Define requirements for teams and individuals outside the core migration team in advance @@ -68 +68 @@ Direct action from application owners, leadership, alignment, and a clear escala - * [Validate that there are no licensing issues when migrating workloads](./people.html#licensing) + * Validate that there are no licensing issues when migrating workloads @@ -75,6 +75 @@ Direct action from application owners, leadership, alignment, and a clear escala -###### In this section: - - - - -A critical first step in a large migration project is to enable the organization to work in the cloud. To accomplish this, we recommend building a [Cloud Enablement Engine](https://d1.awsstatic.com/whitepapers/cloud-enablement-engine-practical-guide.pdf) (CEE). The CEE is an empowered and accountable team focused on organization’s operational readiness for migrations to AWS. The CEE should be a cross-functional team that includes representation from infrastructure, applications, operations, and security. The team is charged with the following responsibilities: +A critical first step in a large migration project is to enable the organization to work in the cloud. To accomplish this, we recommend building a [Cloud Enablement Engine](https://d1.awsstatic.com/whitepapers/cloud-enablement-engine-practical-guide.pdf) (CEE). The CEE is an empowered and accountable team focused on organization's operational readiness for migrations to AWS. The CEE should be a cross-functional team that includes representation from infrastructure, applications, operations, and security. The team is charged with the following responsibilities: @@ -91 +86 @@ A critical first step in a large migration project is to enable the organization -One healthcare customer didn’t start with a CEE. However, through initial pilot migrations, the gap was identified. Leading up to the final migration cutover date, with stringent deadlines in place, the team implemented a _migration war room_. In the migration war room, stakeholders from infrastructure, security, applications, and business could assist in resolving issues. +One healthcare customer didn't start with a CEE. However, through initial pilot migrations, the gap was identified. Leading up to the final migration cutover date, with stringent deadlines in place, the team implemented a _migration war room._ In the migration war room, stakeholders from infrastructure, security, applications, and business could assist in resolving issues. @@ -95 +90 @@ One healthcare customer didn’t start with a CEE. However, through initial pilo -Identify teams and individuals that are outside the core program, and define their involvement during the migration planning phases. To facilitate the momentum of the migration during the later stages, pay specific attention to the application teams’ involvement. Their knowledge of the application, ability to diagnose issues, and requirement to sign off on the cutover will be required. +Identify teams and individuals that are outside the core program, and define their involvement during the migration planning phases. To facilitate the momentum of the migration during the later stages, pay specific attention to the application teams' involvement. Their knowledge of the application, ability to diagnose issues, and requirement to sign off on the cutover will be required. @@ -99 +94 @@ While the migration will be led by a core team, the application teams will likel -We recommend considering the application team’s required involvement when selecting a migration strategy. For example, a rehost strategy requires less application-team involvement compared with a replatform or refactor strategy in which more of the application landscape is being changed. If application owner availability is limited, consider using rehost or replatform as opposed to the refactor, relocate, or repurchase strategies. +We recommend considering the application team's required involvement when selecting a migration strategy. For example, a rehost strategy requires less application-team involvement compared with a replatform or refactor strategy in which more of the application landscape is being changed. If application owner availability is limited, consider using rehost or replatform as opposed to the refactor, relocate, or repurchase strategies. @@ -109,10 +104 @@ We recommend collaborating with your sourcing or vendor management teams as soon -###### In this section: - - * [Train teams on new tooling and processes](./people.html#tools-training) - - - - -### Train teams on new tooling and processes - -After the migration strategy is defined, invest time in understanding what training might be required for the migration and for your target operating model. During the migration, you will likely use tooling, such as AWS Database Migration Service, that is new to your organization. Proactively training teams reduces the delays experienced during the migration phases. +After the migration strategy is defined, invest time in understanding what training might be required for the migration and for your target operating model. During the migration, you will likely use tooling, such as AWS Database Migration Service (AWS DMS), that is new to your organization. Proactively training teams reduces the delays experienced during the migration phases. @@ -128 +114 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Best practices +Best practices for large migrations @@ -130 +116 @@ Best practices -Technology +Technology perspective