使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
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 about | Read |
|---|---|
| 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 blocked | references/deployed-artifacts.md |
| A request, alarm or incident that spans several services: tracing one request, counting failed requests, deciding where an event was lost | references/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 records | references/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 question | references/completeness-and-root-cause.md |
Rules for every investigation
- 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.
- 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.
- Count exactly. Use aggregate queries run in the engine, scoped to exactly what was asked, and
report unique entities separately from raw records.
- Quote, don't paraphrase. Give identifiers, field values, error codes and messages exactly as
the source produced them, including null and empty values.
- 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:
- Have you searched all relevant regions and scopes?
- Have you paginated through all results, and said which part of the requested range has data?
- Have you verified the scope of failures (entity-specific vs fleet-wide, the whole affected
population)?
- Does your root cause fit all the facts you found?
- 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?
- Did your claims about live configuration come from the deployed artifact, not the latest
stored version (deployed-artifacts.md)?
- 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)?
- Have you answered the user's specific question directly?
- Before you finish, have you reread your conclusion against each piece of evidence you
collected and removed any statement that contradicts it?
- Have you removed any contradictions between your findings and recommendations, and checked
each runbook option against the confirmed cause?