AWS devopsagent documentation change
Summary
Added Agent-to-Agent (A2A) integration method. Updated MCP integration details to include authentication methods (access tokens/SigV4) and IDE examples. Removed specific GitHub power references.
Security assessment
Introduces authentication mechanisms (access tokens and AWS SigV4) for remote endpoints but doesn't address specific vulnerabilities. Enhances security documentation by specifying authentication requirements for agent connections. No evidence of patching existing security flaws.
Diff
diff --git a/devopsagent/latest/userguide/working-with-devops-agent-accessing-devops-agent-index.md b/devopsagent/latest/userguide/working-with-devops-agent-accessing-devops-agent-index.md index b8e7fca4d..2369d9fca 100644 --- a//devopsagent/latest/userguide/working-with-devops-agent-accessing-devops-agent-index.md +++ b//devopsagent/latest/userguide/working-with-devops-agent-accessing-devops-agent-index.md @@ -7 +7 @@ -DevOps Agent web appModel Context Protocol (MCP) integrationAgent Client Protocol (ACP) integrationWebhooksAWS DevOps Agent API +DevOps Agent web appModel Context Protocol (MCP) integrationAgent-to-Agent (A2A) integrationAgent Client Protocol (ACP) integrationWebhooksAWS DevOps Agent API @@ -11 +11 @@ DevOps Agent web appModel Context Protocol (MCP) integrationAgent Client Protoco -AWS DevOps Agent supports five access methods: the web app console, Model Context Protocol (MCP) integration, Agent Client Protocol (ACP) integration, webhooks for event-driven automation, and direct API access. Choose the method that best fits your workflow and technical requirements. +AWS DevOps Agent supports several access methods: the web app console, Model Context Protocol (MCP) integration, Agent-to-Agent (A2A) integration, Agent Client Protocol (ACP) integration, webhooks for event-driven automation, and direct API access. Choose the method that best fits your workflow and technical requirements. @@ -15 +15 @@ The following diagram illustrates these access methods and how they connect to t - + @@ -23 +23 @@ The web app is the primary interface for DevOps Agent. Use conversational chat t -You can access AWS DevOps Agent capabilities directly from MCP-compatible clients and IDEs. Use the [AWS MCP Server](https://docs.aws.amazon.com/aws-mcp/latest/userguide/what-is-mcp-server.html) to connect. You can investigate incidents, optimize costs, review architecture, and map topology without leaving your development environment. +You can access AWS DevOps Agent capabilities directly from MCP-compatible clients and IDEs such as Kiro, Claude Code, and Cursor. AWS DevOps Agent provides a dedicated remote MCP endpoint that you connect to using an access token or AWS SigV4 credentials. From your development environment, you can investigate incidents, optimize costs, review architecture, and map topology. For setup instructions, including the Kiro power and Claude Code plugin, see [Connect to DevOps Agent remote servers](./accessing-devops-agent-connect-to-devops-agent-remote-servers.html). @@ -25 +25 @@ You can access AWS DevOps Agent capabilities directly from MCP-compatible client -For [Kiro](https://kiro.dev/) users, a dedicated **aws-devops-agent** power is available in the [Kiro powers repository](https://github.com/kirodotdev/powers). This power connects Kiro to AWS DevOps Agent through the AWS MCP Server. It delivers AI-powered operational intelligence directly in your IDE. +The [AWS MCP Server](https://docs.aws.amazon.com/aws-mcp/latest/userguide/what-is-mcp-server.html) is also available for direct AWS API access, and serves as a fallback when the remote server endpoint is unavailable. @@ -27 +27,3 @@ For [Kiro](https://kiro.dev/) users, a dedicated **aws-devops-agent** power is a -For [Claude Code](https://docs.anthropic.com/en/docs/claude-code) users, the [sample-aws-devops-agent-claude-plugin](https://github.com/aws-samples/sample-aws-devops-agent-claude-plugin) provides a pre-configured plugin that connects Claude Code to AWS DevOps Agent through the AWS MCP Server. +## Agent-to-Agent (A2A) integration + +You can connect autonomous agents to AWS DevOps Agent through a dedicated Agent-to-Agent (A2A) v1.0 remote endpoint, using an access token or AWS SigV4 credentials. Agents can send messages, stream responses, and manage asynchronous tasks for agent-to-agent communication. For setup instructions, see [Connect to DevOps Agent remote servers](./accessing-devops-agent-connect-to-devops-agent-remote-servers.html).