AWS prescriptive-guidance documentation change
Summary
Updated documentation structure and content for application portfolio assessment data requirements. Changes include: converting section headers to markdown H2 format, adding a new 'Connected locations' field in Networks section, modifying column values in tables (e.g., changing 'N/A' to 'O' for Cost fields), adding 'cost' suffix to migration attributes, and correcting typos/formatting.
Security assessment
The changes are documentation improvements focusing on data requirements for portfolio assessments and migration planning. No security vulnerabilities, incidents, or security-specific features are mentioned. Modifications relate to cost tracking, infrastructure mapping, and data collection processes without any security context or implications.
Diff
diff --git a/prescriptive-guidance/latest/application-portfolio-assessment-guide/understanding-complete-assessment-data-requirements.md b/prescriptive-guidance/latest/application-portfolio-assessment-guide/understanding-complete-assessment-data-requirements.md index b61b04628..9ce99903e 100644 --- a//prescriptive-guidance/latest/application-portfolio-assessment-guide/understanding-complete-assessment-data-requirements.md +++ b//prescriptive-guidance/latest/application-portfolio-assessment-guide/understanding-complete-assessment-data-requirements.md @@ -6,0 +7,2 @@ +ApplicationsInfrastructureNetworksMigration + @@ -22 +24 @@ The tables use the following abbreviations: -**Applications** +## Applications @@ -24 +26 @@ The tables use the following abbreviations: -**Attribute name** | **Description** | **Inventory and prioritization** | **Detailed Business case** | **Recommended fidelity level (minimum)** +Attribute name | Description | Inventory and prioritization | Detailed business case | Recommended fidelity level (minimum) @@ -38 +40 @@ License | Commodity software license type (for example, Microsoft SQL Server Ent -Cost | Costs for software license, software operations, and maintenance | N/A | R | Medium-high +Cost | Costs for software license, software operations, and maintenance | O | R | Medium-high @@ -45 +47 @@ Support tickets | 12–24 months of data to help assess the productivity and fin -**Infrastructure** +## Infrastructure @@ -47 +49 @@ Support tickets | 12–24 months of data to help assess the productivity and fin -**Attribute name** | **Description** | **Inventory and prioritization** | **Business case** | **Recommended fidelity level (minimum)** +Attribute name | Description | Inventory and prioritization | Business case | Recommended fidelity level (minimum) @@ -59 +60,0 @@ License | Commodity license type (for example, RHEL Standard) | R | R | High -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 | High @@ -61,2 +62,2 @@ Application mapping | Applications or application components that run in this in -Cost | Fully loaded costs for bare-metal servers, including hardware, maintenance, operations, storage (SAN, NAS, Object), operating system license, share of rack space, and data center overheads | N/A | R | Medium-high -Estimated volume of data transfer (in/out) | For example, per infrastructure asset over per day over a 30 days period | O | R | Medium +Cost | Fully loaded costs for bare-metal servers, including hardware, maintenance, operations, storage (SAN, NAS, object), operating system license, share of rack space, and data center overheads | O | R | Medium-high +Estimated volume of data transfer (in/out) | For example, per infrastructure asset per day over a 30-day period | O | R | Medium @@ -64 +65 @@ Estimated volume of data transfer (in/out) | For example, per infrastructure ass -**Networks** +## Networks @@ -66 +67 @@ Estimated volume of data transfer (in/out) | For example, per infrastructure ass -**Attribute name** | **Description** | **Inventory and prioritization** | **Business case** | **Recommended fidelity level (minimum)** +Attribute name | Description | Inventory and prioritization | Business case | Recommended fidelity level (minimum) @@ -68,0 +70 @@ Size of pipe (Mb/s), redundancy (Y/N) | Current WAN link specifications (for exa +Connected locations | Named locations connected by this link | R | O | High @@ -73 +75 @@ Cost | Current cost per month | N/A | R | Medium-high -**Migration** +## Migration @@ -75 +77 @@ Cost | Current cost per month | N/A | R | Medium-high -**Attribute name** | **Description** | **Inventory and prioritization** | **Business case** | **Recommended fidelity level (minimum)** +Attribute name | Description | Inventory and prioritization | Business case | Recommended fidelity level (minimum) @@ -77,4 +79,4 @@ Cost | Current cost per month | N/A | R | Medium-high -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 | 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 | Medium-high -Refactor | Customer and partner effort for each workload (person-days), customer and partner cost rates per day, number of workloads | N/A | R | Medium-high -Retire | Number of servers, average decommission cost | N/A | R | 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 | 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 | 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 | Medium-high +Retire cost | Number of servers, average decommission cost | N/A | R | Medium-high @@ -93 +95 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Previous +Portfolio analysis and migration planning