AWS prescriptive-guidance documentation change
Summary
Updated terminology from 'inventory' to 'documentation', restructured section headers with markdown syntax, modified requirement levels (R/O) in data attribute tables, added network connection details, expanded discovery tool evaluation criteria including new security questions, enhanced software/database discovery features, and improved wording throughout.
Security assessment
The change adds a specific security question ('What data is collected by the tool?') under the discovery tool selection criteria. This enhances security documentation by prompting evaluation of data collection practices but doesn't address a specific vulnerability. Other modifications are structural or clarify non-security aspects like data fidelity requirements and cost attributes.
Diff
diff --git a/prescriptive-guidance/latest/application-portfolio-assessment-guide/understanding-initial-assessment-data-requirements.md b/prescriptive-guidance/latest/application-portfolio-assessment-guide/understanding-initial-assessment-data-requirements.md index e302e63f3..65d536455 100644 --- a//prescriptive-guidance/latest/application-portfolio-assessment-guide/understanding-initial-assessment-data-requirements.md +++ b//prescriptive-guidance/latest/application-portfolio-assessment-guide/understanding-initial-assessment-data-requirements.md @@ -23 +23 @@ To guide these conversations, use the following set of questions: - * Does the current inventory, such as the CMDB, contain application-to-infrastructure mapping? Is each infrastructure asset associated to an application? Is each application mapped to infrastructure? + * Does the current documentation, such as the CMDB or equivalent, contain application-to-infrastructure mapping? Is each infrastructure asset associated to an application? Is each application mapped to infrastructure? @@ -25 +25 @@ To guide these conversations, use the following set of questions: - * Does the inventory contain a catalog of licenses and licensing agreements for each product? + * Does the documentation contain a catalog of licenses and licensing agreements for each product? @@ -27 +27 @@ To guide these conversations, use the following set of questions: - * Does the inventory contain dependency data? Note the existence of communication data such as server to server, application to application, application or server to database. + * Does the documentation contain dependency data? Note the existence of communication data such as server to server, application to application, application or server to database. @@ -29 +29 @@ To guide these conversations, use the following set of questions: - * What other tools that can provide application and infrastructure information are available in the environment? Note the existence of performance, monitoring, and management tools that can be used as a source of data. + * What other tools that can provide application and infrastructure information are available in the environment? Note the existence of performance, monitoring, repositories, knowledge bases, and management tools that can be used as a source of data. @@ -40 +40 @@ The data fidelity levels in the following table are provided as examples. We rec -**Data sources** | **Fidelity level** | **Portfolio coverage** | **Comments** +**Data sources** | **Fidelity level assessment** | **Portfolio coverage** | **Comments** @@ -63 +63 @@ The following tables specify the required and optional data attributes for each -**Applications** +### Applications @@ -77 +77 @@ Dependencies | Upstream and downstream dependencies to internal and external app -Infrastructure mapping | Mapping to physical and/or virtual assets that make up the application | O | O | Medium +Infrastructure mapping | Mapping to physical and/or virtual assets that make up the application | R | O | Medium @@ -79 +79 @@ License | Commodity software license type (e.g., Microsoft SQL Server Enterprise -Cost | Costs for software license, software operations, and maintenance | N/A | O | Medium +Cost | Costs for software license, software operations, and maintenance | O | O | Medium @@ -81 +81 @@ Cost | Costs for software license, software operations, and maintenance | N/A | -**Infrastructure** +### Infrastructure @@ -88 +88 @@ DNS name (fully qualified domain name, or FQDN) | DNS name | O | O | Medium -IP address and netmask | Internal and/or public IP addresses | R | O | Medium-high +IP address and netmask | Internal and/or public IP addresses | O | O | Medium-high @@ -93,5 +93,4 @@ Configuration | Allocated CPU, number of cores, threads per core, total memory, -Utilization | CPU, memory, and storage peak and average. Database instance throughput. | R | O | Medium-high -License | Commodity license type (e.g., RHEL Standard) | R | R | Medium -Is shared infrastructure? | Yes or No to denote infrastructure services that provide shared services such as authentication provider, monitoring systems, backup services, and similar services | R | R (D) | Medium -Application mapping | Applications or application components that run in this infrastructure | O | O | Medium -Cost | Fully loaded costs for bare-metal servers, including hardware, maintenance, operations, storage (SAN, NAS, Object), operating system license, share of rackspace, and data center overheads | N/A | O | Medium-high +Utilization | CPU, memory, and storage peak and average. Database instance throughput. | O | O | Medium-high +License | Commodity license type (e.g., RHEL Standard) | O | R | Medium +Application mapping | Applications or application components that run in this infrastructure | R | O | Medium +Cost | Fully loaded costs for bare-metal servers, including hardware, maintenance, operations, storage (SAN, NAS, object), operating system licenses, rackspace share, and data center overhead | O | O | Medium-high @@ -99 +98 @@ Cost | Fully loaded costs for bare-metal servers, including hardware, maintenanc -**Networks** +### Networks @@ -101 +100 @@ Cost | Fully loaded costs for bare-metal servers, including hardware, maintenanc -**Attribute Name** | **Description** | **Inventory and prioritization** | **Business case** | **Recommended fidelity level (minimum)** +**Attribute name** | **Description** | **Inventory and prioritization** | **Business case** | **Recommended fidelity level (minimum)** @@ -103,0 +103 @@ Size of pipe (Mb/s), redundancy (Y/N) | Current WAN link specifications (e.g., 1 +Connected locations | Named locations connected by this link | O | O | Medium @@ -105 +105 @@ Link utilization | Peak and average utilization, outbound data transfer (GB/mont -Latency (ms) | Current latency between connected locations. | O | O | Medium +Latency (ms) | Current latency between connected locations | O | O | Medium @@ -108 +108 @@ Cost | Current cost per month | N/A | O | Medium -**Migration** +### Migration @@ -112,4 +112,4 @@ Cost | Current cost per month | N/A | O | Medium -Rehost | Customer and partner effort for each workload (person-days), customer and Partner cost rates per day, tool cost, number of workloads | N/A | R (F) | Medium-high -Replatform | Customer and partner effort for each workload (person-days), customer and partner cost rates per day, number of workloads | N/A | R (F) | Medium-high -Refactor | Customer and partner effort for each workload (person-days), customer and partner cost rates per day, number of workloads | N/A | O | Medium-high -Retire | Number of servers, average decommission cost | N/A | O | Medium-high +Rehost cost | Customer and partner effort for each workload (person-days), customer and Partner cost rates per day, tool cost, number of workloads | N/A | R (F) | Medium-high +Replatform cost | Customer and partner effort for each workload (person-days), customer and partner cost rates per day, number of workloads | N/A | R (F) | Medium-high +Refactor cost | Customer and partner effort for each workload (person-days), customer and partner cost rates per day, number of workloads | N/A | R (F) | Medium-high +Retire cost | Number of servers, average decommission cost | N/A | O | Medium-high @@ -120 +120 @@ Parallel cost | Time frame and rate at which as-is costs can be removed during m -Time frame and rate at which AWS products and services, and other infrastructure costs, are introduced during migration | N/A | O | Medium-high +Parallel cost | Time frame and rate at which AWS products and services, and other infrastructure costs, are introduced during migration | N/A | O | Medium-high @@ -124,3 +124 @@ Time frame and rate at which AWS products and services, and other infrastructure -Does your organization need discovery tooling? Portfolio assessment requires high-confidence, up-to-date data about applications and infrastructure. Initial stages of portfolio assessment can use assumptions to fill data gaps. - -However, as progress is made, high-fidelity data enables the creation of successful migration plans and the correct estimation of target infrastructure to reduce cost and maximize benefits. It also reduces risk by enabling implementations that consider dependencies and avoids migration pitfalls. The primary use case for discovery tooling in cloud migration programs is to reduce risk and increase confidence levels in data through the following: +Does your organization need discovery tooling? Portfolio assessment requires high-confidence, up-to-date data about applications and infrastructure. Initial stages of portfolio assessment can use assumptions to fill data gaps. However, as progress is made, high-fidelity data helps you create successful migration plans and correctly estimate the target infrastructure to reduce costs and maximize benefits. It also reduces risk by enabling implementations that consider dependencies and avoids migration pitfalls. The primary use case for discovery tooling in cloud migration programs is to reduce risk and increase confidence levels in data through the following: @@ -143 +141 @@ When there is uncertainty about whether systems exist in a given location, most -Further stages of application portfolio assessment and migration heavily rely on accurate dependency-mapping information. Dependency mapping provides an understanding of the infrastructure and configuration that will be required in AWS (such as security groups, instance types, account placement, and network routing). It also helps with grouping applications that must move at the same time (such as applications that must communicate over low latency networks). In addition, dependency mapping provides information for evolving the business case. +Further stages of application portfolio assessment and migration heavily rely on accurate dependency-mapping information. Dependency mapping provides an understanding of the infrastructure and configuration that will be required in AWS (such as security groups, instance types, account placement, and network routing). It also helps with grouping applications that must move at the same time (such as applications that must communicate over low latency networks). @@ -147 +145 @@ When deciding on a discovery tool, it is important to consider all stages of the -_How to select a discovery tool?_ +### How to select a discovery tool? @@ -151 +149,3 @@ Several discovery tools in the market provide different features and capabilitie -_Security_ +#### Security + + * What data is collected by the tool? @@ -174 +174 @@ Ensure that security teams are involved in early conversations about discovery t -_Data sovereignty_ +#### Data sovereignty @@ -189 +189 @@ Consider your organization needs in terms of data residency requirements. -_Architecture_ +#### Architecture @@ -191 +191 @@ _Architecture_ - * What infrastructure is required and what are the different components? + * What infrastructure is required to deploy the tool, and what are the different components? @@ -193 +193 @@ _Architecture_ - * Is more than one architecture available? + * Is more than one architecture or deployment model available? @@ -200 +200 @@ _Architecture_ -_Performance_ +#### Performance @@ -207 +207 @@ _Performance_ -_Compatibility and scope_ +#### Compatibility and scope @@ -216 +216 @@ _Compatibility and scope_ -_Collection methods_ +#### Collection methods @@ -220 +220 @@ _Collection methods_ - * Does it support agent-less deployments? + * Does it support agent-less data collection? @@ -229 +229 @@ _Collection methods_ -_Features_ +#### Features @@ -252 +252 @@ Consider tools with strong application and infrastructure dependency-mapping fun -_Cost_ +#### Cost @@ -267 +267 @@ Discovery tools are typically used throughout the entire lifecycle of migration -_Support model_ +#### Support model @@ -278 +278 @@ _Support model_ -_Professional services_ +#### Professional services @@ -293 +293 @@ To find and evaluate discovery tooling, use the [Discovery, Planning, and Recomm -_Recommended features for the discovery tool_ +### Recommended features for the discovery tool @@ -297 +297 @@ To avoid provisioning and combining data from multiple tools over time, a discov - * **Software** – The discovery tool should be able to identify running processes and installed software. + * **Software** – The discovery tool should be able to identify running processes and installed runtimes, packages, and frameworks. @@ -304,0 +305,2 @@ To avoid provisioning and combining data from multiple tools over time, a discov + * **Database discovery** – It should be able to discover databases, instances, and schemas, including engine types and versions. + @@ -318 +320 @@ To avoid provisioning and combining data from multiple tools over time, a discov -_Additional features to consider_ +### Additional features to consider @@ -336 +338 @@ _Additional features to consider_ - * **Wave planning** (for example, recommended groups of applications and the ability to create migration wave plans) + * **Wave planning** (for example, recommended groups of applications and help creating migration wave plans) @@ -343 +345 @@ _Additional features to consider_ -_Deployment considerations_ +### Deployment considerations