create_o_auth2_token_with_iam
async
¶
create_o_auth2_token_with_iam(
grant_type: ClientCredentialsGrantType,
resource: str,
*,
config_overrides: Optional[AsyncSigninClientConfig] = None,
) -> CreateOAuth2TokenWithIAMResponse
Grants permission to exchange client credentials for an OAuth 2.0 access token scoped to a resource that can be used to access AWS services from applications
Parameters:
-
grant_type(ClientCredentialsGrantType) –OAuth 2.0 grant type. Must be "client_credentials".
-
resource(str) –The OAuth resource for which the access token is requested. Example: "aws-mcp.amazonaws.com".
Raises:
-
AccessDeniedException–Error thrown for access denied scenarios with flexible HTTP status mapping Runtime HTTP Status Code Mapping: - HTTP 401 (Unauthorized): TOKEN_EXPIRED, AUTHCODE_EXPIRED - HTTP 403 (Forbidden): USER_CREDENTIALS_CHANGED, INSUFFICIENT_PERMISSIONS The specific HTTP status code is determined at runtime based on the error enum value. Consumers should use the error field to determine the specific access denial reason.
-
InternalServerException–Error thrown when an internal server error occurs HTTP Status Code: 500 Internal Server Error Used for unexpected server-side errors that prevent request processing.
-
TooManyRequestsError–Error thrown when rate limit is exceeded HTTP Status Code: 429 Too Many Requests Possible OAuth2ErrorCode values: - INVALID_REQUEST: Rate limiting, too many requests, abuse prevention Possible causes: - Too many token requests from the same client - Rate limiting based on client_id or IP address - Abuse prevention mechanisms triggered - Service protection against excessive token generation
-
ValidationException–Error thrown when request validation fails HTTP Status Code: 400 Bad Request Used for request validation errors such as malformed parameters, missing required fields, or invalid parameter values.
-
UnknownServiceError–The service returned an error code this client does not model.