AWS prescriptive-guidance documentation change
Summary
Minor text edits including punctuation correction, updated function reference link, emphasized 'graph data model' and 'network graph' terms, and changed 'Documentation generation' to 'Document generation'
Security assessment
Changes are grammatical improvements and formatting adjustments without any security implications. Dependency mapping remains focused on resource relationships without introducing new security concepts or addressing vulnerabilities.
Diff
diff --git a/prescriptive-guidance/latest/automating-aws-infrastructure-documentation-generation-and-analysis/dependency-mapping.md b/prescriptive-guidance/latest/automating-aws-infrastructure-documentation-generation-and-analysis/dependency-mapping.md index 11ec2df6d..b92d4b0ec 100644 --- a//prescriptive-guidance/latest/automating-aws-infrastructure-documentation-generation-and-analysis/dependency-mapping.md +++ b//prescriptive-guidance/latest/automating-aws-infrastructure-documentation-generation-and-analysis/dependency-mapping.md @@ -11 +11 @@ Key responsibilities of the dependency mapping componentWorkflow of the dependen -The _dependency mapping_ component analyzes relationships between AWS resources and builds a comprehensive graph of how AWS services interact with each other. Unlike the scanning phase (which only inventories resources) and the documentation phase (which explains configurations and best practices), dependency mapping focuses on interconnections. To infer how resources are linked, this phase relies heavily on resource-based policies (for example, Amazon S3 bucket policies, Lambda execution permissions, and Amazon SNS or Amazon SQS access controls). +The _dependency mapping_ component analyzes relationships between AWS resources and builds a comprehensive graph of how AWS services interact with each other. Unlike the scanning phase (which only inventories resources) and the documentation phase (which explains configurations and best practices), dependency mapping focuses on interconnections. To infer how resources are linked, this phase relies heavily on resource-based policies (for example, Amazon S3 bucket policies, Lambda execution permissions, Amazon SNS or Amazon SQS access controls). @@ -50 +50 @@ The mapping process includes a continuation mechanism that does the following: -The [generate_service_markdown_with_continuation](https://github.com/awslabs/InfraDocGen/blob/dc1ea8a4ebdba821f6954a2b03c4fecbec809c10/services/bedrock_service.py#L794) function ensures that services are processed sequentially and that the continuation prompt logic is handled with retries in case of rate limits or incomplete analysis. +The [generate_service_markdown_with_continuation](https://github.com/awslabs/InfraDocGen/blob/dc1ea8a4ebdba821f6954a2b03c4fecbec809c10/services/policy_extractor.py#L146) function ensures that services are processed sequentially and that the continuation prompt logic is handled with retries in case of rate limits or incomplete analysis. @@ -60 +60 @@ This process is handled by the method [combine_service_markdown_results](https:/ -The Markdown output is parsed and transformed into a graph data model (nodes and edges) using [React Flow](https://www.npmjs.com/package/reactflow) as follows: +The Markdown output is parsed and transformed into a **graph data model** (nodes and edges) using [React Flow](https://www.npmjs.com/package/reactflow) as follows: @@ -64 +64 @@ The Markdown output is parsed and transformed into a graph data model (nodes and - * _Edges_ represent connections or access relationships such as Lambda to `S3: InvokeFunction`. This enables the frontend to render a network graph where dependencies can be visually explored. + * _Edges_ represent connections or access relationships such as Lambda to `S3: InvokeFunction`. This enables the frontend to render a **network graph** where dependencies can be visually explored. @@ -100 +100 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Documentation generation +Document generation