aws-investigation
Investigates what is happening in an AWS account from evidence already recorded there. Not for capturing new data from running code (snapshots of function arguments on a live service, Dynamic Instrumentation), questions answered from the CloudWatch Omni context graph or Application Signals service map, or building or changing infrastructure. Covers reading deployment records instead of the newest stored version (completed AppConfig deployments, the version an alias points to, a stack's current template), following a request through every service's own logs (exact per-layer fields, unique failed requests in an alarm's breach window, failure boundary per event), and answering questions from the account's data (exact counts and breakdowns, coverage of the requested range, exact filters and joins, the rule behind failed or unmatched records, verbatim values). Use to triage an alarm, error spike or failed request, trace a request across services, or count, break down, extract or join records.
- Version
- 1
Pinned to revision 00840a095dcc, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/aws-investigation/SKILL.md
- skills/aws-investigation/references/completeness-and-root-cause.md
- skills/aws-investigation/references/data-investigation.md
- skills/aws-investigation/references/deployed-artifacts.md
- skills/aws-investigation/references/multi-service-logs.md
Every link opens the file at its source, pinned to the revision this page describes.