AWS prescriptive-guidance documentation change
Summary
Updated documentation links, corrected apostrophe usage, improved table formatting, added emphasis to key terms, updated service names (e.g., CloudFormation to AWS CloudFormation), and condensed application mapping examples into compact tables.
Security assessment
Changes are primarily editorial improvements and formatting adjustments. No security vulnerabilities, incidents, or weaknesses are addressed. Minor security mentions (e.g., 'Improve security and compliance') exist in example tables but are unchanged in substance and not new additions.
Diff
diff --git a/prescriptive-guidance/latest/large-migration-portfolio-playbook/deep-dive.md b/prescriptive-guidance/latest/large-migration-portfolio-playbook/deep-dive.md index 07bc41994..cab73e4c7 100644 --- a//prescriptive-guidance/latest/large-migration-portfolio-playbook/deep-dive.md +++ b//prescriptive-guidance/latest/large-migration-portfolio-playbook/deep-dive.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Portfolio playbook for AWS large migrations](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Portfolio playbook for AWS large migrations](introduction.html) @@ -30 +30 @@ This task consists of the following steps: -The workshop process is one of the most efficient approaches to an application deep dive. Using this process, you collaborate with the stakeholders, application owners, and the portfolio team to assess and analyze the application. The goal is to clearly understand the current state of the application, including its architecture, business purpose, dependencies, and environment. You then use this detailed information about the size and complexity of the application to design the application’s target state. +The workshop process is one of the most efficient approaches to an application deep dive. Using this process, you collaborate with the stakeholders, application owners, and the portfolio team to assess and analyze the application. The goal is to clearly understand the current state of the application, including its architecture, business purpose, dependencies, and environment. You then use this detailed information about the size and complexity of the application to design the application's target state. @@ -36 +36 @@ Each workshop typically lasts 1–8 hours, although you might find that addition -Before conducting an application workshop, you should set an agenda and define the expected outcomes of the workshop, or information that you need to collect in the workshop. This allows the workshop participants to prepare for the workshop, helps keep the meeting on target, and ensures that by the end of the workshop, you have all of the information necessary to prioritize, wave plan, and migrate the application. +Before conducting an application workshop, you should set an agenda and define the _expected outcomes_ of the workshop, or information that you need to collect in the workshop. This allows the workshop participants to prepare for the workshop, helps keep the meeting on target, and ensures that by the end of the workshop, you have all of the information necessary to prioritize, wave plan, and migrate the application. @@ -55 +55 @@ The following are examples of expected outcomes for the application workshop. -Priority | Expected outcome of application workshop +**Priority**| **Expected outcome of application workshop** @@ -57 +57 @@ Priority | Expected outcome of application workshop -1 | Clear understanding of the application’s current architecture, including associated servers, dependencies, the environment, and the application tier. +1| Clear understanding of the application's current architecture, including associated servers, dependencies, the environment, and the application tier. @@ -90 +90 @@ The following are examples of rules for the application workshop. -Priority | Workshop rule +**Priority**| **Workshop rule** @@ -147 +147 @@ The _Runbook template for application prioritization_ includes a standard step-b -_Application mapping_ is the process of assigning each application to a migration pattern, which you identified and validated in [Step 4: Validate the migration patterns](./discovery.html#discovery-4). In this step, you define the rules that you will use to evaluate the application. You then define the process that you will use to evaluate each application. Mapping each application to the migration pattern’s use case helps you identify the migration tool, any skills necessary to complete the migration, and the complexity of the migration pattern. + _Application mapping_ is the process of assigning each application to a migration pattern, which you identified and validated in [Step 4: Validate the migration patterns](./discovery.html#discovery-4). In this step, you define the rules that you will use to evaluate the application. You then define the process that you will use to evaluate each application. Mapping each application to the migration pattern's use case helps you identify the migration tool, any skills necessary to complete the migration, and the complexity of the migration pattern. @@ -149 +149 @@ _Application mapping_ is the process of assigning each application to a migratio -You do not always migrate an application to a single pattern. For more information about when you might need multiple patterns for the same application, see Define the application mapping process later in this section. +You do not always migrate an application to a single pattern. For more information about when you might need multiple patterns for the same application, see _Define the application mapping process_ , later in this section. @@ -155 +155 @@ The application mapping rules help you evaluate the application and identify the -In the [portfolio playbook templates](samples/portfolio-playbook-templates.zip), the _Runbook template for application prioritization_ includes a section for documenting your application mapping rules. Define your process as follows: +The attached _Runbook template for application prioritization_ includes a section for documenting your application mapping rules. Define your process as follows: @@ -181 +181 @@ Priority | Mapping rule - * If the OS is not supported, choose _Pattern 3: Replatform to Amazon EC2 using CloudFormation_. + * If the OS is not supported, choose _Pattern 3: Replatform to Amazon EC2 using AWS CloudFormation_. @@ -185 +185 @@ Priority | Mapping rule -5 | Identify whether the application’s on-premises database(s) can be migrated to a homogeneous service in the cloud, such as migrating an on-premises Oracle database to Amazon RDS for Oracle or migrating an on-premises MySQL database to Amazon Aurora MySQL-Compatible Edition database. If these criteria are met, use _Pattern 2: Replatform to Amazon RDS using AWS DMS and AWS SCT_. +5| Identify whether the application's on-premises database(s) can be migrated to a homogeneous service in the cloud, such as migrating an on-premises Oracle database to Amazon RDS for Oracle or migrating an on-premises MySQL database to Amazon Aurora MySQL-Compatible Edition database. If these criteria are met, use _Pattern 2: Replatform to Amazon RDS using AWS DMS and AWS SCT_. @@ -188 +188 @@ Priority | Mapping rule -8 | Identify whether the application’s servers are mainframe or midrange servers, such as IBM AS/400 or Apache Spark, and confirm that the applications are compatible with emulators. If these criteria are met, use _Pattern 6: Replatform mainframe or midrange servers to Amazon EC2 using an emulator_. +8| Identify whether the application's servers are mainframe or midrange servers, such as IBM AS/400 or Apache Spark, and confirm that the applications are compatible with emulators. If these criteria are met, use _Pattern 6: Replatform mainframe or midrange servers to Amazon EC2 using an emulator_. @@ -201 +201 @@ You should also consider whether the application is an n-tier application, which -You then evaluate the application against your application mapping rules, which you defined in your application prioritization runbook. For more information, see Application mapping rules earlier in this section. +You then evaluate the application against your application mapping rules, which you defined in your application prioritization runbook. For more information, see _Application mapping rules_ earlier in this section. @@ -207 +207 @@ When you have mapped the application to one or more migration patterns and confi -In the [portfolio playbook templates](samples/portfolio-playbook-templates.zip), the _Runbook template for application prioritization_ includes a standard step-by-step process for application mapping. Define your process as follows: +The attached _Runbook template for application prioritization_ includes a standard step-by-step process for application mapping. Define your process as follows: @@ -228,65 +228,9 @@ Application name | Pattern ID | Pattern name | Business and technical drivers ad -Corporate website | 1 | Rehost to Amazon EC2 using MGN or Cloud Migration Factory | - - * Data center exit - * Reduce operational costs - - -HR system | 8 | Retire the application | - - * Reduce operational costs - - -Time and attendance application | 9 | Retain on premises | - - * Reduce operational costs - * Reduce risk and impact - - -PO system | 3 | Replatform to Amazon EC2 using CloudFormation | - - * Technology integration - * Storage and compute limitation - * Hardware and software end-of-life support - * Improve security and compliance - - -CRM system | 10 | Repurchase and upgrade to SaaS | - - * Reduce operational costs - * Technology integration - * Hardware and software end-of-life support - * Accelerate development, innovation, and growth - - -Fixed asset system | 7 | Replatform from Windows to Linux on Amazon EC2 | - - * Reduce operational costs - - -ERP file storage | 4 | Replatform to Amazon EFS using AWS DataSync or AWS Transfer Family | - - * Storage and compute limitation - - -Ledger system | 6 | Rehost mainframe or midrange servers to Amazon EC2 using an emulator | - - * Data center exit - * Technology integration - * Improve security and compliance - * Hardware and software end-of-life support - * Storage and compute limitation - * Modernizing application architecture - - -General ledger | 11 | Re-architect the application | - - * Reduce operational costs - * Technology integration - * Improve security and compliance - * Hardware and software end-of-life support - * Storage and compute limitation - * Modernizing application architecture - * Scalability and resiliency - * Accelerate development, innovation, and growth - - +Corporate website| 1| Rehost to Amazon EC2 using MGN or Cloud Migration Factory| Data center exitReduce operational costs +HR system| 8| Retire the application| Reduce operational costs +Time and attendance application| 9| Retain on premises| Reduce operational costsReduce risk and impact +PO system| 3| Replatform to Amazon EC2 using AWS CloudFormation| Technology integrationStorage and compute limitationHardware and software end-of-life supportImprove security and compliance +CRM system| 10| Repurchase and upgrade to SaaS| Reduce operational costsTechnology integrationHardware and software end-of-life supportAccelerate development, innovation, and growth +Fixed asset system| 7| Replatform from Windows to Linux on Amazon EC2| Reduce operational costs +ERP file storage | 4| Replatform to Amazon EFS using AWS DataSync or AWS Transfer Family| Storage and compute limitation +Ledger system| 6| Rehost mainframe or midrange servers to Amazon EC2 using an emulator| Data center exitTechnology integrationImprove security and complianceHardware and software end-of-supportStorage and compute limitationModernizing application architecture +General ledger| 11| Re-architect the application| Reduce operational costsTechnology integrationImprove security and complianceHardware and software end-of-supportStorage and compute limitationModernizing application architectureScalability and resiliencyAccelerate development, innovation, and growth @@ -309 +253 @@ General ledger | 11 | Re-architect the application | -In this step, you define the attributes and the process that you use to document the target state, or _to-be state_ , for the application. The target state is how the application operates in the target cloud environment after the migration. The target environment varies based on your target platform or service and business requirements. The target environment could be the AWS Cloud or AWS Managed Services (AMS). +In this step, you define the attributes and the process that you use to document the target state, or _to-be_ _state_ , for the application. The _target state_ is how the application operates in the target cloud environment after the migration. The target environment varies based on your target platform or service and business requirements. The target environment could be the AWS Cloud or AWS Managed Services (AMS). @@ -313 +257 @@ Defining the target state helps project managers, migration consultants, archite -For some applications, this step is optional. You can skip this step if the application you are migrating is standalone or low-complexity. Migration strategies that don’t modify the application, such as rehost, might not require this step. However, for more complex migration strategies, such as replatform and re-architect, you should define the target state before starting the migration. +For some applications, this step is optional. You can skip this step if the application you are migrating is standalone or low-complexity. Migration strategies that don't modify the application, such as rehost, might not require this step. However, for more complex migration strategies, such as replatform and re-architect, you should define the target state before starting the migration. @@ -315 +259 @@ For some applications, this step is optional. You can skip this step if the appl -The workshop provides you with an in-depth understanding of the current state of the application, so it’s a good idea to draft the target state after completing the workshop. In addition, mapping the application to its migration pattern provides additional insights and helps you identify whether defining the target state is necessary. For example, if you map the application to the pattern _Rehost to Amazon EC2 using MGN or Cloud Migration Factory_ , you’ve identified that the strategy is rehost, and you likely do not need to define the target state for this application. +The workshop provides you with an in-depth understanding of the current state of the application, so it's a good idea to draft the target state after completing the workshop. In addition, mapping the application to its migration pattern provides additional insights and helps you identify whether defining the target state is necessary. For example, if you map the application to the pattern _Rehost to Amazon EC2 using MGN or Cloud Migration Factory_ , you've identified that the strategy is rehost, and you likely do not need to define the target state for this application. @@ -339 +283 @@ When defining the target state and making decisions about the application, we re - * **Disaster recovery** – Identify the application’s current and future-state disaster recovery (DR) plan, including the recovery point objective (RPO) and recovery time objective (RTO). Decide whether to use the existing on-premises DR plan or to explore a new DR strategy in the cloud. For more information, see the sections [Disaster recovery options in the cloud](https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/disaster-recovery-options-in-the-cloud.html) and [Recovery objectives (RTO and RPO)](https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/business-continuity-plan-bcp.html#recovery-objectives-rto-and-rpo) in the _Disaster Recovery of Workloads on AWS: Recovery in the Cloud_ whitepaper. + * **Disaster recovery** – Identify the application's current and future-state disaster recovery (DR) plan, including the recovery point objective (RPO) and recovery time objective (RTO). Decide whether to use the existing on-premises DR plan or to explore a new DR strategy in the cloud. For more information, see the sections [Disaster recovery options in the cloud](https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/disaster-recovery-options-in-the-cloud.html) and [Recovery objectives (RTO and RPO)](https://docs.aws.amazon.com/whitepapers/latest/disaster-recovery-workloads-on-aws/business-continuity-plan-bcp.html#recovery-objectives-rto-and-rpo) in the _Disaster Recovery of Workloads on AWS: Recovery in the Cloud_ whitepaper. @@ -346 +290 @@ When defining the target state and making decisions about the application, we re -To define the application target state, we recommend you use the provided template, _Application target state worksheet_ (Excel format), which is available in the [portfolio playbook templates](samples/portfolio-playbook-templates.zip). The template includes standard attributes that you can use or modify. Define the process for documenting the application target state as follows: +To define the application target state, we recommend you use the provided template, _Application target state worksheet_(Excel format). The template includes standard attributes that you can use or modify. Define the process for documenting the application target state as follows: @@ -358 +302 @@ To define the application target state, we recommend you use the provided templa - 1. In the _When to complete this process_ section, establish criteria that allow the portfolio team to determine whether they need to define the application’s target state. + 1. In the _When to complete this process_ section, establish criteria that allow the portfolio team to determine whether they need to define the application's target state. @@ -371 +315 @@ To define the application target state, we recommend you use the provided templa -The following table shows an example of how you use the _Application target state_ worksheet to document the target state of the application. +The following table shows an example of how you use the _Application target state worksheet_ to document the target state of the application.