ai-devtools —

Scope down permissions of existing sessions using AWS STS GetScopedCredentials

When you build AI agents, you often want each agent or sub-agent to have only the permissions its tasks require, rather than the full permissions of the session that started it.

Scope down permissions of existing sessions using AWS STS GetScopedCredentials

GetScopedCredentials is a new AWS Security Token Service (AWS STS) API that you can use to scope down the permissions of existing temporary security credentials. You can assign each agent, sub-agent, or process its own set of credentials that keep the caller’s AWS Identity and Access Management (IAM) identity but carry reduced permissions, a shorter session duration, or both.

You can call GetScopedCredentials with the temporary security credentials you already use, such as those from aws login, an Amazon Elastic Compute Cloud (Amazon EC2) instance profile, or an AWS Lambda function. In each call, you pass a scope down policy, a shorter session duration, or both.

A scope down policy is an inline policy that describes the maximum permissions for the new credentials. The resulting permissions are the intersection of your session’s effective permissions and the scope down policy, so they can only be reduced. Similarly, the session duration you request can’t exceed the remaining duration of the calling session.

Earlier coverage

Reported by aws.amazon.com.

ai-devtoolssecuritycloud

Related coverage

Elsewhere in this edition