Let Claude triage AWS incidents in read-only mode

A startup engineer had Claude inspect cloud systems, logs, and database data without write access, then compile a findings report.

Done with Claudeยท Intermediateยท Oct 2026

What they did
The engineer handles application code, deployment, data, cloud infrastructure, and networking, so they handed first-pass incident work to Claude. They gave it read-only access to AWS, log data, and the database, then had it use the AWS CLI to search for clues instead of manually combing through everything themselves. Claude pulled together a detailed report that could be shared with the rest of the team.
How it went
The engineer says this approach resolves problems about 10x faster than they can on their own. Claude can still invent details, though, so its report needs verification before anyone treats it as reliable.
Tips
Read-only permissions reduce risk, but they do not prevent bad conclusions. Ask for sources on every claim and verify anything you plan to pass along.

Try it yourself with Claude

Please investigate this issue using only read-only access to [AWS environment], [log location], and [database]. The symptom is: [describe what is happening and when it started]. Use the AWS CLI and any other non-destructive checks you need, but do not edit, delete, create, or submit anything. For each conclusion, include the supporting evidence such as log entries, query results, or resource IDs, and clearly mark any uncertain point as a hypothesis. Before any action that would alter data, send a message asking for my approval and stop until I respond.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on news.ycombinator.com โ†—

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.