AWS prescriptive-guidance documentation change
Summary
Updated grammar in stakeholder section, refined timeline in migration example (6-12 months to 12 months), narrowed migration strategy to rehost-only, updated service reference to AWS Application Migration Service, and added new content about defining architectural security principles including communication encryption requirements.
Security assessment
The change introduces new documentation about architectural security principles requiring encrypted communications for migrated applications. This adds explicit security guidance but doesn't address a specific vulnerability. No evidence of a security incident being fixed.
Diff
diff --git a/prescriptive-guidance/latest/application-portfolio-assessment-guide/business-drivers-technical-guiding-principles.md b/prescriptive-guidance/latest/application-portfolio-assessment-guide/business-drivers-technical-guiding-principles.md index c1dcdc180..4ea72467a 100644 --- a//prescriptive-guidance/latest/application-portfolio-assessment-guide/business-drivers-technical-guiding-principles.md +++ b//prescriptive-guidance/latest/application-portfolio-assessment-guide/business-drivers-technical-guiding-principles.md @@ -15 +15 @@ Whether your organization has already decided to move to the cloud or is close t -Identify the stakeholders that should be part of the discussion to document the drivers. Typically, CxOs, senior managers, and key technology leaders within the organization, and your own customers. Although your customers are not likely to be part of this discussion, we recommend that one or more persons in your organization are designated represent your customers' views and goals. +Identify the stakeholders that should be part of the discussion to document the drivers. Typically, CxOs, senior managers, and key technology leaders within the organization, and your own customers. Although your customers are not likely to be part of this discussion, we recommend that one or more persons in your organization are designated to represent your customers' views and goals. @@ -29 +29 @@ Guiding principles can be established as general technology-related and approach -For example, a company has a primary goal to reduce cost, and the desired outcome is to close an on-premises data center by a given date in 6–12 months. A resulting guiding principle is to lift and shift all applications to the cloud by using a rehost or relocate migration strategy whenever possible. In this case, the lift-and-shift approach accelerates near-term migration outcomes. After the applications have moved out of the on-premises data center, the company can focus on the main business drivers to optimize or modernize the migrated workloads. +For example, a company has a primary goal to reduce cost, and the desired outcome is to close an on-premises data center by a given date in 12 months. A resulting guiding principle is to lift and shift all applications to the cloud by using a rehost migration strategy whenever possible. In this case, the lift-and-shift approach accelerates near-term migration outcomes. After the applications have moved out of the on-premises data center, the company can focus on other business drivers to optimize or modernize the migrated workloads. @@ -42 +42 @@ Increase operational resiliency. | Improved uptime, reduced mean time to recover -Exit the data center. | Data-center closure by a date within 6–12 months | Speed of server migrations | Rehost applications by using Cloud Migration Factory Solution. +Exit the data center. | Data-center closure by a date within 6–12 months | Speed of server migrations | Rehost applications by using [AWS Application Migration Service](https://aws.amazon.com/application-migration-service/). @@ -44,0 +45,2 @@ Stay on premises, but increase agility and resiliency. | Improved competitivenes +It is also important to define architectural principles that inform the migration strategies. For example, you might introduce an architectural principle for the AWS Cloud that all migrated applications must encrypt all communications. If this kind of principle is not currently applied on-premises, it forces migration teams to implement changes as part of migration, which affects effort and planning. Define all architectural principles and share them with the relevant teams. +