AI Services Market › Use cases › Software & DevOps
Software & DevOpsDone with Claude Oct 30, 2026
Diagnose AWS issues with read-only Claude access
A startup engineer gives Claude read-only access to AWS, logs and the database, and it investigates issues and writes a report, though it sometimes makes things up. · Oct 30, 2026
- What They Did
- A startup engineer who covers the whole stack (code, deployment, database, cloud, networking) gives Claude read-only access to AWS, the logs and the database. Instead of manually reading logs, checking routing tables and cross-checking against database data, they let Claude use the AWS CLI to investigate the issue. It then writes a detailed report that can be passed to others.
- How It Went
- The author says it solves issues roughly 10x faster than they could. It sometimes makes things up, and the author worries about skill atrophy, including for future job interviews.
- Worth Knowing
- Read-only access limits the damage, but the report can contain invented claims, so verify its findings before passing them along.
Try it yourself with Claude
I'm giving you read-only access to [my AWS account/profile], [log source], and [database]. Investigate this problem: [describe the symptom and when it started]. Only run read-only commands, and don't change or delete anything. Write a report with what you found, the evidence for each claim (log lines, queries, resource IDs), and anything you're unsure about, clearly marked as a guess rather than a fact.