aws/agent-toolkit-for-aws

aws-investigation

Investigates what is happening in an AWS account from evidence already recorded there.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/aws/agent-toolkit-for-aws --skill aws-investigation

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

AWS Investigation

An investigation answers a question about what an AWS account is doing, and every claim in the answer must come from something you read: a deployed artifact, a service's own log record, or a query result. Inference from names, descriptions, the newest stored version or one service's view of another is a lead, never evidence.

Pick the reference

Read the reference that matches the question before you start; most investigations need more than one.

The question is aboutRead
What a deployed system currently does, serves or executes: live configuration, feature flags, parameters, which code runs, reproducing a code path's query, or a first data route that is blockedreferences/deployed-artifacts.md
A request, alarm or incident that spans several services: tracing one request, counting failed requests, deciding where an event was lostreferences/multi-service-logs.md
Facts in the account's data: finding where data lives, exact counts and breakdowns, filtering, joining or exporting records, the rules behind failed or unmatched recordsreferences/data-investigation.md
Whether a finding is complete and a root cause holds: searching every region and scope, paginating before counting, coverage of a date range, one entity vs the whole affected population, consistency of the root cause, whether a runbook fixes the cause, answering the user's own questionreferences/completeness-and-root-cause.md

Rules for every investigation

  1. Explore before you give up. Assume the credentials are the intended environment. Treat

unfamiliar or internal terms (service nicknames, airport-code regions such as PDX = us-west-2, IAD = us-east-1) as search hints: list resources, log groups and data stores in the likely regions and search for the identifiers in the request before saying something cannot be done.

  1. Separate evidence from inference. Keep a short provenance note per claim

(claim <- artifact, record or query). Label anything you did not read as a hypothesis or UNVERIFIED, with the routes you tried.

  1. Count exactly. Use aggregate queries run in the engine, scoped to exactly what was asked, and

report unique entities separately from raw records.

  1. Quote, don't paraphrase. Give identifiers, field values, error codes and messages exactly as

the source produced them, including null and empty values.

  1. Finish the task. Produce every requested artifact (files, tables, plans), and state the

assumptions you made in the final answer.

Closing checklist

Before submitting your analysis:

  1. Have you searched all relevant regions and scopes?
  2. Have you paginated through all results, and said which part of the requested range has data?
  3. Have you verified the scope of failures (entity-specific vs fleet-wide, the whole affected

population)?

  1. Does your root cause fit all the facts you found?
  2. Have you labelled every mechanism you could not confirm as unverified, and reported a

missing component as a defect only if it was meant to exist?

  1. Did your claims about live configuration come from the deployed artifact, not the latest

stored version (deployed-artifacts.md)?

  1. For a request that crosses services, did you read each service's own logs and place the

failure boundary per event (multi-service-logs.md)?

  1. Have you answered the user's specific question directly?
  2. Before you finish, have you reread your conclusion against each piece of evidence you

collected and removed any statement that contradicts it?

  1. Have you removed any contradictions between your findings and recommendations, and checked

each runbook option against the confirmed cause?

来自同一仓库

更多 Skills

全部 Skills
aws
官方

amazon-aurora-mysql

Amazon Aurora MySQL — creates, modifies, and advises on Aurora MySQL clusters specifically (MySQL-compatible engine, Aurora serverless, parallel query). Trigger for Aurora MySQL cluster operations, ACU sizing, I/O-Optimized storage, commitment pricing, or MySQL upgrade planning. Aurora MySQL uses full (VPC-based) configuration — express configuration is PostgreSQL-only. For Aurora PostgreSQL, use amazon-aurora-postgresql instead. Contains safety guardrails and response templates that override de

1小时安装量
2
GitHub Stars
3536
最近更新
11月20日
aws
官方

amazon-aurora-postgresql

Amazon Aurora PostgreSQL — creates, modifies, and advises on Aurora PostgreSQL clusters specifically (PostgreSQL-compatible engine, Aurora serverless, express configuration, pgvector, Babelfish). Trigger for Aurora PostgreSQL cluster operations, express-configuration quick-start, ACU sizing, I/O-Optimized storage, commitment pricing, or PostgreSQL upgrade planning. For Aurora MySQL, use amazon-aurora-mysql instead. Contains safety guardrails, express-first routing, and response templates that ov

1小时安装量
2
GitHub Stars
3536
最近更新
11月20日
aws
官方

amazon-bedrock

Builds generative AI applications on Amazon Bedrock. Covers model invocation (Converse API, InvokeModel), RAG with Knowledge Bases, Bedrock Agents, Guardrails, and AgentCore (including the Harness managed agent loop). Applies when invoking models, setting up or migrating Knowledge Bases to Managed, deploying to AgentCore, migrating/porting/converting a Bedrock Agent (including inline agents) to an AgentCore Harness, troubleshooting Bedrock errors (ThrottlingException, AccessDeniedException), or

1小时安装量
2
GitHub Stars
3536
最近更新
11月20日
aws
官方

amazon-braket

Runs quantum workflows on AWS / Amazon Braket: circuits and algorithms, QPU/device and ARN discovery, LocalSimulator, tasks, program sets, Hybrid Jobs, S3 results, pricing, account setup, and spending limits. Applies to quantum programs and execution, AHS, OpenQASM, pulse control, reservations, notebooks, or Qiskit or PennyLane integrations.

1小时安装量
2
GitHub Stars
3536
最近更新
11月20日