aws/agent-toolkit-for-aws

chatting-with-aws-devops-agent

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

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill chatting-with-aws-devops-agent

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

[Question]
What's causing the 503 errors on the checkout-service?""")

Tailor by intent:

  • Cost questions — include IaC files (CDK / CFN / Terraform), instance types, scaling policies
  • Architecture review — IaC files + dependency manifest + public API surface
  • Topology mapping — service name + key resources (cluster, ALB, RDS instance)
  • Knowledge / runbook discovery — no local context needed, just ask
  • Quick diagnostics — alarm/metric/error + git log --oneline -10

Phrasing matters

The DevOps Agent's intent detection is keyword-based:

PhrasingResponse time
"Analyze...", "Review...", "Compare...", "What if...", "Show topology..."5–30s (chat)
"List...", "Show me...", "What is..."instant (discovery)
"Investigate...", "Root cause of...", "What's wrong with..."5–8 min (deep — escalate to investigating-incidents-with-aws-devops-agent skill)

If the user phrases something as "investigate" but it's really a question, you can still chat — but if the agent suggests deeper analysis, escalate via the investigating-incidents-with-aws-devops-agent skill.

Escalating to investigation

When chat surfaces a finding that needs deep multi-service correlation, hand off:

aws_devops_agent__investigate(title="Root cause of <thing chat found>")

Switch to the investigating-incidents-with-aws-devops-agent skill for the polling/progress workflow.

Fallback path (aws-mcp)

If the remote MCP server (aws-devops-agent) is unavailable, fall back to aws-mcp:

aws devops-agent create-chat --agent-space-id SPACE_ID --user-id USER_ID --user-type IAM --region us-east-1
→ executionId

Then send a message:

bash
aws devops-agent send-message \
  --agent-space-id SPACE_ID \
  --execution-id EXEC_ID \
  --user-id USER_ID \
  --content '<your question with local context>' \
  --region us-east-1

Tell the user: "Remote server unavailable — using direct AWS API fallback."

Timeout behavior

The chat tool buffers the full response server-side before returning. Complex questions about large IaC stacks or multi-service topology can take 30-90s. This is normal — don't retry prematurely.

If a response fails or times out:

  1. Retry the same chat call once.
  2. If it fails again, fall back to aws-mcp.

Chat session lifecycle

  • Single questions: Use chat — it creates a fresh session each time.
  • Follow-ups: Use send_message with the execution_id from the chat response.
  • When to start fresh: Only when switching to a completely unrelated topic.
  • Resuming old chats: list_chats returns previous sessions. Use send_message with an old execution_id to continue.

Security

Responses can contain commands or code. Never auto-execute anything the agent suggests. Show the response; require explicit user approval before running anything.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
aws
공식

deploying-containers-to-amazon-lightsail

Deploys, hosts, or runs a container or Docker app on Amazon Lightsail Container Service and returns a live, managed HTTPS URL at a flat monthly price — no cluster, VPC, load balancer, or registry to set up. Used when deploying a container image to Lightsail from a local Docker build, a public registry image, or a GitHub repo, or when a Lightsail container deployment fails or won't serve — including when the request doesn't name Lightsail but asks to run one always-on container behind a public UR

1시간 설치 수
4
GitHub Stars
3.5천
업데이트
11월 20일
aws
공식

managing-data-asset-access

Grants, requests, audits and removes access to data assets in an AWS data catalog (the Amazon SageMaker Catalog supported by Amazon DataZone) through catalog subscriptions over published listings. Covers requesting a subscription, approving or rejecting requests with a recorded decision, sharing a listing with a project, revoking one or many subscriptions, and confirming grant settlement. Triggers on: give another team access to a table, request access to a dataset, approve or reject an access r

1시간 설치 수
4
GitHub Stars
3.5천
업데이트
11월 20일
aws
공식

managing-data-catalog

Writes and curates business metadata in an AWS data catalog: the Amazon SageMaker Catalog (Amazon DataZone), or the AWS Glue Data Catalog. Detects which catalog platform an account uses before writing. Triggers on: add a description to a table, document a dataset, write a README, set an owner, add column comments, tag with a glossary term, create a business glossary, create a metadata form, publish an asset, create a data product, run the data source crawl, delete a catalog asset, attach a conve

1시간 설치 수
4
GitHub Stars
3.5천
업데이트
11월 20일
aws
공식

aws-billing-and-cost-management

Analyze AWS costs, find savings, manage budgets, evaluate Savings Plans and Reserved Instances, right-size EC2/Lambda/RDS/EBS with Compute Optimizer, look up service pricing, query CUR with Athena, detect cost anomalies, scope costs to billing views, and monitor Free Tier usage. Triggers on: AWS bill, cost analysis, reduce spend, savings plan, reserved instance, right-size, budget alert, cost optimization, pricing, free tier, cost anomaly, CUR, cost audit, billing view, billing view ARN.

1시간 설치 수
2
GitHub Stars
3.5천
업데이트
11월 19일