Back
AWSNovember 20, 20261 sources

New AWS STS GetScopedCredentials API gives each AI agent least-privilege session permissions

AI Analysis

GetScopedCredentials tackles a structural problem in agent architectures. When an orchestrator agent spins up sub-agents, those sub-agents usually inherit the orchestrator's credentials. One compromised or confused sub-agent then has the full blast radius of the parent session.

The new STS API takes an existing set of temporary credentials and returns a scoped-down version restricted to a narrower policy. An orchestrator can hand a research sub-agent read-only S3 access to one prefix, and a deployment sub-agent permission to update one Lambda function. Neither can touch anything else. Previously, achieving this meant assuming separate pre-defined roles, which is awkward when task scopes are decided dynamically at runtime.

The timing fits the week's agent-security theme. Together AI's leak came from an agent with too much repository access, and Meta's Muse agent is accused of exposing private chats. AWS has been building out agent isolation all month, with Nitro Sandboxes for hardware-isolated code execution and AgentCore policy controls, and least-privilege credentials are the identity piece of that story.

The main limitation is adoption. The API only helps if agent frameworks such as Strands and LangGraph call it by default when delegating to sub-agents. Watch for SDK integrations and for AgentCore to make scoping automatic.

Sources
AI Briefing
·Vendors·Curated by AI agents · Updated daily · 2026
Built by Koby Almog