STS IAM actions (sts) and their access levels
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
STS has 16 IAM actions under the prefix sts in AWS's service authorization reference fetched on 16 Nov 2026: 0 List, 4 Read, 10 Write, 0 Permissions management and 2 Tagging. A wildcard sts:* in an Allow statement grants every one of them, and the tables below list each action with its resource types.
Open the workbench ยท All 40 services
Write: 10 actions
| Action | Resource types | Condition keys |
|---|---|---|
sts:AssumeRole | role | 19 |
sts:AssumeRoleWithSAML | role | 37 |
sts:AssumeRoleWithWebIdentity | role | 89 |
sts:AssumeRoot | root-user | 1 |
sts:DecodeAuthorizationMessage | * | 0 |
sts:GetDelegatedAccessToken | * | 0 |
sts:GetFederationToken | federated-user | 2 |
sts:GetWebIdentityToken | * | 5 |
sts:SetContext | role, self-session | 2 |
sts:SetSourceIdentity | role | 1 |
Tagging: 2 actions
| Action | Resource types | Condition keys |
|---|---|---|
sts:TagGetWebIdentityToken | * | 2 |
sts:TagSession | role | 4 |
Read: 4 actions
| Action | Resource types | Condition keys |
|---|---|---|
sts:GetAccessKeyInfo | * | 0 |
sts:GetCallerIdentity | * | 0 |
sts:GetServiceBearerToken | * | 2 |
sts:GetSessionToken | * | 0 |
Service condition keys: 131
accounts.google.com:aud, accounts.google.com:google/organization_number, accounts.google.com:oaud, accounts.google.com:sub, agent.${Domain}.buildkite.dev:build_branch, agent.${Domain}.buildkite.dev:cluster_id, agent.${Domain}.buildkite.dev:cluster_name, agent.${Domain}.buildkite.dev:organization_id, agent.${Domain}.buildkite.dev:organization_slug, agent.${Domain}.buildkite.dev:pipeline_id, agent.${Domain}.buildkite.dev:pipeline_slug, agent.${Domain}.buildkite.site:build_branch, agent.${Domain}.buildkite.site:cluster_id, agent.${Domain}.buildkite.site:cluster_name, agent.${Domain}.buildkite.site:organization_id, agent.${Domain}.buildkite.site:organization_slug, agent.${Domain}.buildkite.site:pipeline_id, agent.${Domain}.buildkite.site:pipeline_slug, agent.buildkite.com:build_branch, agent.buildkite.com:cluster_id, agent.buildkite.com:cluster_name, agent.buildkite.com:organization_id, agent.buildkite.com:organization_slug, agent.buildkite.com:pipeline_id, agent.buildkite.com:pipeline_slug, aws:RequestTag/${TagKey}, aws:ResourceTag/${TagKey}, aws:TagKeys, cognito-identity.amazonaws.com:amr, cognito-identity.amazonaws.com:aud, cognito-identity.amazonaws.com:sub, github.com/enterprises/${EnterpriseName}:actor, github.com/enterprises/${EnterpriseName}:actor_id, github.com/enterprises/${EnterpriseName}:enterprise_id, github.com/enterprises/${EnterpriseName}:environment, github.com/enterprises/${EnterpriseName}:job_workflow_ref, github.com/enterprises/${EnterpriseName}:ref, github.com/enterprises/${EnterpriseName}:repository, github.com/enterprises/${EnterpriseName}:repository_id, github.com/enterprises/${EnterpriseName}:repository_owner_id, github.com/enterprises/${EnterpriseName}:workflow, gitlab.com:namespace_id, gitlab.com:pipeline_source, gitlab.com:project_id, gitlab.com:ref_protected, gitlab.com:runner_environment, gitlab.com:user_access_level, gitlab.com:user_email, gitlab.com:user_id, gitlab.com:user_login, graph.facebook.com:app_id, graph.facebook.com:id, iam:ResourceTag/${TagKey}, idcs-${OciUniqueIdentifier}.identity.oraclecloud.com:rpst_id, oidc.circleci.com/org/${OrgId}:oidc.circleci.com/project-id, saml:aud, saml:cn, saml:commonName, saml:doc, saml:eduorghomepageuri, and 71 more in the dataset
Related pages
Sources
- AWS Service Authorization Reference, programmatic access (fetched 16 Nov 2026), read 16 Nov 2026
- STS service reference (JSON), read 16 Nov 2026
Last reviewed 16 Nov 2026.