All integrationsIdentity & Access
Amazon STS
Issue and inspect temporary AWS credentials through the Security Token Service: identify the connected principal and the owner of any access key, issue a session token, a federation token, or an assumed role, decode an access-denied error, and issue a signed JWT for outbound identity federation.
- actions
- 7
Actions
Steps a workflow can run in Amazon STS.
- Get caller identityShow which AWS account and IAM principal the connection acts as. Needs no permissions, so it also tests the connection.
- Get access key infoFind the AWS account that owns an access key ID, from any account. It does not say whether the key is still active.
- Get session tokenIssue temporary credentials with the connected user's own permissions, optionally MFA-authenticated. The result contains a secret access key and session token: anyone who can see this workflow's run history can use them until they expire.
- Get federation tokenIssue temporary credentials for a named federated user, limited by a session policy you pass. The result contains a secret access key and session token: anyone who can see this workflow's run history can use them until they expire.
- Assume roleIssue temporary credentials for an IAM role whose trust policy trusts the connected user or account. The result contains a secret access key and session token: anyone who can see this workflow's run history can use them until they expire.
- Decode authorization messageDecode the 'Encoded authorization failure message' from an AWS access-denied error, to see which policy denied what.
- Get web identity tokenIssue a signed JWT that proves this AWS identity to an external service (outbound identity federation). The token is a credential: anyone who can see this workflow's run history can present it until it expires.
No actions match that.
Automate Amazon STS with Lodol.
Connect Amazon STS, then hand Lodol the job in Slack, Claude or ChatGPT.
Free plan, no credit card