AWS prescriptive-guidance documentation change
Summary
Updated prioritization criteria table with new scores for environments, added 'Number of dependencies' and 'Operations team cloud maturity' criteria, replaced decision tree diagram, removed attachments section
Security assessment
Changes involve routine updates to prioritization metrics and migration strategy guidance without any security context, vulnerability mentions, or security controls documentation
Diff
diff --git a/prescriptive-guidance/latest/application-portfolio-assessment-guide/prioritization-and-migration-strategy.md b/prescriptive-guidance/latest/application-portfolio-assessment-guide/prioritization-and-migration-strategy.md index 21c6e0492..17f80aa1f 100644 --- a//prescriptive-guidance/latest/application-portfolio-assessment-guide/prioritization-and-migration-strategy.md +++ b//prescriptive-guidance/latest/application-portfolio-assessment-guide/prioritization-and-migration-strategy.md @@ -7 +7 @@ -Prioritizing applicationsDetermining the R type for migrationAttachments +Prioritizing applicationsDetermining the R type for migration @@ -19 +19 @@ The initial criteria should prioritize applications with a small number of depen -_Deciding what initial criteria to use_ +### Deciding what initial criteria to use @@ -21 +21 @@ _Deciding what initial criteria to use_ -Select 2–10 data points to use for prioritizing your first workloads. These data points come from your initial application and infrastructure inventory (refer to the [data collection](./initiating-data-collection.html) section). +Select 2–10 data points to use for prioritizing your first workloads. These data points come from your initial data collection (refer to the [data collection](./initiating-data-collection.html) section). @@ -27 +27 @@ Based on the strategy to prioritize low-risk, simple applications for the first -**Attribute (data point)** | **Possible values** | **Score (0-99)** | **Importance or relevance multiplying factor** +Attribute (data point) | Possible values | Score (0-99) | Importance or relevance multiplying factor @@ -29,2 +29,2 @@ Based on the strategy to prioritize low-risk, simple applications for the first -Environment | Test | 60 | High (1x) -Development | 40 +Environment | Test | 80 | High (1x) +Development | 50 @@ -41,0 +42,3 @@ Number of compute instances | 1-3 | 60 | Medium-high (0.8x) +Number of dependencies | 0-3 | 70 | High (1x) +4-10 | 30 +11 or more | 10 @@ -44,0 +48,3 @@ Refactor, or re-architect | 10 +Operations team cloud maturity or readiness | High | 80 | High (1x) +Medium | 50 +Low | 10 @@ -62 +68 @@ However, starting with a complete rehost of all applications delays the greater -_How to determine a migration strategy for your applications?_ +### How to determine a migration strategy for your applications? @@ -66,3 +72 @@ At this stage of assessment, the focus is to incorporate an initial model for gu - - -A customizable [draw.io](https://github.com/jgraph/drawio-desktop/releases) version of this diagram is available in the _Attachments_ section. + @@ -72,7 +76 @@ The first step to an initial model is to update the business drivers at the top -The independent component assignment will lead you to define a migration strategy for the associated infrastructure. The infrastructure strategy might be the same strategy as the application component that it supports, or it might be different. For example, an application component that will be replatformed into a new virtual machine with a newer operating system will follow the replatform strategy while the current virtual machine that hosts it will be retired. The migration strategy for infrastructure is calculated based on the strategy chosen for the application components. - -Before using the decision tree to establish migration strategies, test the logic with a few applications and see if you generally agree with the outcome. The 6 Rs decision tree is a guide that does not replace the analysis required to determine its correctness. The tree logic might not apply to particular cases. Treat those cases as exceptions and proceed to override the decision driven by the tree by documenting the rationale for the override rather than changing the tree logic. This prevents multiple decision tree versions, which could become difficult to manage. General guidance is that the tree should be valid for at least 70-80 percent of the workloads. For the rest, there will be exceptions. Any adjustments to the tree logic, at this stage of assessment, should be focused on establishing an initial model. Further iterations and refinement will occur in later stages, such as [portfolio analysis and migration planning](./portfolio-analysis-migration-planning.html). - -## Attachments - -[attachment.zip](samples/attachment.zip) +Before using the decision tree to establish migration strategies, test the logic with a few applications and confirm that you generally agree with the outcome. The decision tree is a guide that does not replace the analysis required to determine its correctness. The tree logic might not apply to particular cases. Treat those cases as exceptions, and proceed to override the decision driven by the tree by documenting the rationale for the override rather than changing the tree logic. This prevents multiple decision tree versions, which could become difficult to manage. General guidance is that the tree should be valid for at least 70–80 percent of the workloads. For the rest, there will be exceptions. At this stage of the assessment, any adjustments to the tree logic should be focused on establishing an initial model to enable planning. Further iterations and refinement occur in later stages, such as [portfolio analysis and migration planning](./portfolio-analysis-migration-planning.html).