AWS signin: Document OAuth 2.0 token exchange authorization for AWS MCP
Summary
Adds a 'Token exchange authorization' section describing use of the OAuth 2.0 Token Exchange Grant (RFC 8693) to exchange an OIDC identity token for a short-lived, service-scoped OAuth access token, including the required IAM permission signin:CreateOAuth2Token and a CLI example.
Security assessment
The added text documents an authentication/authorization flow (OIDC-to-OAuth token exchange) and the least-privilege IAM permission signin:CreateOAuth2Token, noting that IAM role permissions still govern access. It is security feature documentation rather than a fix for a specific vulnerability.
Evidence
+Token exchange authorization uses the OAuth 2.0 Token Exchange Grant (RFC 8693). It enables third-party applications to exchange an existing OpenID Connect (OIDC) identity token for a short-lived OAuth access token. This token is scoped to a supported AWS service and requires no AWS credentials.
Diff
diff --git a/signin/latest/userguide/aws-mcp-server.md b/signin/latest/userguide/aws-mcp-server.md index 6e231c8..9dd0eeb 100644 --- a//signin/latest/userguide/aws-mcp-server.md +++ b//signin/latest/userguide/aws-mcp-server.md @@ -152,0 +153,36 @@ The following example shows how to obtain an access token using the AWS CLI: +### Token exchange authorization + +Token exchange authorization uses the OAuth 2.0 Token Exchange Grant (RFC 8693). It enables third-party applications to exchange an existing OpenID Connect (OIDC) identity token for a short-lived OAuth access token. This token is scoped to a supported AWS service and requires no AWS credentials. + +The general workflow is: + + 1. The application obtains an OIDC token from its identity provider. + + 2. The application submits the token to the AWS Sign-In token exchange endpoint. + + 3. AWS validates the identity and IAM role permissions and issues a service-scoped OAuth access token. + + 4. The application uses the access token to access the supported AWS service. + + + + +The IAM role's permissions and applicable service-specific authorization controls continue to govern access. + +Required IAM permission: + + * `signin:CreateOAuth2Token` + + + + +The following example shows how to exchange an OIDC token to obtain access: + + + aws signin create-oauth2-token-with-token-exchange \ + --grant-type urn:ietf:params:oauth:grant-type:token-exchange \ + --subject-token "$OIDC_TOKEN" \ + --subject-token-type urn:ietf:params:oauth:token-type:jwt \ + --resource aws-mcp.amazonaws.com \ + --region us-east-1 +