AWS prescriptive-guidance documentation change
Summary
Updated navigation links, formatted section headers in bold, fixed apostrophes, adjusted link formatting for AWS App2Container, added cautionary advice about refactoring complexity, and expanded a section title.
Security assessment
Changes are primarily formatting improvements (bolding headers, apostrophe corrections) and content clarifications. The 'Security and compliance' bullet was only formatted, not substantively changed. Added refactoring advice discusses complexity/cost, not security vulnerabilities. No evidence of addressing exploits, vulnerabilities, or security incidents.
Diff
diff --git a/prescriptive-guidance/latest/large-migration-guide/migration-strategies.md b/prescriptive-guidance/latest/large-migration-guide/migration-strategies.md index 94819b3a1..611fb63ba 100644 --- a//prescriptive-guidance/latest/large-migration-guide/migration-strategies.md +++ b//prescriptive-guidance/latest/large-migration-guide/migration-strategies.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Guide for AWS large migrations](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Guide for AWS large migrations](introduction.html) @@ -59 +59 @@ The following are common use cases for the retain strategy: - * Security and compliance – You might want to retain applications in order to remain in compliance with data residency requirements. + * **Security and compliance** – You might want to retain applications in order to remain in compliance with data residency requirements. @@ -61 +61 @@ The following are common use cases for the retain strategy: - * High risk – You might decide to retain an application because it requires a detailed assessment and plan prior to migration. + * **High risk** – You might decide to retain an application because it requires a detailed assessment and plan prior to migration. @@ -63 +63 @@ The following are common use cases for the retain strategy: - * Dependencies – You might decide to retain an application if you need to migrate one or more other applications first. + * **Dependencies** – You might decide to retain an application if you need to migrate one or more other applications first. @@ -65 +65 @@ The following are common use cases for the retain strategy: - * Applications that are recently upgraded – You might want to postpone migrating the application until the next technical refresh because you recently invested in upgrading your current system. + * **Applications that are recently upgraded** –You might want to postpone migrating the application until the next technical refresh because you recently invested in upgrading your current system. @@ -67 +67 @@ The following are common use cases for the retain strategy: - * No business value to migrate – There is no business value for migrating some applications to the cloud, such as those with only a few internal users. + * **No business value to migrate** – There is no business value for migrating some applications to the cloud, such as those with only a few internal users. @@ -69 +69 @@ The following are common use cases for the retain strategy: - * Plans to migrate to software as a service (SaaS) – You might choose retain an application until the SaaS version is released by the vendor. This is a common strategy for vendor-based applications. + * **Plans to migrate to software as a service (SaaS)** – You might choose retain an application until the SaaS version is released by the vendor. This is a common strategy for vendor-based applications. @@ -71 +71 @@ The following are common use cases for the retain strategy: - * Unresolved physical dependencies – You might choose to retain an application that is dependent on specialized hardware that does not have a cloud equivalent, such as machines in a manufacturing plant. + * **Unresolved physical dependencies** – You might choose to retain an application that is dependent on specialized hardware that does not have a cloud equivalent, such as machines in a manufacturing plant. @@ -73 +73 @@ The following are common use cases for the retain strategy: - * Mainframe or mid-range applications and non-x86 Unix applications – These applications require careful assessment and planning before migrating them to the cloud. Examples of mid-range applications include IBM AS/400 and Oracle Solaris. + * **Mainframe or mid-range applications and non-x86 Unix applications** – These applications require careful assessment and planning before migrating them to the cloud. Examples of mid-range applications include IBM AS/400 and Oracle Solaris. @@ -75 +75 @@ The following are common use cases for the retain strategy: - * Performance – You might want to retain applications based on their performance. For example, you might want to keep zombie or idle applications in your source environment. + * **Performance** – You might want to retain applications based on their performance. For example, you might want to keep zombie or idle applications in your source environment. @@ -107 +107 @@ Using this strategy, you can transfer a large number of servers, comprising one -The relocate strategy doesn’t require that you purchase new hardware, rewrite applications, or modify your existing operation. During relocation, the application continues to serve users, which minimizes disruption and downtime. Relocate is the quickest way to migrate and operate your workload in the cloud because it does not impact the overall architecture of your application. +The relocate strategy doesn't require that you purchase new hardware, rewrite applications, or modify your existing operation. During relocation, the application continues to serve users, which minimizes disruption and downtime. Relocate is the quickest way to migrate and operate your workload in the cloud because it does not impact the overall architecture of your application. @@ -117 +117 @@ The following are common use cases for the repurchase migration strategy: - * Moving from a traditional license to SaaS – This removes the burden of managing and maintaining the infrastructure and helps reduce licensing issues. + * **Moving from a traditional license to SaaS** – This removes the burden of managing and maintaining the infrastructure and helps reduce licensing issues. @@ -119 +119 @@ The following are common use cases for the repurchase migration strategy: - * Version upgrades or third-party equivalents – By replacing your existing on-premises application with the vendor’s latest version or third-party equivalent in the cloud, you can leverage new features, integrate with cloud services, and scale the application more easily. + * **Version upgrades or third-party equivalents** – By replacing your existing on-premises application with the vendor's latest version or third-party equivalent in the cloud, you can leverage new features, integrate with cloud services, and scale the application more easily. @@ -121 +121 @@ The following are common use cases for the repurchase migration strategy: - * Replacing a custom application – You can avoid recoding and re-architecting a custom application by repurchasing a vendor-based SaaS or cloud-based application. + * **Replacing a custom application** – You can avoid recoding and re-architecting a custom application by repurchasing a vendor-based SaaS or cloud-based application. @@ -159 +159 @@ The following are common use cases for the replatform migration strategy: - * You can improve performance by migrating virtual machines into containers, without making any code changes. You can modernize your .NET and Java applications into containerized applications by using the [AWS App2Container migration tool](https://aws.amazon.com/app2container/). + * You can improve performance by migrating virtual machines into containers, without making any code changes. You can modernize your .NET and Java applications into containerized applications by using the [AWS App2Container](https://aws.amazon.com/app2container/) migration tool. @@ -190,0 +191,2 @@ For a list of migration patterns for the refactor migration strategy, see [Re-ar +Refactoring is the most complex and costly of the migration strategies because you modernize the application during the migration, which involves redesigning the core components so that it runs in the target cloud environment. For a large migration, refactor only when the other migration strategies are not an acceptable option. In large migrations, whenever possible, we recommend that you modernize applications after the migration is complete. + @@ -197 +199 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Stage 2: Implementing +Stage 2: Implementing a large migration