openapi: 3.0.0
info:
version: 2014-06-30
x-release: v4
title: 'Amazon Cognito Identity #X Amz Target=AWSCognitoIdentityProviderService.AddCustomAttributes #X Amz Target=AWSCognitoIdentityProviderService.AddCustomAttributes #X Amz Target=AWSCognitoIdentityProviderService.RespondToAuthChallenge API'
description: <fullname>Amazon Cognito Federated Identities</fullname> <p>Amazon Cognito Federated Identities is a web service that delivers scoped temporary credentials to mobile devices and other untrusted environments. It uniquely identifies a device and supplies the user with a consistent identity over the lifetime of an application.</p> <p>Using Amazon Cognito Federated Identities, you can enable authentication with one or more third-party identity providers (Facebook, Google, or Login with Amazon) or an Amazon Cognito user pool, and you can also choose to support unauthenticated access from your app. Cognito delivers a unique identifier for each user and acts as an OpenID token provider trusted by AWS Security Token Service (STS) to access temporary, limited-privilege AWS credentials.</p> <p>For a description of the authentication flow from the Amazon Cognito Developer Guide see <a href="https://docs.aws.amazon.com/cognito/latest/developerguide/authentication-flow.html">Authentication Flow</a>.</p> <p>For more information see <a href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-identity.html">Amazon Cognito Federated Identities</a>.</p>
x-logo:
url: https://api.apis.guru/v2/cache/logo/https_twitter.com_awscloud_profile_image.png
backgroundColor: '#FFFFFF'
termsOfService: https://aws.amazon.com/service-terms/
contact:
name: Mike Ralphson
email: mike.ralphson@gmail.com
url: https://github.com/mermade/aws2openapi
x-twitter: PermittedSoc
license:
name: Apache 2.0 License
url: http://www.apache.org/licenses/
x-providerName: amazonaws.com
x-serviceName: cognito-identity
x-origin:
- contentType: application/json
url: https://raw.githubusercontent.com/aws/aws-sdk-js/master/apis/cognito-identity-2014-06-30.normal.json
converter:
url: https://github.com/mermade/aws2openapi
version: 1.0.0
x-apisguru-driver: external
x-apiClientRegistration:
url: https://portal.aws.amazon.com/gp/aws/developer/registration/index.html?nc2=h_ct
x-apisguru-categories:
- cloud
x-preferred: true
servers:
- url: http://cognito-identity.{region}.amazonaws.com
variables:
region:
description: The AWS region
enum:
- us-east-1
- us-east-2
- us-west-1
- us-west-2
- us-gov-west-1
- us-gov-east-1
- ca-central-1
- eu-north-1
- eu-west-1
- eu-west-2
- eu-west-3
- eu-central-1
- eu-south-1
- af-south-1
- ap-northeast-1
- ap-northeast-2
- ap-northeast-3
- ap-southeast-1
- ap-southeast-2
- ap-east-1
- ap-south-1
- sa-east-1
- me-south-1
default: us-east-1
description: The Amazon Cognito Identity multi-region endpoint
- url: https://cognito-identity.{region}.amazonaws.com
variables:
region:
description: The AWS region
enum:
- us-east-1
- us-east-2
- us-west-1
- us-west-2
- us-gov-west-1
- us-gov-east-1
- ca-central-1
- eu-north-1
- eu-west-1
- eu-west-2
- eu-west-3
- eu-central-1
- eu-south-1
- af-south-1
- ap-northeast-1
- ap-northeast-2
- ap-northeast-3
- ap-southeast-1
- ap-southeast-2
- ap-east-1
- ap-south-1
- sa-east-1
- me-south-1
default: us-east-1
description: The Amazon Cognito Identity multi-region endpoint
- url: http://cognito-identity.{region}.amazonaws.com.cn
variables:
region:
description: The AWS region
enum:
- cn-north-1
- cn-northwest-1
default: cn-north-1
description: The Amazon Cognito Identity endpoint for China (Beijing) and China (Ningxia)
- url: https://cognito-identity.{region}.amazonaws.com.cn
variables:
region:
description: The AWS region
enum:
- cn-north-1
- cn-northwest-1
default: cn-north-1
description: The Amazon Cognito Identity endpoint for China (Beijing) and China (Ningxia)
security:
- hmac: []
tags:
- name: '#X Amz Target=AWSCognitoIdentityProviderService.RespondToAuthChallenge'
paths:
/#X-Amz-Target=AWSCognitoIdentityProviderService.RespondToAuthChallenge:
parameters:
- $ref: '#/components/parameters/X-Amz-Content-Sha256'
- $ref: '#/components/parameters/X-Amz-Date'
- $ref: '#/components/parameters/X-Amz-Algorithm'
- $ref: '#/components/parameters/X-Amz-Credential'
- $ref: '#/components/parameters/X-Amz-Security-Token'
- $ref: '#/components/parameters/X-Amz-Signature'
- $ref: '#/components/parameters/X-Amz-SignedHeaders'
post:
operationId: RespondToAuthChallenge
description: <p>Responds to the authentication challenge.</p> <note> <p>This action might generate an SMS text message. Starting June 1, 2021, US telecom carriers require you to register an origination phone number before you can send SMS messages to US phone numbers. If you use SMS text messages in Amazon Cognito, you must register a phone number with <a href="https://console.aws.amazon.com/pinpoint/home/">Amazon Pinpoint</a>. Amazon Cognito uses the registered number automatically. Otherwise, Amazon Cognito users who must receive SMS messages might not be able to sign up, activate their accounts, or sign in.</p> <p>If you have never used SMS text messages with Amazon Cognito or any other Amazon Web Service, Amazon Simple Notification Service might place your account in the SMS sandbox. In <i> <a href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox mode</a> </i>, you can send messages only to verified phone numbers. After you test your app while in the sandbox environment, you can move out of the sandbox and into production. For more information, see <a href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html"> SMS message settings for Amazon Cognito user pools</a> in the <i>Amazon Cognito Developer Guide</i>.</p> </note>
responses:
'200':
description: Success
content:
application/json:
schema:
$ref: '#/components/schemas/RespondToAuthChallengeResponse'
examples:
RespondToAuthChallenge200Example:
summary: Default RespondToAuthChallenge 200 response
x-microcks-default: true
value:
ChallengeName: my-user-pool
Session: example-value
ChallengeParameters: example-value
AuthenticationResult: example-value
'480':
description: ResourceNotFoundException
content:
application/json:
schema:
$ref: '#/components/schemas/ResourceNotFoundException'
examples:
RespondToAuthChallenge480Example:
summary: Default RespondToAuthChallenge 480 response
x-microcks-default: true
value: example
'481':
description: InvalidParameterException
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidParameterException'
examples:
RespondToAuthChallenge481Example:
summary: Default RespondToAuthChallenge 481 response
x-microcks-default: true
value: example
'482':
description: NotAuthorizedException
content:
application/json:
schema:
$ref: '#/components/schemas/NotAuthorizedException'
examples:
RespondToAuthChallenge482Example:
summary: Default RespondToAuthChallenge 482 response
x-microcks-default: true
value: example
'483':
description: CodeMismatchException
content:
application/json:
schema:
$ref: '#/components/schemas/CodeMismatchException'
examples:
RespondToAuthChallenge483Example:
summary: Default RespondToAuthChallenge 483 response
x-microcks-default: true
value: example
'484':
description: ExpiredCodeException
content:
application/json:
schema:
$ref: '#/components/schemas/ExpiredCodeException'
examples:
RespondToAuthChallenge484Example:
summary: Default RespondToAuthChallenge 484 response
x-microcks-default: true
value: example
'485':
description: UnexpectedLambdaException
content:
application/json:
schema:
$ref: '#/components/schemas/UnexpectedLambdaException'
examples:
RespondToAuthChallenge485Example:
summary: Default RespondToAuthChallenge 485 response
x-microcks-default: true
value: example
'486':
description: UserLambdaValidationException
content:
application/json:
schema:
$ref: '#/components/schemas/UserLambdaValidationException'
examples:
RespondToAuthChallenge486Example:
summary: Default RespondToAuthChallenge 486 response
x-microcks-default: true
value: example
'487':
description: InvalidPasswordException
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidPasswordException'
examples:
RespondToAuthChallenge487Example:
summary: Default RespondToAuthChallenge 487 response
x-microcks-default: true
value: example
'488':
description: InvalidLambdaResponseException
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidLambdaResponseException'
examples:
RespondToAuthChallenge488Example:
summary: Default RespondToAuthChallenge 488 response
x-microcks-default: true
value: example
'489':
description: TooManyRequestsException
content:
application/json:
schema:
$ref: '#/components/schemas/TooManyRequestsException'
examples:
RespondToAuthChallenge489Example:
summary: Default RespondToAuthChallenge 489 response
x-microcks-default: true
value: example
'490':
description: InvalidUserPoolConfigurationException
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidUserPoolConfigurationException'
examples:
RespondToAuthChallenge490Example:
summary: Default RespondToAuthChallenge 490 response
x-microcks-default: true
value: example
'491':
description: MFAMethodNotFoundException
content:
application/json:
schema:
$ref: '#/components/schemas/MFAMethodNotFoundException'
examples:
RespondToAuthChallenge491Example:
summary: Default RespondToAuthChallenge 491 response
x-microcks-default: true
value: example
'492':
description: PasswordResetRequiredException
content:
application/json:
schema:
$ref: '#/components/schemas/PasswordResetRequiredException'
examples:
RespondToAuthChallenge492Example:
summary: Default RespondToAuthChallenge 492 response
x-microcks-default: true
value: example
'493':
description: UserNotFoundException
content:
application/json:
schema:
$ref: '#/components/schemas/UserNotFoundException'
examples:
RespondToAuthChallenge493Example:
summary: Default RespondToAuthChallenge 493 response
x-microcks-default: true
value: example
'494':
description: UserNotConfirmedException
content:
application/json:
schema:
$ref: '#/components/schemas/UserNotConfirmedException'
examples:
RespondToAuthChallenge494Example:
summary: Default RespondToAuthChallenge 494 response
x-microcks-default: true
value: example
'495':
description: InvalidSmsRoleAccessPolicyException
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidSmsRoleAccessPolicyException'
examples:
RespondToAuthChallenge495Example:
summary: Default RespondToAuthChallenge 495 response
x-microcks-default: true
value: example
'496':
description: InvalidSmsRoleTrustRelationshipException
content:
application/json:
schema:
$ref: '#/components/schemas/InvalidSmsRoleTrustRelationshipException'
examples:
RespondToAuthChallenge496Example:
summary: Default RespondToAuthChallenge 496 response
x-microcks-default: true
value: example
'497':
description: AliasExistsException
content:
application/json:
schema:
$ref: '#/components/schemas/AliasExistsException'
examples:
RespondToAuthChallenge497Example:
summary: Default RespondToAuthChallenge 497 response
x-microcks-default: true
value: example
'498':
description: InternalErrorException
content:
application/json:
schema:
$ref: '#/components/schemas/InternalErrorException'
examples:
RespondToAuthChallenge498Example:
summary: Default RespondToAuthChallenge 498 response
x-microcks-default: true
value: example
'499':
description: SoftwareTokenMFANotFoundException
content:
application/json:
schema:
$ref: '#/components/schemas/SoftwareTokenMFANotFoundException'
examples:
RespondToAuthChallenge499Example:
summary: Default RespondToAuthChallenge 499 response
x-microcks-default: true
value: example
'500':
description: ForbiddenException
content:
application/json:
schema:
$ref: '#/components/schemas/ForbiddenException'
examples:
RespondToAuthChallenge500Example:
summary: Default RespondToAuthChallenge 500 response
x-microcks-default: true
value: example
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/RespondToAuthChallengeRequest'
examples:
RespondToAuthChallengeRequestExample:
summary: Default RespondToAuthChallenge request
x-microcks-default: true
value:
ClientId: us-east-1_AbCdEfGhI
ChallengeName: my-user-pool
Session: example-value
ChallengeResponses: example-value
AnalyticsMetadata: example-value
UserContextData: example-value
ClientMetadata: example-value
parameters:
- name: X-Amz-Target
in: header
required: true
schema:
type: string
enum:
- AWSCognitoIdentityProviderService.RespondToAuthChallenge
summary: Amazon Cognito Respond to Auth Challenge
x-microcks-operation:
delay: 0
dispatcher: FALLBACK
tags:
- '#X Amz Target=AWSCognitoIdentityProviderService.RespondToAuthChallenge'
components:
schemas:
ResourceNotFoundException: {}
ChallengeParametersType:
type: object
additionalProperties:
$ref: '#/components/schemas/StringType'
InvalidSmsRoleAccessPolicyException: {}
SessionType:
type: string
minLength: 20
maxLength: 2048
UserNotFoundException: {}
InvalidSmsRoleTrustRelationshipException: {}
InvalidPasswordException: {}
UnexpectedLambdaException: {}
ExpiredCodeException: {}
CodeMismatchException: {}
UserNotConfirmedException: {}
InvalidParameterException: {}
AuthenticationResultType:
type: object
properties:
AccessToken:
allOf:
- $ref: '#/components/schemas/TokenModelType'
- description: A valid access token that Amazon Cognito issued to the user who you want to authenticate.
ExpiresIn:
allOf:
- $ref: '#/components/schemas/IntegerType'
- description: The expiration period of the authentication result in seconds.
TokenType:
allOf:
- $ref: '#/components/schemas/StringType'
- description: The token type.
RefreshToken:
allOf:
- $ref: '#/components/schemas/TokenModelType'
- description: The refresh token.
IdToken:
allOf:
- $ref: '#/components/schemas/TokenModelType'
- description: The ID token.
NewDeviceMetadata:
allOf:
- $ref: '#/components/schemas/NewDeviceMetadataType'
- description: The new device metadata from an authentication result.
description: The authentication result.
UserContextDataType:
type: object
properties:
IpAddress:
allOf:
- $ref: '#/components/schemas/StringType'
- description: The source IP address of your user's device.
EncodedData:
allOf:
- $ref: '#/components/schemas/StringType'
- description: Encoded device-fingerprint details that your app collected with the Amazon Cognito context data collection library. For more information, see <a href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pool-settings-adaptive-authentication.html#user-pool-settings-adaptive-authentication-device-fingerprint">Adding user device and session data to API requests</a>.
description: Contextual data, such as the user's device fingerprint, IP address, or location, used for evaluating the risk of an unexpected event by Amazon Cognito advanced security.
RespondToAuthChallengeResponse:
type: object
properties:
ChallengeName:
allOf:
- $ref: '#/components/schemas/ChallengeNameType'
- description: The challenge name. For more information, see <a href="https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_InitiateAuth.html">InitiateAuth</a>.
Session:
allOf:
- $ref: '#/components/schemas/SessionType'
- description: The session that should be passed both ways in challenge-response calls to the service. If the caller must pass another challenge, they return a session with other challenge parameters. This session should be passed as it is to the next <code>RespondToAuthChallenge</code> API call.
ChallengeParameters:
allOf:
- $ref: '#/components/schemas/ChallengeParametersType'
- description: The challenge parameters. For more information, see <a href="https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_InitiateAuth.html">InitiateAuth</a>.
AuthenticationResult:
allOf:
- $ref: '#/components/schemas/AuthenticationResultType'
- description: The result returned by the server in response to the request to respond to the authentication challenge.
description: The response to respond to the authentication challenge.
TooManyRequestsException: {}
InternalErrorException: {}
ClientMetadataType:
type: object
additionalProperties:
$ref: '#/components/schemas/StringType'
StringType:
type: string
SoftwareTokenMFANotFoundException: {}
InvalidLambdaResponseException: {}
IntegerType:
type: integer
NotAuthorizedException: {}
AliasExistsException: {}
ChallengeResponsesType:
type: object
additionalProperties:
$ref: '#/components/schemas/StringType'
ClientIdType:
type: string
pattern: '[\w+]+'
minLength: 1
maxLength: 128
format: password
PasswordResetRequiredException: {}
AnalyticsMetadataType:
type: object
properties:
AnalyticsEndpointId:
allOf:
- $ref: '#/components/schemas/StringType'
- description: The endpoint ID.
description: <p>An Amazon Pinpoint analytics endpoint.</p> <p>An endpoint uniquely identifies a mobile device, email address, or phone number that can receive messages from Amazon Pinpoint analytics. For more information about Amazon Web Services Regions that can contain Amazon Pinpoint resources for use with Amazon Cognito user pools, see <a href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-pinpoint-integration.html">Using Amazon Pinpoint analytics with Amazon Cognito user pools</a>.</p>
TokenModelType:
type: string
pattern: '[A-Za-z0-9-_=.]+'
format: password
InvalidUserPoolConfigurationException: {}
NewDeviceMetadataType:
type: object
properties:
DeviceKey:
allOf:
- $ref: '#/components/schemas/DeviceKeyType'
- description: The device key.
DeviceGroupKey:
allOf:
- $ref: '#/components/schemas/StringType'
- description: The device group key.
description: The new device metadata type.
RespondToAuthChallengeRequest:
type: object
required:
- ClientId
- ChallengeName
title: RespondToAuthChallengeRequest
properties:
ClientId:
allOf:
- $ref: '#/components/schemas/ClientIdType'
- description: The app client ID.
ChallengeName:
allOf:
- $ref: '#/components/schemas/ChallengeNameType'
- description: <p>The challenge name. For more information, see <a href="https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_InitiateAuth.html">InitiateAuth</a>.</p> <p> <code>ADMIN_NO_SRP_AUTH</code> isn't a valid value.</p>
Session:
allOf:
- $ref: '#/components/schemas/SessionType'
- description: The session that should be passed both ways in challenge-response calls to the service. If <code>InitiateAuth</code> or <code>RespondToAuthChallenge</code> API call determines that the caller must pass another challenge, they return a session with other challenge parameters. This session should be passed as it is to the next <code>RespondToAuthChallenge</code> API call.
ChallengeResponses:
allOf:
- $ref: '#/components/schemas/ChallengeResponsesType'
- description: '<p>The challenge responses. These are inputs corresponding to the value of <code>ChallengeName</code>, for example:</p> <note> <p> <code>SECRET_HASH</code> (if app client is configured with client secret) applies to all of the inputs that follow (including <code>SOFTWARE_TOKEN_MFA</code>).</p> </note> <ul> <li> <p> <code>SMS_MFA</code>: <code>SMS_MFA_CODE</code>, <code>USERNAME</code>.</p> </li> <li> <p> <code>PASSWORD_VERIFIER</code>: <code>PASSWORD_CLAIM_SIGNATURE</code>, <code>PASSWORD_CLAIM_SECRET_BLOCK</code>, <code>TIMESTAMP</code>, <code>USERNAME</code>.</p> <note> <p> <code>PASSWORD_VERIFIER</code> requires <code>DEVICE_KEY</code> when you sign in with a remembered device.</p> </note> </li> <li> <p> <code>NEW_PASSWORD_REQUIRED</code>: <code>NEW_PASSWORD</code>, <code>USERNAME</code>, <code>SECRET_HASH</code> (if app client is configured with client secret). To set any required attributes that Amazon Cognito returned as <code>requiredAttributes</code> in the <code>InitiateAuth</code> response, add a <code>userAttributes.<i>attributename</i> </code> parameter. This parameter can also set values for writable attributes that aren''t required by your user pool.</p> <note> <p>In a <code>NEW_PASSWORD_REQUIRED</code> challenge response, you can''t modify a required attribute that already has a value. In <code>RespondToAuthChallenge</code>, set a value for any keys that Amazon Cognito returned in the <code>requiredAttributes</code> parameter, then use the <code>UpdateUserAttributes</code> API operation to modify the value of any additional attributes.</p> </note> </li> <li> <p> <code>SOFTWARE_TOKEN_MFA</code>: <code>USERNAME</code> and <code>SOFTWARE_TOKEN_MFA_CODE</code> are required attributes.</p> </li> <li> <p> <code>DEVICE_SRP_AUTH</code> requires <code>USERNAME</code>, <code>DEVICE_KEY</code>, <code>SRP_A</code> (and <code>SECRET_HASH</code>).</p> </li> <li> <p> <code>DEVICE_PASSWORD_VERIFIER</code> requires everything that <code>PASSWORD_VERIFIER</code> requires, plus <code>DEVICE_KEY</code>.</p> </li> <li> <p> <code>MFA_SETUP</code> requires <code>USERNAME</code>, plus you must use the session value returned by <code>VerifySoftwareToken</code> in the <code>Session</code> parameter.</p> </li> </ul>'
AnalyticsMetadata:
allOf:
- $ref: '#/components/schemas/AnalyticsMetadataType'
- description: The Amazon Pinpoint analytics metadata that contributes to your metrics for <code>RespondToAuthChallenge</code> calls.
UserContextData:
allOf:
- $ref: '#/components/schemas/UserContextDataType'
- description: Contextual data about your user session, such as the device fingerprint, IP address, or location. Amazon Cognito advanced security evaluates the risk of an authentication event based on the context that your app generates and passes to Amazon Cognito when it makes API requests.
ClientMetadata:
allOf:
- $ref: '#/components/schemas/ClientMetadataType'
- description: '<p>A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.</p> <p>You create custom workflows by assigning Lambda functions to user pool triggers. When you use the RespondToAuthChallenge API action, Amazon Cognito invokes any functions that are assigned to the following triggers: <i>post authentication</i>, <i>pre token generation</i>, <i>define auth challenge</i>, <i>create auth challenge</i>, and <i>verify auth challenge</i>. When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a <code>clientMetadata</code> attribute, which provides the data that you assigned to the ClientMetadata parameter in your RespondToAuthChallenge request. In your function code in Lambda, you can process the <code>clientMetadata</code> value to enhance your workflow for your specific needs.</p> <p>For more information, see <a href="https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-working-with-aws-lambda-triggers.html"> Customizing user pool Workflows with Lambda Triggers</a> in the <i>Amazon Cognito Developer Guide</i>.</p> <note> <p>When you use the ClientMetadata parameter, remember that Amazon Cognito won''t do the following:</p> <ul> <li> <p>Store the ClientMetadata value. This data is available only to Lambda triggers that are assigned to a user pool to support custom workflows. If your user pool configuration doesn''t include triggers, the ClientMetadata parameter serves no purpose.</p> </li> <li> <p>Validate the ClientMetadata value.</p> </li> <li> <p>Encrypt the ClientMetadata value. Don''t use Amazon Cognito to provide sensitive information.</p> </li> </ul> </note>'
description: The request to respond to an authentication challenge.
UserLambdaValidationException: {}
MFAMethodNotFoundException: {}
ForbiddenException: {}
ChallengeNameType:
type: string
enum:
- SMS_MFA
- SOFTWARE_TOKEN_MFA
- SELECT_MFA_TYPE
- MFA_SETUP
- PASSWORD_VERIFIER
- CUSTOM_CHALLENGE
- DEVICE_SRP_AUTH
- DEVICE_PASSWORD_VERIFIER
- ADMIN_NO_SRP_AUTH
- NEW_PASSWORD_REQUIRED
DeviceKeyType:
type: string
pattern: '[\w-]+_[0-9a-f-]+'
minLength: 1
maxLength: 55
parameters:
X-Amz-Credential:
name: X-Amz-Credential
in: header
schema:
type: string
required: false
X-Amz-Date:
name: X-Amz-Date
in: header
schema:
type: string
required: false
X-Amz-Signature:
name: X-Amz-Signature
in: header
schema:
type: string
required: false
X-Amz-Algorithm:
name: X-Amz-Algorithm
in: header
schema:
type: string
required: false
X-Amz-Security-Token:
name: X-Amz-Security-Token
in: header
schema:
type: string
required: false
X-Amz-SignedHeaders:
name: X-Amz-SignedHeaders
in: header
schema:
type: string
required: false
X-Amz-Content-Sha256:
name: X-Amz-Content-Sha256
in: header
schema:
type: string
required: false
securitySchemes:
hmac:
type: apiKey
name: Authorization
in: header
description: Amazon Signature authorization v4
x-amazon-apigateway-authtype: awsSigv4
externalDocs:
description: Amazon Web Services documentation
url: https://docs.aws.amazon.com/cognito-identity/
x-hasEquivalentPaths: true