AWS prescriptive-guidance documentation change
Summary
Added new documentation page about iterating migration strategies, including PDF reference, navigation elements, and content about validating migration decision trees.
Security assessment
Content discusses migration strategy planning without any security context. No security controls, vulnerabilities, or features are mentioned. Focus is on operational processes.
Diff
diff --git a/prescriptive-guidance/latest/application-portfolio-assessment-guide/iterating-7-rs-migration-strategy-selection.md b/prescriptive-guidance/latest/application-portfolio-assessment-guide/iterating-7-rs-migration-strategy-selection.md index 8b1378917..c7c27ac76 100644 --- a//prescriptive-guidance/latest/application-portfolio-assessment-guide/iterating-7-rs-migration-strategy-selection.md +++ b//prescriptive-guidance/latest/application-portfolio-assessment-guide/iterating-7-rs-migration-strategy-selection.md @@ -0,0 +1 @@ +[View a markdown version of this page](iterating-7-rs-migration-strategy-selection.md) @@ -1,0 +3,31 @@ +[](/pdfs/prescriptive-guidance/latest/application-portfolio-assessment-guide/application-portfolio-assessment-guide.pdf#iterating-7-rs-migration-strategy-selection "Open PDF") + +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Application portfolio assessment guide for AWS Cloud migration](introduction.html) + +# Iterating the 6 Rs migration strategy selection + +At this stage, we recommend that you iterate and evolve the 6 Rs decision tree. The [Determining the R type for migration](./prioritization-and-migration-strategy.html#migration-r-type) section introduced a default decision tree. We recommend revising the tree, considering the learnings throughout migration of the initial pilot applications, and ensuring that it still aligns to business drivers, prioritization criteria, and your unique circumstances. Validate the decision tree with sample applications, and verify that it still produces the expected strategy. Otherwise, update the logic accordingly. The resulting tree will be key in establishing baselines for the portfolio of applications and in allocating migration strategies for each application component. + +Make sure that migration strategies are allocated to each application component and its associated infrastructure. This information is a key factor when estimating effort, capacity, and skills needed, and when creating migration wave plans. + + **Javascript is disabled or is unavailable in your browser.** + +To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. + +[Document Conventions](/general/latest/gr/docconventions.html) + +Iterating the prioritization criteria + +Wave planning + +Did this page help you? - Yes + +Thanks for letting us know we're doing a good job! + +If you've got a moment, please tell us what we did right so we can do more of it. + +Did this page help you? - No + +Thanks for letting us know this page needs work. We're sorry we let you down. + +If you've got a moment, please tell us how we can make the documentation better.