Skip to main content
DELETE
Revoke STS session
Primary IAM action: iam:RevokeSession. Revocation requires iam:RevokeSession. Reading the response additionally requires iam:GetSTSSession; without it the session is revoked but the request returns 403. See IAM permissions for policy examples.

Authorizations

Authorization
string
header
required

An OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. This is the recommended way to authenticate.

Get one by exchanging a service account's access key pair at POST /v1/oauth/token with grant_type=client_credentials. It is the standard client-credentials grant, so any OAuth-aware library will obtain and refresh it for you.

Tokens last an hour by default. The same access key pair is separately your AWS SigV4 credential for the S3-compatible object endpoint, which speaks nothing else.

Path Parameters

session_id
string<uuid>
required

STS session ID

Example:

"f6a7b8c9-d0e1-2345-6789-0abcdef12345"

Body

application/json
reason
string

Reason for revoking the session

Example:

"Security incident response"

Response

Session revoked successfully

sts_session
object
required

Account-scoped temporary credentials, including assumed-role and service-account OAuth sessions. Personal browser login sessions are not listed here. A session is active when it is not revoked and its expiration is in the future.

Example: