AWS devopsagent documentation change
Summary
Updated documentation for AWS DevOps Agent topology features, including new 'Learned' view generated by Agent Space Understanding skill, renamed topology views (System, Container, Components, All Resources), and changed resource discovery method from tag-based to AWS Resource Explorer for non-CloudFormation resources.
Security assessment
The changes are feature updates and documentation improvements without any mention of security vulnerabilities, patches, or incidents. The modifications describe new visualization capabilities and updated resource discovery mechanisms using AWS Resource Explorer, which is a standard AWS service feature. No security advisories, vulnerability disclosures, or security configuration changes are referenced in the diff.
Diff
diff --git a/devopsagent/latest/userguide/about-aws-devops-agent-what-is-a-devops-agent-topology.md b/devopsagent/latest/userguide/about-aws-devops-agent-what-is-a-devops-agent-topology.md index 335a53f59..38402dfc7 100644 --- a//devopsagent/latest/userguide/about-aws-devops-agent-what-is-a-devops-agent-topology.md +++ b//devopsagent/latest/userguide/about-aws-devops-agent-what-is-a-devops-agent-topology.md @@ -5 +5 @@ -How topology graphs are createdKey capabilitiesTopology viewsResource discoveryInvestigation scope beyond topology +How topology graphs are createdKey capabilitiesTopology viewsResource discoveryInvestigation scope beyond topologyTopology and the Agent Space Understanding skill @@ -45 +45 @@ Resource mapping provides several capabilities that enhance incident investigati -The topology visualization in DevOps Center page in the Operator Web App offers multiple levels of detail: +The topology visualization in the Topology page in the Operator Web App offers multiple levels of detail: @@ -47 +47 @@ The topology visualization in DevOps Center page in the Operator Web App offers - * **System view** – Shows high-level account and region boundaries + * **Learned** – The default view, generated from the Agent Space Understanding skill. Displays a structured summary of your infrastructure organized by logical services and request paths. @@ -49 +49 @@ The topology visualization in DevOps Center page in the Operator Web App offers - * **Container view** – Displays deployment stacks like CloudFormation stacks that contain related resources + * **System** – Shows high-level account and region boundaries. @@ -51 +51 @@ The topology visualization in DevOps Center page in the Operator Web App offers - * **Resource view** – Shows the complete view with all resources and their relationships + * **Container** – Displays deployment stacks like CloudFormation stacks that contain related resources. @@ -52,0 +53 @@ The topology visualization in DevOps Center page in the Operator Web App offers + * **Components** – Shows individual components within containers and their relationships. @@ -53,0 +55 @@ The topology visualization in DevOps Center page in the Operator Web App offers + * **All Resources** – Shows the complete view with all discovered resources and their relationships. @@ -56 +57,0 @@ The topology visualization in DevOps Center page in the Operator Web App offers -## Resource discovery @@ -58 +58,0 @@ The topology visualization in DevOps Center page in the Operator Web App offers -Resources are discovered through two methods: @@ -60 +60 @@ Resources are discovered through two methods: - * **CloudFormation stacks** – The agent will list all of the CloudFormation stacks and their resources in the primary AWS account as well as an connected secondary accounts. This is supported for any infrastructure-as-code tooling that uses CloudFormation for deployment, including Cloud Development Kit (CDK). +## Resource discovery @@ -62 +62 @@ Resources are discovered through two methods: - * **Resource Tags** – For resources not deployed from CloudFormation, you can specify a list of AWS Tag keys and value pairs to include in the resource topology. This is useful to identify application boundaries for applications deployed through the AWS Management Console, the AWS service APIs, or other infrastructure-as-code frameworks. +Resources are discovered through two methods: @@ -63,0 +64 @@ Resources are discovered through two methods: + * **CloudFormation stacks** – The agent lists all CloudFormation stacks and their resources in the primary AWS account and any connected secondary accounts. This is supported for any infrastructure-as-code tooling that uses CloudFormation for deployment, including AWS Cloud Development Kit (AWS CDK). @@ -64,0 +66 @@ Resources are discovered through two methods: + * **Resource Explorer** – For resources not deployed from CloudFormation, tagged resources are discovered from AWS Resource Explorer. The target AWS account must have Resource Explorer enabled. This is useful for identifying application boundaries for resources deployed through the AWS Management Console, the AWS service APIs, or other infrastructure-as-code frameworks. @@ -67 +68,0 @@ Resources are discovered through two methods: -###### Note @@ -69 +69,0 @@ Resources are discovered through two methods: - __The target AWS account must have Resource Explorer enabled to discover tagged resources. @@ -76,0 +77,4 @@ To limit the resources the agent has access to, restrict the policy for the role +## Topology and the Agent Space Understanding skill + +The topology graph feeds into the Agent Space Understanding learned skill, which encodes a structured summary of your infrastructure for use during investigations. When topology discovery completes for a new agent space, the system automatically generates the Agent Space Understanding skill. For more information about learned skills, see [Learned Skills](./about-aws-devops-agent-learned-skills.html). +