# Chatting With AWS Devops Agent

Have a fast, conversational analysis with the AWS DevOps Agent.

- Repository: https://github.com/aws/agent-toolkit-for-aws (3366 stars)
- Category: Security
- License: Apache-2.0
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add aws/agent-toolkit-for-aws --skill chatting-with-aws-devops-agent -g -a claude-code -y`
Codex: `npx skills add aws/agent-toolkit-for-aws --skill chatting-with-aws-devops-agent -g -a codex -y`
Cursor: `npx skills add aws/agent-toolkit-for-aws --skill chatting-with-aws-devops-agent -g -a cursor -y`
Gemini CLI: `npx skills add aws/agent-toolkit-for-aws --skill chatting-with-aws-devops-agent -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add aws/agent-toolkit-for-aws`

## Description

Have a fast, conversational analysis with the AWS DevOps Agent. Use for cost optimization, architecture review, topology mapping, knowledge / runbook discovery, security audits, dependency questions, and quick diagnostics, anything that needs a 5-30 second answer rather than a 5-8 minute deep investigation. Trigger words include cost, optimize, review, architecture, topology, what runbooks, show me, compare, audit, what if.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Chat with the AWS DevOps Agent

> **AgentSpace routing (SigV4 only):** If `list_agent_spaces` is available in your tool list and the multi-space orchestration skill has NOT been invoked yet this session, invoke it first to determine which `agent_space_id` to use. Then pass `agent_space_id` on all tool calls below. For bearer token auth this is unnecessary, the token is already scoped to one space.

Chat is the **default**. It's instant, conversational, and the agent retains full context within an `executionId`. Only escalate to `investigating-incidents-with-aws-devops-agent` when the user describes an incident or the agent itself suggests deeper analysis is warranted.

## How to send messages

**Primary, use the `chat` tool:**

```
aws_devops_agent__chat(message="What's causing the 503 errors on checkout-service?")
→ {"executionId": "uuid", "answer": "Based on my analysis..."}
```

One call, full answer. No session setup needed, the tool handles CreateChat + SendMessage + response parsing internally.

**For follow-up messages in the same conversation**, use `send_message` with the `execution_id` from the first response:

```
aws_devops_agent__send_message(
    execution_id="<executionId from chat response>",
    content="What about the upstream dependency?"
)
→ "The upstream service shows..."
```

The agent retains full context within an `executionId`. Reuse it for follow-ups, don't call `chat` again for the same conversation.

**For browsing previous conversations:**

```
aws_devops_agent__list_chats()
→ {"chats": [...]}
```

## Injecting local context

Pack local workspace knowledge into the `message` parameter. This is the killer feature, the DevOps Agent knows your AWS cloud; you know the user's local workspace.

```
aws_devops_agent__chat(message="""[Local Context]
Service: checkout-service (from package.json)
Last deploy: commit abc1234, 2h ago
CDK Stack: lib/checkout-stack.ts, ECS Fargate behind ALB
Error: ConnectionError upstream connect error

The rest: https://github.com/aws/agent-toolkit-for-aws/blob/HEAD/plugins/aws-agents-for-devsecops/skills/chatting-with-aws-devops-agent/SKILL.md