AWS just shipped the official way to let a coding agent build, deploy, and operate on your cloud — a managed MCP server, evaluated skills, and guardrails that finally distinguish what an **agent* did from what a human did. This is a deep dive on how the Agent Toolkit for AWS works, the IAM trick that makes it enterprise-ready, and how to wire it into Claude Code, Cursor, Codex, or Kiro without handing over the keys to the kingdom.*

Why This Matters

Point an AI coding agent at AWS and you get an instant taste of both heaven and hell.

Heaven: "spin up a serverless API with a DynamoDB table, wire the IAM role, and deploy it." The agent knows CloudFormation, it knows the SDK, it just does it.

Hell: the agent is now an actor inside your account with your permissions, calling APIs you can't easily see, against 300+ services where a single wrong delete-* is unrecoverable. Every community MCP server that "connects Claude to AWS" runs into the same three questions I keep hammering on: Is the credential scoped? Are side effects documented? Is there a trace when it acts? For production AWS, "it works on my laptop" is not good enough. You need governance.