Using Local Agents for Development via AWS
By far one of the easiest development workflows is to literally just tell Claude to standup some AWS infra and it creates the aws cli commands required and runs them, that or boto3 and runs them as well.
I tell Claude through hooks to use only read-only roles but (AFIAK, happy to be corrected) there's no way to enforce this config to everyone in our org.
I work in cyber so I understand the graveness of blindly letting Claude hit the AWS API with my write creds, but how are others tackling this? i.e. an offshore dev let's an agent (doesn't have to be Claude) do the same but blindly approves everything and it starts deleting things. I've seen it tell an analyst that they should remove an SCP to get their program to work and it actually attempted to do so, only failing because they weren't in the org admin account.
Posted May 7, 2026, 12:43 PM UTC