AWS prescriptive-guidance documentation change
Summary
Updated navigation links, simplified section headers, corrected apostrophe usage, updated image reference path, and made minor text formatting changes. Changed section title from 'Best practices' to 'Best practices for large migrations'.
Security assessment
Changes are primarily formatting, navigation, and typographical corrections. No explicit security vulnerabilities, mitigations, or new security features are mentioned. The existing security-related content (e.g., references to security services like VPNs and certificate authorities) remains unchanged from previous version.
Diff
diff --git a/prescriptive-guidance/latest/strategy-large-scale-migrations/scope-strategy-time.md b/prescriptive-guidance/latest/strategy-large-scale-migrations/scope-strategy-time.md index 7e766f103..a44d258db 100644 --- a//prescriptive-guidance/latest/strategy-large-scale-migrations/scope-strategy-time.md +++ b//prescriptive-guidance/latest/strategy-large-scale-migrations/scope-strategy-time.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) @@ -7 +7 @@ -Scope – What are you migrating?Strategy – Why do you want to migrate?Timeline – When do you need to complete the migration? +ScopeStrategyTimeline @@ -13 +13 @@ Three key elements make up the building blocks of all programs and their relevan - + @@ -19 +19 @@ To set the stage for your migration journey, these elements must be aligned and -It’s common for the total scope of the program to be undefined, even when you’re half way through the migration. This is because various factors might not be unpacked until the later stages. For example, halfway through your migration, you might uncover a pocket of shadow IT that was not recorded in your configuration management database (CMDB). Alternatively, the planning might have focused on a server view without considering the supporting network and security services that are required for those applications to run (such as VPN connections to AWS Partners, and certificate authorities to sign certificates). We recommend investing some time in defining the scope, working backwards from your target business outcome. You might end up using discovery tooling to uncover assets, a best practice that will be discussed later in this guide. +It's common for the total scope of the program to be undefined, even when you're half way through the migration. This is because various factors might not be unpacked until the later stages. For example, halfway through your migration, you might uncover a pocket of shadow IT that was not recorded in your configuration management database (CMDB). Alternatively, the planning might have focused on a server view without considering the supporting network and security services that are required for those applications to run (such as VPN connections to AWS Partners, and certificate authorities to sign certificates). We recommend investing some time in defining the scope, working backwards from your target business outcome. You might end up using discovery tooling to uncover assets, a best practice that will be discussed later in this guide. @@ -31 +31 @@ You might be planning to migrate to AWS for one or more of the following reasons - * The board has decided that you need to move to the cloud as a strategic direction, allowing for a fast pace of change in the business’s future. + * The board has decided that you need to move to the cloud as a strategic direction, allowing for a fast pace of change in the business's future. @@ -36 +36 @@ You might be planning to migrate to AWS for one or more of the following reasons -Whatever the reason, all these reasons and more will be on the minds of your business and IT organizations. It’s key to understand what your drivers are, to communicate them, and to prioritize them. Each additional driver potentially adds time, costs, scope, and risks to your already-large migration. Being fully aware of the impact that the strategy has on the timeline and scope is key. +Whatever the reason, all these reasons and more will be on the minds of your business and IT organizations. It's key to understand what your drivers are, to communicate them, and to prioritize them. Each additional driver potentially adds time, costs, scope, and risks to your already-large migration. Being fully aware of the impact that the strategy has on the timeline and scope is key. @@ -38 +38 @@ Whatever the reason, all these reasons and more will be on the minds of your bus -After you define your migration strategy, one of the main keys to success is alignment of requirements across the various stakeholders and teams. Performing the migration requires different teams across the organization, including Infrastructure, Security, Application, and Operations. These teams will have individual priorities and other projects that might have already commenced. If these teams are working toward different timelines and priorities, it’s more challenging to agree on and implement a migration plan. The migration team and key stakeholders must ensure that all involved teams work toward a single goal and align their priorities with a single timeline of migrations. +After you define your migration strategy, one of the main keys to success is alignment of requirements across the various stakeholders and teams. Performing the migration requires different teams across the organization, including Infrastructure, Security, Application, and Operations. These teams will have individual priorities and other projects that might have already commenced. If these teams are working toward different timelines and priorities, it's more challenging to agree on and implement a migration plan. The migration team and key stakeholders must ensure that all involved teams work toward a single goal and align their priorities with a single timeline of migrations. @@ -44 +44 @@ Frequently, businesses want to modernize applications, which can result in infra -To achieve this, set the right expectations early in the project. The key message should be “Migrate first, then modernize.” This approach not only enables organizations to reduce technical debt and operate at scale eventually, it opens avenues for different modernization approaches by using the scalability and agility that the AWS Cloud can provide. Thinking long term will help infrastructure teams to streamline infrastructure deployment and management. As a result the business can have faster feature release cycles. +To achieve this, set the right expectations early in the project. The key message should be "Migrate first, then modernize." This approach not only enables organizations to reduce technical debt and operate at scale eventually, it opens avenues for different modernization approaches by using the scalability and agility that the AWS Cloud can provide. Thinking long term will help infrastructure teams to streamline infrastructure deployment and management. As a result the business can have faster feature release cycles. @@ -50 +50 @@ Depending on your business case, you must ensure you are not taking on more than -In these time-sensitive types of migrations, we recommend the “Migrate first, then modernize” approach. This helps set expectations and encourages the teams to ensure that their individual project plans and budgets are aligned with the overall migration goal. It’s important to find out any disagreements as early as possible in the project, fail fast and address the disagreements at the Steering Committee level, and engage the right stakeholders to ensure that alignment is in place. +In these time-sensitive types of migrations, we recommend the "Migrate first, then modernize" approach. This helps set expectations and encourages the teams to ensure that their individual project plans and budgets are aligned with the overall migration goal. It's important to find out any disagreements as early as possible in the project, fail fast and address the disagreements at the Steering Committee level, and engage the right stakeholders to ensure that alignment is in place. @@ -52 +52 @@ In these time-sensitive types of migrations, we recommend the “Migrate first, -Conversely, if your main goal of migration is to gain the benefits of application modernization, this must be called out early in the program. Many programs start with an initial goal based on a fixed deadline, and they don’t plan for the requirements from stakeholders who want to resolve outstanding issues and problems. In some cases, these issues have been present for years in the source systems, but now they become artificial blockers to migration. +Conversely, if your main goal of migration is to gain the benefits of application modernization, this must be called out early in the program. Many programs start with an initial goal based on a fixed deadline, and they don't plan for the requirements from stakeholders who want to resolve outstanding issues and problems. In some cases, these issues have been present for years in the source systems, but now they become artificial blockers to migration. @@ -64 +64 @@ Introduction -Best practices +Best practices for large migrations