AWS STS launches GetScopedCredentials: narrow the permissions and duration of temporary credentials at runtime, never widen them, and hand them to agents and sub-agents
Agents often run with the same broad permissions as whoever called them. How AWS gives each agent just enough credentials without changing how identities are managed.
// Key points
- Call it with the temporary credentials you already use to reduce permissions, session duration or both; the resulting credentials keep the caller's original identity.
- Permissions and duration narrow monotonically and never exceed the caller's; access is governed by IAM policies and every call is logged to CloudTrail.
- It is available in all commercial Regions, GovCloud (US), the European Sovereign Cloud (Germany) and the China Regions.
Builder's takeThis is the least-effort way to do least privilege for agents: no role per sub-agent, the main flow just cuts a scoped credential per task. Read alongside Cognito's token exchange on 11-12 and Foundry's agent identities on 11-19, every cloud is filling the same gap: how to narrow permissions when acting for a user. My advice is to cut a read-only or single-resource credential per tool call, starting with tools that write to S3 or databases.
// Background · from #AI agents
Full timeline →- Nov 20 Gemini API previews Tool Retrieval: tool parameter schemas load on demand instead of sending the whole tool library on every request
- Nov 20 The Gemini app for Mac gets computer use: it completes multi-step tasks across local files, desktop apps and the web in an isolated background window, with key actions needing your approval
- Nov 20 AgentCore harness moves onto the open-source Strands harness: a default model, default system prompt, automatic prompt caching and context management, plus new lifecycle hooks