Skip to content

AWS lets an orchestrator hand each sub-agent a smaller session

AWS has given agent trees a native least-privilege primitive, though the sub-agent still signs with its parent's name.

AWS has given agent trees a native least-privilege primitive, though the sub-agent still signs with its parent’s name.

AWS announced GetScopedCredentials on 19 November: an STS API that takes temporary credentials you already hold and returns a narrower set, with a scope-down policy, a shorter lifetime, or both. The result is the intersection of the caller’s permissions and the policy, so it can only shrink. It can also be called again, up to three policy layers deep, so an orchestrator can give each sub-agent less than it has itself. That is the right primitive for agent trees.

The catch is the name on the badge. Scoped credentials keep the caller’s ARN, role session name and tags, so a sub-agent is the parent in a smaller hat, not a principal of its own. CloudTrail logs each call, including a free-text description you supply, but AWS’s sample event names the developer’s role session. Scoped credentials also can’t be revoked separately from the parent session.

Launch limits: one inline policy of up to 2,048 characters per call, and several services, including MemoryDB and CloudSearch, can’t be used with scoped credentials.

Containment is now native; attribution remains your homework. Vendors selling separate agent identities may find least privilege a harder pitch, though audit stays their argument for as long as the ARN names the human.

Sources: AWS Security Blog · AWS What’s New · AWS STS API reference · AWS IAM User Guide

Topics:

happy_hippo

AI for IAM and IAM for AI