Using the Amazon Cognito user pools API, you can create a user pool to manage directories and users. You can authenticate a user to obtain tokens related to user identity and access policies.

This API reference provides information about user pools in Amazon Cognito user pools.

For more information, see the Amazon Cognito Documentation.

Adds additional user attributes to the user pool schema.

Adds the specified user to the specified group.

Calling this action requires developer credentials.

Confirms user registration as an admin without using a confirmation code. Works on any user.

Calling this action requires developer credentials.

Creates a new user in the specified user pool.

If MessageAction isn\'t set, the default is to send a welcome message via email or phone (SMS).

This message is based on a template that you configured in your call to create or update a user pool. This template includes your custom sign-up instructions and placeholders for user name and temporary password.

Alternatively, you can call AdminCreateUser with SUPPRESS for the MessageAction parameter, and Amazon Cognito won\'t send any email.

In either case, the user will be in the FORCE_CHANGE_PASSWORD state until they sign in and change their password.

AdminCreateUser requires developer credentials.

Deletes a user as an administrator. Works on any user.

Calling this action requires developer credentials.

Deletes the user attributes in a user pool as an administrator. Works on any user.

Calling this action requires developer credentials.

Prevents the user from signing in with the specified external (SAML or social) identity provider (IdP). If the user that you want to deactivate is a Amazon Cognito user pools native username + password user, they can\'t use their password to sign in. If the user to deactivate is a linked external IdP user, any link between that user and an existing user is removed. When the external user signs in again, and the user is no longer attached to the previously linked DestinationUser, the user must create a new user account. See AdminLinkProviderForUser.

This action is enabled only for admin access and requires developer credentials.

The ProviderName must match the value specified when creating an IdP for the pool.

To deactivate a native username + password user, the ProviderName value must be Cognito and the ProviderAttributeName must be Cognito_Subject. The ProviderAttributeValue must be the name that is used in the user pool for the user.

The ProviderAttributeName must always be Cognito_Subject for social IdPs. The ProviderAttributeValue must always be the exact subject that was used when the user was originally linked as a source user.

For de-linking a SAML identity, there are two scenarios. If the linked identity has not yet been used to sign in, the ProviderAttributeName and ProviderAttributeValue must be the same values that were used for the SourceUser when the identities were originally linked using AdminLinkProviderForUser call. (If the linking was done with ProviderAttributeName set to Cognito_Subject, the same applies here). However, if the user has already signed in, the ProviderAttributeName must be Cognito_Subject and ProviderAttributeValue must be the subject of the SAML assertion.

Deactivates a user and revokes all access tokens for the user. A deactivated user can\'t sign in, but still appears in the responses to GetUser and ListUsers API requests.

You must make this API request with Amazon Web Services credentials that have cognito-idp:AdminDisableUser permissions.

Enables the specified user as an administrator. Works on any user.

Calling this action requires developer credentials.

Forgets the device, as an administrator.

Calling this action requires developer credentials.

Gets the device, as an administrator.

Calling this action requires developer credentials.

Gets the specified user by user name in a user pool as an administrator. Works on any user.

Calling this action requires developer credentials.

Initiates the authentication flow, as an administrator.

Calling this action requires developer credentials.

Links an existing user account in a user pool (DestinationUser) to an identity from an external IdP (SourceUser) based on a specified attribute name and value from the external IdP. This allows you to create a link from the existing user account to an external federated user identity that has not yet been used to sign in. You can then use the federated user identity to sign in as the existing user account.

For example, if there is an existing user with a username and password, this API links that user to a federated user identity. When the user signs in with a federated user identity, they sign in as the existing user account.

This action is administrative and requires developer credentials.

Lists devices, as an administrator.

Calling this action requires developer credentials.

Lists the groups that the user belongs to.

Calling this action requires developer credentials.

A history of user activity and any risks detected as part of Amazon Cognito advanced security.

Removes the specified user from the specified group.

Calling this action requires developer credentials.

Resets the specified user\'s password in a user pool as an administrator. Works on any user.

When a developer calls this API, the current password is invalidated, so it must be changed. If a user tries to sign in after the API is called, the app will get a PasswordResetRequiredException exception back and should direct the user down the flow to reset the password, which is the same as the forgot password flow. In addition, if the user pool has phone verification selected and a verified phone number exists for the user, or if email verification is selected and a verified email exists for the user, calling this API will also result in sending a message to the end user with the code to change their password.

Calling this action requires developer credentials.

Responds to an authentication challenge, as an administrator.

Calling this action requires developer credentials.

The user\'s multi-factor authentication (MFA) preference, including which MFA options are activated, and if any are preferred. Only one factor can be set as preferred. The preferred MFA factor will be used to authenticate a user if multiple factors are activated. If multiple options are activated and no preference is set, a challenge to choose an MFA option will be returned during sign-in.

Sets the specified user\'s password in a user pool as an administrator. Works on any user.

The password can be temporary or permanent. If it is temporary, the user status enters the FORCE_CHANGE_PASSWORD state. When the user next tries to sign in, the InitiateAuth/AdminInitiateAuth response will contain the NEW_PASSWORD_REQUIRED challenge. If the user doesn\'t sign in before it expires, the user won\'t be able to sign in, and an administrator must reset their password.

Once the user has set a new password, or the password is permanent, the user status is set to Confirmed.

This action is no longer supported. You can use it to configure only SMS MFA. You can\'t use it to configure time-based one-time password (TOTP) software token MFA. To configure either type of MFA, use AdminSetUserMFAPreference instead.

Provides feedback for an authentication event indicating if it was from a valid user. This feedback is used for improving the risk evaluation decision for the user pool as part of Amazon Cognito advanced security.

Updates the device status as an administrator.

Calling this action requires developer credentials.

Updates the specified user\'s attributes, including developer attributes, as an administrator. Works on any user.

For custom attributes, you must prepend the custom: prefix to the attribute name.

In addition to updating user attributes, this API can also be used to mark phone and email as verified.

Calling this action requires developer credentials.

Signs out a user from all devices. You must sign AdminUserGlobalSignOut requests with Amazon Web Services credentials. It also invalidates all refresh tokens that Amazon Cognito has issued to a user. The user\'s current access and ID tokens remain valid until they expire. By default, access and ID tokens expire one hour after they\'re issued. A user can still use a hosted UI cookie to retrieve new tokens for the duration of the cookie validity period of 1 hour.

Calling this action requires developer credentials.

Begins setup of time-based one-time password (TOTP) multi-factor authentication (MFA) for a user, with a unique private key that Amazon Cognito generates and returns in the API response. You can authorize an AssociateSoftwareToken request with either the user\'s access token, or a session string from a challenge response that you received from Amazon Cognito.

Changes the password for a specified user in a user pool.

Confirms tracking of the device. This API call is the call that begins device tracking.

Allows a user to enter a confirmation code to reset a forgotten password.

Confirms registration of a new user.

Creates a new group in the specified user pool.

Calling this action requires developer credentials.

Creates an IdP for a user pool.

Creates a new OAuth2.0 resource server and defines custom scopes within it.

Creates the user import job.

Creates a new Amazon Cognito user pool and sets the password policy for the pool.

Creates the user pool client.

When you create a new user pool client, token revocation is automatically activated. For more information about revoking tokens, see RevokeToken.

Creates a new domain for a user pool.

Deletes a group.

Calling this action requires developer credentials.

Deletes an IdP for a user pool.

Deletes a resource server.

Allows a user to delete himself or herself.

Deletes the attributes for a user.

Deletes the specified Amazon Cognito user pool.

Allows the developer to delete the user pool client.

Deletes a domain for a user pool.

Gets information about a specific IdP.

Describes a resource server.

Describes the risk configuration.

Describes the user import job.

Returns the configuration information and metadata of the specified user pool.

Client method for returning the configuration information and metadata of the specified user pool app client.

Gets information about a domain.

Forgets the specified device.

Calling this API causes a message to be sent to the end user with a confirmation code that is required to change the user\'s password. For the Username parameter, you can use the username or user alias. The method used to send the confirmation code is sent according to the specified AccountRecoverySetting. For more information, see Recovering User Accounts in the Amazon Cognito Developer Guide. If neither a verified phone number nor a verified email exists, an InvalidParameterException is thrown. To use the confirmation code for resetting the password, call ConfirmForgotPassword.

Gets the header information for the comma-separated value (CSV) file to be used as input for the user import job.

Gets the device.

Gets a group.

Calling this action requires developer credentials.

Gets the specified IdP.

This method takes a user pool ID, and returns the signing certificate. The issued certificate is valid for 10 years from the date of issue.

Amazon Cognito issues and assigns a new signing certificate annually. This process returns a new value in the response to GetSigningCertificate, but doesn\'t invalidate the original certificate.

Gets the user interface (UI) Customization information for a particular app client\'s app UI, if any such information exists for the client. If nothing is set for the particular client, but there is an existing pool level customization (the app clientId is ALL), then that information is returned. If nothing is present, then an empty shape is returned.

Gets the user attributes and metadata for a user.

Generates a user attribute verification code for the specified attribute name. Sends a message to a user with a code that they must return in a VerifyUserAttribute request.

Gets the user pool multi-factor authentication (MFA) configuration.

Signs out users from all devices. It also invalidates all refresh tokens that Amazon Cognito has issued to a user. A user can still use a hosted UI cookie to retrieve new tokens for the duration of the 1-hour cookie validity period.

Initiates sign-in for a user in the Amazon Cognito user directory. You can\'t sign in a user with a federated IdP with InitiateAuth. For more information, see Adding user pool sign-in through a third party.

Lists the sign-in devices that Amazon Cognito has registered to the current user.

Lists the groups associated with a user pool.

Calling this action requires developer credentials.

Lists information about all IdPs for a user pool.

Lists the resource servers for a user pool.

Lists the tags that are assigned to an Amazon Cognito user pool.

A tag is a label that you can apply to user pools to categorize and manage them in different ways, such as by purpose, owner, environment, or other criteria.

You can use this action up to 10 times per second, per account.

Lists the user import jobs.

Lists the clients that have been created for the specified user pool.

Lists the user pools associated with an Amazon Web Services account.

Lists the users in the Amazon Cognito user pool.

Lists the users in the specified group.

Calling this action requires developer credentials.

Resends the confirmation (for confirmation of registration) to a specific user in the user pool.

Responds to the authentication challenge.

Revokes all of the access tokens generated by, and at the same time as, the specified refresh token. After a token is revoked, you can\'t use the revoked token to access Amazon Cognito user APIs, or to authorize access to your resource server.

Configures actions on detected risks. To delete the risk configuration for UserPoolId or ClientId, pass null values for all four configuration types.

To activate Amazon Cognito advanced security features, update the user pool to include the UserPoolAddOns keyAdvancedSecurityMode.

Sets the user interface (UI) customization information for a user pool\'s built-in app UI.

You can specify app UI customization settings for a single client (with a specific clientId) or for all clients (by setting the clientId to ALL). If you specify ALL, the default configuration is used for every client that has no previously set UI customization. If you specify UI customization settings for a particular client, it will no longer return to the ALL configuration.

Set the user\'s multi-factor authentication (MFA) method preference, including which MFA factors are activated and if any are preferred. Only one factor can be set as preferred. The preferred MFA factor will be used to authenticate a user if multiple factors are activated. If multiple options are activated and no preference is set, a challenge to choose an MFA option will be returned during sign-in. If an MFA type is activated for a user, the user will be prompted for MFA during all sign-in attempts unless device tracking is turned on and the device has been trusted. If you want MFA to be applied selectively based on the assessed risk level of sign-in attempts, deactivate MFA for users and turn on Adaptive Authentication for the user pool.

Sets the user pool multi-factor authentication (MFA) configuration.

This action is no longer supported. You can use it to configure only SMS MFA. You can\'t use it to configure time-based one-time password (TOTP) software token MFA. To configure either type of MFA, use SetUserMFAPreference instead.

Registers the user in the specified user pool and creates a user name, password, and user attributes.

Starts the user import.

Stops the user import job.

Assigns a set of tags to an Amazon Cognito user pool. A tag is a label that you can use to categorize and manage user pools in different ways, such as by purpose, owner, environment, or other criteria.

Each tag consists of a key and value, both of which you define. A key is a general category for more specific values. For example, if you have two versions of a user pool, one for testing and another for production, you might assign an Environment tag key to both user pools. The value of this key might be Test for one user pool, and Production for the other.

Tags are useful for cost tracking and access control. You can activate your tags so that they appear on the Billing and Cost Management console, where you can track the costs associated with your user pools. In an Identity and Access Management policy, you can constrain permissions for user pools based on specific tags or tag values.

You can use this action up to 5 times per second, per account. A user pool can have as many as 50 tags.

Removes the specified tags from an Amazon Cognito user pool. You can use this action up to 5 times per second, per account.

Provides the feedback for an authentication event, whether it was from a valid user or not. This feedback is used for improving the risk evaluation decision for the user pool as part of Amazon Cognito advanced security.

Updates the device status.

Updates the specified group with the specified attributes.

Calling this action requires developer credentials.

Updates IdP information for a user pool.

Updates the name and scopes of resource server. All other fields are read-only.

Allows a user to update a specific attribute (one at a time).

Updates the specified user pool with the specified attributes. You can get a list of the current user pool settings using DescribeUserPool. If you don\'t provide a value for an attribute, it will be set to the default value.

Updates the specified user pool app client with the specified attributes. You can get a list of the current user pool app client settings using DescribeUserPoolClient.

You can also use this operation to enable token revocation for user pool clients. For more information about revoking tokens, see RevokeToken.

Updates the Secure Sockets Layer (SSL) certificate for the custom domain for your user pool.

You can use this operation to provide the Amazon Resource Name (ARN) of a new certificate to Amazon Cognito. You can\'t use it to change the domain for a user pool.

A custom domain is used to host the Amazon Cognito hosted UI, which provides sign-up and sign-in pages for your application. When you set up a custom domain, you provide a certificate that you manage with Certificate Manager (ACM). When necessary, you can use this operation to change the certificate that you applied to your custom domain.

Usually, this is unnecessary following routine certificate renewal with ACM. When you renew your existing certificate in ACM, the ARN for your certificate remains the same, and your custom domain uses the new certificate automatically.

However, if you replace your existing certificate with a new one, ACM gives the new certificate a new ARN. To apply the new certificate to your custom domain, you must provide this ARN to Amazon Cognito.

When you add your new certificate in ACM, you must choose US East (N. Virginia) as the Amazon Web Services Region.

After you submit your request, Amazon Cognito requires up to 1 hour to distribute your new certificate to your custom domain.

For more information about adding a custom domain to your user pool, see Using Your Own Domain for the Hosted UI.

Use this API to register a user\'s entered time-based one-time password (TOTP) code and mark the user\'s software token MFA status as "verified" if successful. The request takes an access token or a session string, but not both.

Verifies the specified user attributes in the user pool.

If your user pool requires verification before Amazon Cognito updates the attribute value, VerifyUserAttribute updates the affected attribute to its pending value. For more information, see UserAttributeUpdateSettingsType.

The Amazon Web Services ID for the user pool owner.

The access token time limit. After this limit expires, your user can\'t use their access token. To specify the time unit for AccessTokenValidity as seconds, minutes, hours, or days, set a TokenValidityUnits value in your API request.

For example, when you set AccessTokenValidity to 10 and TokenValidityUnits to hours, your user can authorize access with their access token for 10 hours.

The default time unit for AccessTokenValidity in an API request is hours. Valid range is displayed below in seconds.

If you don\'t specify otherwise in the configuration of your app client, your access tokens are valid for one hour.

The access token time limit. After this limit expires, your user can\'t use their access token. To specify the time unit for AccessTokenValidity as seconds, minutes, hours, or days, set a TokenValidityUnits value in your API request.

For example, when you set AccessTokenValidity to 10 and TokenValidityUnits to hours, your user can authorize access with their access token for 10 hours.

The default time unit for AccessTokenValidity in an API request is hours. Valid range is displayed below in seconds.

If you don\'t specify otherwise in the configuration of your app client, your access tokens are valid for one hour.

The access token time limit. After this limit expires, your user can\'t use their access token. To specify the time unit for AccessTokenValidity as seconds, minutes, hours, or days, set a TokenValidityUnits value in your API request.

For example, when you set AccessTokenValidity to 10 and TokenValidityUnits to hours, your user can authorize access with their access token for 10 hours.

The default time unit for AccessTokenValidity in an API request is hours. Valid range is displayed below in seconds.

If you don\'t specify otherwise in the configuration of your app client, your access tokens are valid for one hour.

The data type for AccountRecoverySetting.

The available verified method a user can use to recover their password when they call ForgotPassword. You can use this setting to define a preferred method when a user has more than one method available. With this setting, SMS doesn\'t qualify for a valid password recovery mechanism if the user also has SMS multi-factor authentication (MFA) activated. In the absence of this setting, Amazon Cognito uses the legacy behavior to determine the recovery method where SMS is preferred through email.

The available verified method a user can use to recover their password when they call ForgotPassword. You can use this setting to define a preferred method when a user has more than one method available. With this setting, SMS doesn\'t qualify for a valid password recovery mechanism if the user also has SMS multi-factor authentication (MFA) activated. In the absence of this setting, Amazon Cognito uses the legacy behavior to determine the recovery method where SMS is preferred through email.

The available verified method a user can use to recover their password when they call ForgotPassword. You can use this setting to define a preferred method when a user has more than one method available. With this setting, SMS doesn\'t qualify for a valid password recovery mechanism if the user also has SMS multi-factor authentication (MFA) activated. In the absence of this setting, Amazon Cognito uses the legacy behavior to determine the recovery method where SMS is preferred through email.

Flag specifying whether to send a notification.

Account takeover action type.

Action to take for a low risk.

Action to take for a medium risk.

Action to take for a high risk.

Account takeover actions type.

Account takeover risk configuration actions.

The action to take in response to the account takeover action. Valid values are as follows:

• BLOCK Choosing this action will block the request.

• MFA_IF_CONFIGURED Present an MFA challenge if user has configured it, else allow the request.

• MFA_REQUIRED Present an MFA challenge if user has configured it, else block the request.

• NO_ACTION Allow the user to sign in.

Configuration for mitigation actions and notification for different levels of risk detected for a potential account takeover.

The account takeover risk configuration object, including the NotifyConfiguration object and Actions to take if there is an account takeover.

The account takeover risk configuration.

Represents the request to add custom attributes.

Represents the response from the server for the request to add custom attributes.

Represents the request to confirm user registration.

Represents the response from the server for the request to confirm registration.

The configuration for creating a new user profile.

The configuration for AdminCreateUser requests.

The configuration for AdminCreateUser requests.

The configuration for AdminCreateUser requests.

Represents the request to create a user in the specified user pool.

Represents the response from the server to the request to create the user.

The user account expiration limit, in days, after which a new account that hasn\'t signed in is no longer usable. To reset the account after that time limit, you must call AdminCreateUser again, specifying "RESEND" for the MessageAction parameter. The default value for this parameter is 7.

Represents the request to delete user attributes as an administrator.

Represents the response received from the server for a request to delete user attributes.

Represents the request to delete a user as an administrator.

Represents the request to disable the user as an administrator.

Represents the response received from the server to disable the user as an administrator.

Represents the request that enables the user as an administrator.

Represents the response from the server for the request to enable a user as an administrator.

Sends the forgot device request, as an administrator.

Represents the request to get the device, as an administrator.

Gets the device response, as an administrator.

Represents the request to get the specified user as an administrator.

Represents the response from the server from the request to get the specified user as an administrator.

Initiates the authorization request, as an administrator.

Initiates the authentication response, as an administrator.

Represents the request to list devices, as an administrator.

Lists the device\'s response, as an administrator.

Represents the request to reset a user\'s password as an administrator.

Represents the response from the server to reset a user password as an administrator.

The request to respond to the authentication challenge, as an administrator.

Responds to the authentication challenge, as an administrator.

You can use this parameter to set an MFA configuration that uses the SMS delivery medium.

Represents the response from the server to set user settings as an administrator.

The request to update the device status, as an administrator.

The status response to the request to update the device, as an administrator.

Represents the request to update the user\'s attributes as an administrator.

Represents the response from the server for the request to update user attributes as an administrator.

The request to sign out of all devices, as an administrator.

The global sign-out response, as an administrator.

The advanced security mode.

Attributes supported as an alias for this user pool. Possible values: phone_number, email, or preferred_username.

The attributes that are aliased in a user pool.

This exception is thrown when a user tries to confirm the account with an email address or phone number that has already been supplied as an alias for a different user profile. This exception indicates that an account with this email address or phone already exists in a user pool that you\'ve configured to use email address or phone number as a sign-in alias.

The Amazon Pinpoint analytics configuration necessary to collect metrics for a user pool.

The user pool analytics configuration for collecting metrics and sending them to your Amazon Pinpoint campaign.

The Amazon Pinpoint analytics configuration necessary to collect metrics for this user pool.

The Amazon Pinpoint analytics configuration for the user pool client.

An Amazon Pinpoint analytics endpoint.

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 Using Amazon Pinpoint analytics with Amazon Cognito user pools.

The analytics metadata for collecting Amazon Pinpoint metrics for AdminInitiateAuth calls.

The analytics metadata for collecting Amazon Pinpoint metrics for AdminRespondToAuthChallenge calls.

The Amazon Pinpoint analytics metadata for collecting metrics for ConfirmForgotPassword calls.

The Amazon Pinpoint analytics metadata for collecting metrics for ConfirmSignUp calls.

The Amazon Pinpoint analytics metadata that contributes to your metrics for ForgotPassword calls.

The Amazon Pinpoint analytics metadata that contributes to your metrics for InitiateAuth calls.

The Amazon Pinpoint analytics metadata that contributes to your metrics for ResendConfirmationCode calls.

The Amazon Pinpoint analytics metadata that contributes to your metrics for RespondToAuthChallenge calls.

The Amazon Pinpoint analytics metadata that contributes to your metrics for SignUp calls.

The Amazon Resource Name (ARN) of an Amazon Pinpoint project. You can use the Amazon Pinpoint project to integrate with the chosen user pool Client. Amazon Cognito publishes events to the Amazon Pinpoint project that the app ARN declares.

The ARN of an Identity and Access Management role that authorizes Amazon Cognito to publish events to Amazon Pinpoint analytics.

The role Amazon Resource Name (ARN) for the group.

The role ARN for the Amazon CloudWatch Logs Logging role for the user import job.

The Amazon Resource Name (ARN) of an Certificate Manager SSL certificate. You use this certificate for the subdomain of your custom domain.

The Amazon Resource Name (ARN) of the Lambda function that Amazon Cognito activates to send email notifications to users.

The Amazon Resource Name (ARN) of the Lambda function that Amazon Cognito activates to send SMS notifications to users.

The ARN of a verified email address in Amazon SES. Amazon Cognito uses this email address in one of the following ways, depending on the value that you specify for the EmailSendingAccount parameter:

• If you specify COGNITO_DEFAULT, Amazon Cognito uses this address as the custom FROM address when it emails your users using its built-in email account.

• If you specify DEVELOPER, Amazon Cognito emails your users with this address by calling Amazon SES on your behalf.

The Region value of the SourceArn parameter must indicate a supported Amazon Web Services Region of your user pool. Typically, the Region in the SourceArn and the user pool Region are the same. For more information, see Amazon SES email configuration regions in the Amazon Cognito Developer Guide.

The role Amazon Resource Name (ARN) for the group.

A pre-registration Lambda trigger.

A custom Message Lambda trigger.

A post-confirmation Lambda trigger.

A pre-authentication Lambda trigger.

A post-authentication Lambda trigger.

Defines the authentication challenge.

Creates an authentication challenge.

Verifies the authentication challenge response.

A Lambda trigger that is invoked before token generation.

The user migration Lambda config type.

The Amazon Resource Name (ARN) of an KMS key. Amazon Cognito uses the key to encrypt codes and temporary passwords sent to CustomEmailSender and CustomSMSSender.

The Amazon Resource Name (ARN) of the user pool that the tags are assigned to.

The Amazon Resource Name (ARN) of the identity that is associated with the sending authorization policy. This identity permits Amazon Cognito to send for the email address specified in the From parameter.

The Amazon Resource Name (ARN) of the Amazon SNS caller. This is the ARN of the IAM role in your Amazon Web Services account that Amazon Cognito will use to send SMS messages. SMS messages are subject to a spending limit.

The Amazon Resource Name (ARN) of the user pool to assign the tags to.

The Amazon Resource Name (ARN) of the user pool that the tags are assigned to.

The new role Amazon Resource Name (ARN) for the group. This is used for setting the cognito:roles and cognito:preferred_role claims in the token.

The role Amazon Resource Name (ARN) for the Amazon CloudWatch Logging role for the user import job. For more information, see "Creating the CloudWatch Logs IAM Role" in the Amazon Cognito Developer Guide.

The Amazon Resource Name (ARN) for the user pool.

The attribute data type.

An array of name-value pairs that contain user attributes and attribute values to be set for the user to be created. You can create a user without specifying any attributes other than Username. However, any attributes that you specify as required (when creating a user pool or in the Attributes tab of the console) either you should supply (in your call to AdminCreateUser) or the user should supply (when they sign up in response to your welcome message).

For custom attributes, you must prepend the custom: prefix to the attribute name.

To send a message inviting the user to sign up, you must specify the user\'s email address or phone number. You can do this in your call to AdminCreateUser or in the Users tab of the Amazon Cognito console for managing your user pools.

In your call to AdminCreateUser, you can set the email_verified attribute to True, and you can set the phone_number_verified attribute to True. You can also do this by calling AdminUpdateUserAttributes.

• email: The email address of the user to whom the message that contains the code and username will be sent. Required if the email_verified attribute is set to True, or if "EMAIL" is specified in the DesiredDeliveryMediums parameter.

• phone_number: The phone number of the user to whom the message that contains the code and username will be sent. Required if the phone_number_verified attribute is set to True, or if "SMS" is specified in the DesiredDeliveryMediums parameter.

The user\'s validation data. This is an array of name-value pairs that contain user attributes and attribute values that you can use for custom validation, such as restricting the types of user accounts that can be registered. For example, you might choose to allow or disallow user sign-up based on the user\'s domain.

To configure custom validation, you must create a Pre Sign-up Lambda trigger for the user pool as described in the Amazon Cognito Developer Guide. The Lambda trigger receives the validation data and uses it in the validation process.

The user\'s validation data isn\'t persisted.

An array of name-value pairs representing user attributes.

An array of name-value pairs representing user attributes.

For custom attributes, you must prepend the custom: prefix to the attribute name.

If your user pool requires verification before Amazon Cognito updates an attribute value that you specify in this request, Amazon Cognito doesn’t immediately update the value of that attribute. After your user receives and responds to a verification message to verify the new value, Amazon Cognito updates the attribute value. Your user can sign in and receive messages with the original attribute value until they verify the new value.

To update the value of an attribute that requires verification in the same API request, include the email_verified or phone_number_verified attribute, with a value of true. If you set the email_verified or phone_number_verified value for an email or phone_number attribute that requires verification to true, Amazon Cognito doesn’t send a verification message to your user.

The device attributes.

An array of name-value pairs representing user attributes.

For custom attributes, you must prepend the custom: prefix to the attribute name.

An array of name-value pairs representing user attributes.

For custom attributes, you must prepend the custom: prefix to the attribute name.

The validation data in the request to register a user.

An array of name-value pairs representing user attributes.

For custom attributes, you must prepend the custom: prefix to the attribute name.

If you have set an attribute to require verification before Amazon Cognito updates its value, this request doesn’t immediately update the value of that attribute. After your user receives and responds to a verification message to verify the new value, Amazon Cognito updates the attribute value. Your user can sign in and receive messages with the original attribute value until they verify the new value.

A container with information about the user type attributes.

A mapping of IdP attributes to standard and custom user pool attributes.

A mapping of IdP attributes to standard and custom user pool attributes.

The IdP attribute mapping to be changed.

An array of strings representing the user attribute names you want to delete.

For custom attributes, you must prepend the custom: prefix to the attribute name.

An array of strings representing the user attribute names you want to delete.

For custom attributes, you must prependattach the custom: prefix to the front of the attribute name.

The name of the attribute.

The name of the attribute that Amazon Cognito verifies with the code.

The attribute name returned by the server response to get the user attribute verification code.

The attribute name of the MFA option type. The only valid value is phone_number.

The attribute name in the request to verify user attributes.

Specifies whether the attribute is standard or custom.

The value of the attribute.

Requires that your user verifies their email address, phone number, or both before Amazon Cognito updates the value of that attribute. When you update a user attribute that has this option activated, Amazon Cognito sends a verification message to the new phone number or email address. Amazon Cognito doesn’t change the value of the attribute until your user responds to the verification message and confirms the new value.

You can verify an updated email address or phone number with a VerifyUserAttribute API request. You can also call the UpdateUserAttributes or AdminUpdateUserAttributes API and set email_verified or phone_number_verified to true.

When AttributesRequireVerificationBeforeUpdate is false, your user pool doesn\'t require that your users verify attribute changes before Amazon Cognito updates them. In a user pool where AttributesRequireVerificationBeforeUpdate is false, API operations that change attribute values can immediately update a user’s email or phone_number attribute.

The authentication event type.

The response object. It includes the EventID, EventType, CreationDate, EventRisk, and EventResponse.

The authentication flow for this call to run. The API action will depend on this value. For example:

• REFRESH_TOKEN_AUTH will take in a valid refresh token and return new tokens.

• USER_SRP_AUTH will take in USERNAME and SRP_A and return the Secure Remote Password (SRP) protocol variables to be used for next challenge execution.

• ADMIN_USER_PASSWORD_AUTH will take in USERNAME and PASSWORD and return the next challenge or tokens.

Valid values include:

• USER_SRP_AUTH: Authentication flow for the Secure Remote Password (SRP) protocol.

• REFRESH_TOKEN_AUTH/REFRESH_TOKEN: Authentication flow for refreshing the access token and ID token by supplying a valid refresh token.

• CUSTOM_AUTH: Custom authentication flow.

• ADMIN_NO_SRP_AUTH: Non-SRP authentication flow; you can pass in the USERNAME and PASSWORD directly if the flow is enabled for calling the app client.

• ADMIN_USER_PASSWORD_AUTH: Admin-based user password authentication. This replaces the ADMIN_NO_SRP_AUTH authentication flow. In this flow, Amazon Cognito receives the password in the request instead of using the SRP process to verify passwords.

The authentication flow for this call to run. The API action will depend on this value. For example:

• REFRESH_TOKEN_AUTH takes in a valid refresh token and returns new tokens.

• USER_SRP_AUTH takes in USERNAME and SRP_A and returns the SRP variables to be used for next challenge execution.

• USER_PASSWORD_AUTH takes in USERNAME and PASSWORD and returns the next challenge or tokens.

Valid values include:

• USER_SRP_AUTH: Authentication flow for the Secure Remote Password (SRP) protocol.

• REFRESH_TOKEN_AUTH/REFRESH_TOKEN: Authentication flow for refreshing the access token and ID token by supplying a valid refresh token.

• CUSTOM_AUTH: Custom authentication flow.

• USER_PASSWORD_AUTH: Non-SRP authentication flow; user name and password are passed directly. If a user migration Lambda trigger is set, this flow will invoke the user migration Lambda if it doesn\'t find the user name in the user pool.

ADMIN_NO_SRP_AUTH isn\'t a valid value.

The authentication parameters. These are inputs corresponding to the AuthFlow that you\'re invoking. The required values depend on the value of AuthFlow:

• For USER_SRP_AUTH: USERNAME (required), SRP_A (required), SECRET_HASH (required if the app client is configured with a client secret), DEVICE_KEY.

• For REFRESH_TOKEN_AUTH/REFRESH_TOKEN: REFRESH_TOKEN (required), SECRET_HASH (required if the app client is configured with a client secret), DEVICE_KEY.

• For ADMIN_NO_SRP_AUTH: USERNAME (required), SECRET_HASH (if app client is configured with client secret), PASSWORD (required), DEVICE_KEY.

• For CUSTOM_AUTH: USERNAME (required), SECRET_HASH (if app client is configured with client secret), DEVICE_KEY. To start the authentication flow with password verification, include ChallengeName: SRP_A and SRP_A: (The SRP_A Value).

The authentication parameters. These are inputs corresponding to the AuthFlow that you\'re invoking. The required values depend on the value of AuthFlow:

• For USER_SRP_AUTH: USERNAME (required), SRP_A (required), SECRET_HASH (required if the app client is configured with a client secret), DEVICE_KEY.

• For REFRESH_TOKEN_AUTH/REFRESH_TOKEN: REFRESH_TOKEN (required), SECRET_HASH (required if the app client is configured with a client secret), DEVICE_KEY.

• For CUSTOM_AUTH: USERNAME (required), SECRET_HASH (if app client is configured with client secret), DEVICE_KEY. To start the authentication flow with password verification, include ChallengeName: SRP_A and SRP_A: (The SRP_A Value).

Amazon Cognito creates a session token for each API request in an authentication flow. AuthSessionValidity is the duration, in minutes, of that session token. Your user pool native user must respond to each authentication challenge before the session expires.

Amazon Cognito creates a session token for each API request in an authentication flow. AuthSessionValidity is the duration, in minutes, of that session token. Your user pool native user must respond to each authentication challenge before the session expires.

Amazon Cognito creates a session token for each API request in an authentication flow. AuthSessionValidity is the duration, in minutes, of that session token. Your user pool native user must respond to each authentication challenge before the session expires.

The authentication result.

The result of the authentication response. This is only returned if the caller doesn\'t need to pass another challenge. If the caller does need to pass another challenge before it gets tokens, ChallengeName, ChallengeParameters, and Session are returned.

The result returned by the server in response to the authentication request.

The result of the authentication response. This result is only returned if the caller doesn\'t need to pass another challenge. If the caller does need to pass another challenge before it gets tokens, ChallengeName, ChallengeParameters, and Session are returned.

The result returned by the server in response to the request to respond to the authentication challenge.

Overrides the risk decision to always block the pre-authentication requests. The IP range is in CIDR notation, a compact representation of an IP address and its routing prefix.

Set to True if only the administrator is allowed to create user profiles. Set to False if users can sign themselves up via an app.

Indicates that the status is enabled.

True if the password is permanent, False if it is temporary.

If UserDataShared is true, Amazon Cognito includes user data in the events that it publishes to Amazon Pinpoint analytics.

Indicates whether the user confirmation must confirm the device response.

Set to true if the client is allowed to follow the OAuth protocol when interacting with Amazon Cognito user pools.

When true, a remembered device can sign in with device authentication instead of SMS and time-based one-time password (TOTP) factors for multi-factor authentication (MFA).

When true, Amazon Cognito doesn\'t automatically remember a user\'s device when your app sends a ConfirmDevice API request. In your app, create a prompt for your user to choose whether they want to remember their device. Return the user\'s choice in an UpdateDeviceStatus API request.

When DeviceOnlyRememberedOnUserPrompt is false, Amazon Cognito immediately remembers devices that you register in a ConfirmDevice API request.

In the password policy that you have set, refers to whether you have required users to use at least one uppercase letter in their password.

In the password policy that you have set, refers to whether you have required users to use at least one lowercase letter in their password.

In the password policy that you have set, refers to whether you have required users to use at least one number in their password.

In the password policy that you have set, refers to whether you have required users to use at least one symbol in their password.

Specifies whether SMS text message MFA is activated. If an MFA type is activated for a user, the user will be prompted for MFA during all sign-in attempts, unless device tracking is turned on and the device has been trusted.

Specifies whether SMS is the preferred MFA method.

Specifies whether the attribute type is developer only. This attribute can only be modified by an administrator. Users won\'t be able to modify this attribute using their access token. For example, DeveloperOnlyAttribute can be modified using AdminUpdateUserAttributes but can\'t be updated using UpdateUserAttributes.

Specifies whether the value of the attribute can be changed.

For any user pool attribute that is mapped to an IdP attribute, you must set this parameter to true. Amazon Cognito updates mapped attributes when users sign in to your application through an IdP. If an attribute is immutable, Amazon Cognito throws an error when it attempts to update the attribute. For more information, see Specifying Identity Provider Attribute Mappings for Your User Pool.

Specifies whether a user pool attribute is required. If the attribute is required and the user doesn\'t provide a value, registration or sign-in will fail.

A response from the server indicating that a user registration has been confirmed.

Specifies whether software token MFA is activated.

Specifies whether software token MFA is activated. If an MFA type is activated for a user, the user will be prompted for MFA during all sign-in attempts, unless device tracking is turned on and the device has been trusted.

Specifies whether software token MFA is the preferred MFA method.

Set to true if the client is allowed to follow the OAuth protocol when interacting with Amazon Cognito user pools.

Set to true if the client is allowed to follow the OAuth protocol when interacting with Amazon Cognito user pools.

Specifies whether the user is enabled.

The CSS values in the UI customization.

The CSS values in the UI customization.

The CSS version number.

A list of allowed redirect (callback) URLs for the IdPs.

A redirect URI must:

• Be an absolute URI.

• Be registered with the authorization server.

• Not include a fragment component.

See OAuth 2.0 - Redirection Endpoint.

Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only.

App callback URLs such as myapp://example are also supported.

A list of allowed redirect (callback) URLs for the IdPs.

A redirect URI must:

• Be an absolute URI.

• Be registered with the authorization server.

• Not include a fragment component.

See OAuth 2.0 - Redirection Endpoint.

Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only.

App callback URLs such as myapp://example are also supported.

A list of allowed redirect (callback) URLs for the IdPs.

A redirect URI must:

• Be an absolute URI.

• Be registered with the authorization server.

• Not include a fragment component.

See OAuth 2.0 - Redirection Endpoint.

Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only.

App callback URLs such as myapp://example are also supported.

The challenge name.

The name of the challenge that you\'re responding to with this call. This is returned in the AdminInitiateAuth response if you must pass another challenge.

• MFA_SETUP: If MFA is required, users who don\'t have at least one of the MFA methods set up are presented with an MFA_SETUP challenge. The user must set up at least one MFA type to continue to authenticate.

• SELECT_MFA_TYPE: Selects the MFA type. Valid MFA options are SMS_MFA for text SMS MFA, and SOFTWARE_TOKEN_MFA for time-based one-time password (TOTP) software token MFA.

• SMS_MFA: Next challenge is to supply an SMS_MFA_CODE, delivered via SMS.

• PASSWORD_VERIFIER: Next challenge is to supply PASSWORD_CLAIM_SIGNATURE, PASSWORD_CLAIM_SECRET_BLOCK, and TIMESTAMP after the client-side SRP calculations.

• CUSTOM_CHALLENGE: This is returned if your custom authentication flow determines that the user should pass another challenge before tokens are issued.

• DEVICE_SRP_AUTH: If device tracking was activated in your user pool and the previous challenges were passed, this challenge is returned so that Amazon Cognito can start tracking this device.

• DEVICE_PASSWORD_VERIFIER: Similar to PASSWORD_VERIFIER, but for devices only.

• ADMIN_NO_SRP_AUTH: This is returned if you must authenticate with USERNAME and PASSWORD directly. An app client must be enabled to use this flow.

• NEW_PASSWORD_REQUIRED: For users who are required to change their passwords after successful first login. Respond to this challenge with NEW_PASSWORD and any required attributes that Amazon Cognito returned in the requiredAttributes parameter. You can also set values for attributes that aren\'t required by your user pool and that your app client can write. For more information, see AdminRespondToAuthChallenge.

  In a NEW_PASSWORD_REQUIRED challenge response, you can\'t modify a required attribute that already has a value. In AdminRespondToAuthChallenge, set a value for any keys that Amazon Cognito returned in the requiredAttributes parameter, then use the AdminUpdateUserAttributes API operation to modify the value of any additional attributes.

• MFA_SETUP: For users who are required to set up an MFA factor before they can sign in. The MFA types activated for the user pool will be listed in the challenge parameters MFA_CAN_SETUP value.

  To set up software token MFA, use the session returned here from InitiateAuth as an input to AssociateSoftwareToken, and use the session returned by VerifySoftwareToken as an input to RespondToAuthChallenge with challenge name MFA_SETUP to complete sign-in. To set up SMS MFA, users will need help from an administrator to add a phone number to their account and then call InitiateAuth again to restart sign-in.

The challenge name. For more information, see AdminInitiateAuth.

The name of the challenge. For more information, see AdminInitiateAuth.

The name of the challenge that you\'re responding to with this call. This name is returned in the AdminInitiateAuth response if you must pass another challenge.

Valid values include the following:

• SMS_MFA: Next challenge is to supply an SMS_MFA_CODE, delivered via SMS.

• PASSWORD_VERIFIER: Next challenge is to supply PASSWORD_CLAIM_SIGNATURE, PASSWORD_CLAIM_SECRET_BLOCK, and TIMESTAMP after the client-side SRP calculations.

• CUSTOM_CHALLENGE: This is returned if your custom authentication flow determines that the user should pass another challenge before tokens are issued.

• DEVICE_SRP_AUTH: If device tracking was activated on your user pool and the previous challenges were passed, this challenge is returned so that Amazon Cognito can start tracking this device.

• DEVICE_PASSWORD_VERIFIER: Similar to PASSWORD_VERIFIER, but for devices only.

• NEW_PASSWORD_REQUIRED: For users who are required to change their passwords after successful first login.

  Respond to this challenge with NEW_PASSWORD and any required attributes that Amazon Cognito returned in the requiredAttributes parameter. You can also set values for attributes that aren\'t required by your user pool and that your app client can write. For more information, see RespondToAuthChallenge.

  In a NEW_PASSWORD_REQUIRED challenge response, you can\'t modify a required attribute that already has a value. In RespondToAuthChallenge, set a value for any keys that Amazon Cognito returned in the requiredAttributes parameter, then use the UpdateUserAttributes API operation to modify the value of any additional attributes.

• MFA_SETUP: For users who are required to setup an MFA factor before they can sign in. The MFA types activated for the user pool will be listed in the challenge parameters MFA_CAN_SETUP value.

  To set up software token MFA, use the session returned here from InitiateAuth as an input to AssociateSoftwareToken. Use the session returned by VerifySoftwareToken as an input to RespondToAuthChallenge with challenge name MFA_SETUP to complete sign-in. To set up SMS MFA, an administrator should help the user to add a phone number to their account, and then the user should call InitiateAuth again to restart sign-in.

The challenge name. For more information, see InitiateAuth.

ADMIN_NO_SRP_AUTH isn\'t a valid value.

The challenge name. For more information, see InitiateAuth.

The challenge parameters. These are returned to you in the AdminInitiateAuth response if you must pass another challenge. The responses in this parameter should be used to compute inputs to the next call (AdminRespondToAuthChallenge).

All challenges require USERNAME and SECRET_HASH (if applicable).

The value of the USER_ID_FOR_SRP attribute is the user\'s actual username, not an alias (such as email address or phone number), even if you specified an alias in your call to AdminInitiateAuth. This happens because, in the AdminRespondToAuthChallenge API ChallengeResponses, the USERNAME attribute can\'t be an alias.

The challenge parameters. For more information, see AdminInitiateAuth.

The challenge parameters. These are returned in the InitiateAuth response if you must pass another challenge. The responses in this parameter should be used to compute inputs to the next call (RespondToAuthChallenge).

All challenges require USERNAME and SECRET_HASH (if applicable).

The challenge parameters. For more information, see InitiateAuth.

The challenge response.

The challenge responses.

The challenge response type.

The challenge responses. These are inputs corresponding to the value of ChallengeName, for example:

• SMS_MFA: SMS_MFA_CODE, USERNAME, SECRET_HASH (if app client is configured with client secret).

• PASSWORD_VERIFIER: PASSWORD_CLAIM_SIGNATURE, PASSWORD_CLAIM_SECRET_BLOCK, TIMESTAMP, USERNAME, SECRET_HASH (if app client is configured with client secret).

  PASSWORD_VERIFIER requires DEVICE_KEY when signing in with a remembered device.

• ADMIN_NO_SRP_AUTH: PASSWORD, USERNAME, SECRET_HASH (if app client is configured with client secret).

• NEW_PASSWORD_REQUIRED: NEW_PASSWORD, USERNAME, SECRET_HASH (if app client is configured with client secret). To set any required attributes that Amazon Cognito returned as requiredAttributes in the AdminInitiateAuth response, add a userAttributes.attributename parameter. This parameter can also set values for writable attributes that aren\'t required by your user pool.

  In a NEW_PASSWORD_REQUIRED challenge response, you can\'t modify a required attribute that already has a value. In AdminRespondToAuthChallenge, set a value for any keys that Amazon Cognito returned in the requiredAttributes parameter, then use the AdminUpdateUserAttributes API operation to modify the value of any additional attributes.

• MFA_SETUP requires USERNAME, plus you must use the session value returned by VerifySoftwareToken in the Session parameter.

The value of the USERNAME attribute must be the user\'s actual username, not an alias (such as an email address or phone number). To make this simpler, the AdminInitiateAuth response includes the actual username value in the USERNAMEUSER_ID_FOR_SRP attribute. This happens even if you specified an alias in your call to AdminInitiateAuth.

The challenge responses. These are inputs corresponding to the value of ChallengeName, for example:

• SMS_MFA: SMS_MFA_CODE, USERNAME.

• PASSWORD_VERIFIER: PASSWORD_CLAIM_SIGNATURE, PASSWORD_CLAIM_SECRET_BLOCK, TIMESTAMP, USERNAME.

  PASSWORD_VERIFIER requires DEVICE_KEY when you sign in with a remembered device.

• NEW_PASSWORD_REQUIRED: NEW_PASSWORD, USERNAME, SECRET_HASH (if app client is configured with client secret). To set any required attributes that Amazon Cognito returned as requiredAttributes in the InitiateAuth response, add a userAttributes.attributename parameter. This parameter can also set values for writable attributes that aren\'t required by your user pool.

  In a NEW_PASSWORD_REQUIRED challenge response, you can\'t modify a required attribute that already has a value. In RespondToAuthChallenge, set a value for any keys that Amazon Cognito returned in the requiredAttributes parameter, then use the UpdateUserAttributes API operation to modify the value of any additional attributes.

• SOFTWARE_TOKEN_MFA: USERNAME and SOFTWARE_TOKEN_MFA_CODE are required attributes.

• DEVICE_SRP_AUTH requires USERNAME, DEVICE_KEY, SRP_A (and SECRET_HASH).

• DEVICE_PASSWORD_VERIFIER requires everything that PASSWORD_VERIFIER requires, plus DEVICE_KEY.

• MFA_SETUP requires USERNAME, plus you must use the session value returned by VerifySoftwareToken in the Session parameter.

Represents the request to change a user password.

The response from the server to the change password request.

The app client ID.

The app client ID.

The app client ID of the app associated with the user pool.

The ID of the app client associated with the user pool.

The app client ID of the app associated with the user pool.

The app client ID.

The app client ID of the app associated with the user pool.

The ID of the client associated with the user pool.

The client ID for the client app.

The app client ID.

The ID of the client associated with the user pool.

The app client ID.

The client ID for the token that you want to revoke.

The app client ID.

The app client ID. If ClientId is null, then the risk configuration is mapped to userPoolId. When the client ID is null, the same risk configuration is applied to all the clients in the userPool.

Otherwise, ClientId is mapped to the client. When the client ID isn\'t null, the user pool configuration is overridden and the risk configuration for the client is used instead.

The client ID for the client app.

The ID of the client associated with the user pool.

The client ID for the client app.

The ID of the client associated with the user pool.

The ID of the client associated with the user pool.

The ID of the client associated with the user pool.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

If your user pool configuration includes triggers, the AdminConfirmSignUp API action invokes the Lambda function that is specified for the post confirmation trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. In this payload, the clientMetadata attribute provides the data that you assigned to the ClientMetadata parameter in your AdminConfirmSignUp request. In your function code in Lambda, you can process the ClientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminCreateUser API action, Amazon Cognito invokes the function that is assigned to the pre sign-up trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminCreateUser request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for certain custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminInitiateAuth API action, Amazon Cognito invokes the Lambda functions that are specified for various triggers. The ClientMetadata value is passed as input to the functions for only the following triggers:

• Pre signup

• Pre authentication

• User migration

When Amazon Cognito invokes the functions for these triggers, it passes a JSON payload, which the function receives as input. This payload contains a validationData attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminInitiateAuth request. In your function code in Lambda, you can process the validationData value to enhance your workflow for your specific needs.

When you use the AdminInitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it doesn\'t provide the ClientMetadata value as input:

• Post authentication

• Custom message

• Pre token generation

• Create auth challenge

• Define auth challenge

• Verify auth challenge

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminResetUserPassword API action, Amazon Cognito invokes the function that is assigned to the custom message trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminResetUserPassword request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminRespondToAuthChallenge API action, Amazon Cognito invokes any functions that you have assigned to the following triggers:

• pre sign-up

• custom message

• post authentication

• user migration

• pre token generation

• define auth challenge

• create auth challenge

• verify auth challenge response

When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute that provides the data that you assigned to the ClientMetadata parameter in your AdminRespondToAuthChallenge request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the AdminUpdateUserAttributes API action, Amazon Cognito invokes the function that is assigned to the custom message trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute, which provides the data that you assigned to the ClientMetadata parameter in your AdminUpdateUserAttributes request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the ConfirmForgotPassword API action, Amazon Cognito invokes the function that is assigned to the post confirmation trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute, which provides the data that you assigned to the ClientMetadata parameter in your ConfirmForgotPassword request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the ConfirmSignUp API action, Amazon Cognito invokes the function that is assigned to the post confirmation trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute, which provides the data that you assigned to the ClientMetadata parameter in your ConfirmSignUp request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the ForgotPassword API action, Amazon Cognito invokes any functions that are assigned to the following triggers: pre sign-up, custom message, and user migration. When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute, which provides the data that you assigned to the ClientMetadata parameter in your ForgotPassword request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the GetUserAttributeVerificationCode API action, Amazon Cognito invokes the function that is assigned to the custom message trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute, which provides the data that you assigned to the ClientMetadata parameter in your GetUserAttributeVerificationCode request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for certain custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the InitiateAuth API action, Amazon Cognito invokes the Lambda functions that are specified for various triggers. The ClientMetadata value is passed as input to the functions for only the following triggers:

• Pre signup

• Pre authentication

• User migration

When Amazon Cognito invokes the functions for these triggers, it passes a JSON payload, which the function receives as input. This payload contains a validationData attribute, which provides the data that you assigned to the ClientMetadata parameter in your InitiateAuth request. In your function code in Lambda, you can process the validationData value to enhance your workflow for your specific needs.

When you use the InitiateAuth API action, Amazon Cognito also invokes the functions for the following triggers, but it doesn\'t provide the ClientMetadata value as input:

• Post authentication

• Custom message

• Pre token generation

• Create auth challenge

• Define auth challenge

• Verify auth challenge

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the ResendConfirmationCode API action, Amazon Cognito invokes the function that is assigned to the custom message trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute, which provides the data that you assigned to the ClientMetadata parameter in your ResendConfirmationCode request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

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: post authentication, pre token generation, define auth challenge, create auth challenge, and verify auth challenge. When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata 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 clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action triggers.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the SignUp API action, Amazon Cognito invokes any functions that are assigned to the following triggers: pre sign-up, custom message, and post confirmation. When Amazon Cognito invokes any of these functions, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute, which provides the data that you assigned to the ClientMetadata parameter in your SignUp request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

A map of custom key-value pairs that you can provide as input for any custom workflows that this action initiates.

You create custom workflows by assigning Lambda functions to user pool triggers. When you use the UpdateUserAttributes API action, Amazon Cognito invokes the function that is assigned to the custom message trigger. When Amazon Cognito invokes this function, it passes a JSON payload, which the function receives as input. This payload contains a clientMetadata attribute, which provides the data that you assigned to the ClientMetadata parameter in your UpdateUserAttributes request. In your function code in Lambda, you can process the clientMetadata value to enhance your workflow for your specific needs.

For more information, see Customizing user pool Workflows with Lambda Triggers in the Amazon Cognito Developer Guide.

The client name for the user pool client you would like to create.

The client name from the update user pool client request.

The client name from the user pool client description.

The client name from the user pool request of the client type.

The read attributes.

The user pool attributes that the app client can write to.

If your app client allows users to sign in through an IdP, this array must include all attributes that you have mapped to IdP attributes. Amazon Cognito updates mapped attributes when users sign in to your application through an IdP. If your app client does not have write access to a mapped attribute, Amazon Cognito throws an error when it tries to update the attribute. For more information, see Specifying IdP Attribute Mappings for Your user pool.

The read-only attributes of the user pool.

The writeable attributes of the user pool.

The Read-only attributes.

The writeable attributes.

The secret for the client ID. This is required only if the client ID has a secret.

The client secret from the user pool request of the client type.

The code delivery details list from the server for the request to update user attributes.

The delivery details for an email or SMS message that Amazon Cognito sent for authentication or verification.

The code delivery details returned by the server in response to the request to reset a password.

The code delivery details returned by the server in response to the request to get the user attribute verification code.

The code delivery details returned by the server in response to the request to resend the confirmation code.

The code delivery details returned by the server response to the user registration request.

This exception is thrown when a verification code fails to deliver successfully.

This exception is thrown if the provided code doesn\'t match what the server was expecting.

The message returned when the user import job is completed.

The compromised credentials actions type.

The compromised credentials risk configuration actions.

The event action.

The compromised credentials risk configuration type.

The compromised credentials risk configuration object, including the EventFilter and the EventAction.

The compromised credentials risk configuration.

This exception is thrown if two or more modifications are happening concurrently.

Confirms the device request.

Confirms the device response.

The request representing the confirmation for a password reset.

The response from the server that results from a user\'s request to retrieve a forgotten password.

Represents the request to confirm registration of a user.

Represents the response from the server for the registration confirmation.

The confirmation code from your user\'s request to reset their password. For more information, see ForgotPassword.

The confirmation code sent by a user\'s request to confirm registration.

The verification code in the request to verify user attributes.

Contextual user data type used for evaluating the risk of an unexpected event by Amazon Cognito advanced security.

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.

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.

Represents the request to create the user import job.

Represents the response from the server to the request to create the user import job.

Represents the request to create a user pool client.

Represents the response from the server to create a user pool client.

Represents the request to create a user pool.

Represents the response from the server for the request to create a user pool.

A schema attribute of the name type.

An array of custom attributes, such as Mutable and Name.

The configuration for a custom domain that hosts the sign-up and sign-in webpages for your application.

The configuration for a custom domain that hosts the sign-up and sign-in webpages for your application.

Provide this parameter only if you want to use a custom domain for your user pool. Otherwise, you can exclude this parameter and use the Amazon Cognito hosted domain instead.

For more information about the hosted domain and custom domains, see Configuring a User Pool Domain.

The configuration for a custom domain that hosts the sign-up and sign-in webpages for your application.

The configuration for a custom domain that hosts the sign-up and sign-in pages for your application. Use this object to specify an SSL certificate that is managed by ACM.

A custom email sender Lambda configuration type.

A custom email sender Lambda trigger.

Signature of the "request" attribute in the "event" information Amazon Cognito passes to your custom email Lambda function. The only supported value is V1_0.

A custom SMS sender Lambda configuration type.

A custom SMS sender Lambda trigger.

Signature of the "request" attribute in the "event" information that Amazon Cognito passes to your custom SMS Lambda function. The only supported value is V1_0.

The date the user was created.

The date the user was last modified.

The creation date

The creation date of the device.

The last modified date of the device.

The date when the device was last authenticated.

The event feedback date.

The date the group was last modified.

The date the group was created.

The date the IdP was last modified.

The date the IdP was created.

The date the provider was last modified.

The date the provider was added to the user pool.

The last modified date.

The last-modified date for the UI customization.

The creation date for the UI customization.

The date the user import job was created.

The date when the user import job was started.

The date when the user import job was completed.

The date the user pool client was last modified.

The date the user pool client was created.

The date the user pool description was last modified.

The date the user pool description was created.

The date the user pool was last modified.

The date the user pool was created.

The creation date of the user.

The last modified date of the user.

The default email option.

Represents the request to delete user attributes.

Represents the response from the server to delete user attributes.

Represents the request to delete a user pool client.

Represents the request to delete a user pool.

Represents the request to delete a user.

When active, DeletionProtection prevents accidental deletion of your user pool. Before you can delete a user pool that you have protected against deletion, you must deactivate this feature.

When you try to delete a protected user pool in a DeleteUserPool API request, Amazon Cognito returns an InvalidParameterException error. To delete a protected user pool, send a new DeleteUserPool request after you deactivate deletion protection in an UpdateUserPool API request.

When active, DeletionProtection prevents accidental deletion of your user pool. Before you can delete a user pool that you have protected against deletion, you must deactivate this feature.

When you try to delete a protected user pool in a DeleteUserPool API request, Amazon Cognito returns an InvalidParameterException error. To delete a protected user pool, send a new DeleteUserPool request after you deactivate deletion protection in an UpdateUserPool API request.

When active, DeletionProtection prevents accidental deletion of your user pool. Before you can delete a user pool that you have protected against deletion, you must deactivate this feature.

When you try to delete a protected user pool in a DeleteUserPool API request, Amazon Cognito returns an InvalidParameterException error. To delete a protected user pool, send a new DeleteUserPool request after you deactivate deletion protection in an UpdateUserPool API request.

Specify "EMAIL" if email will be used to send the welcome message. Specify "SMS" if the phone number will be used. The default value is "SMS". You can specify more than one value.

The method that Amazon Cognito used to send the code.

The delivery medium to send the MFA code. You can use this parameter to set only the SMS delivery medium value.

Represents the request to describe the user import job.

Represents the response from the server to the request to describe the user import job.

Represents the request to describe a user pool client.

Represents the response from the server from a request to describe the user pool client.

Represents the request to describe the user pool.

Represents the response to describe the user pool.

A string containing the description of the group.

A string containing the description of the group.

A string containing the new description of the group.

The device-remembering configuration for a user pool. A DescribeUserPool request returns a null value for this object when the user pool isn\'t configured to remember devices. When device remembering is active, you can remember a user\'s device with a ConfirmDevice API request. Additionally. when the property DeviceOnlyRememberedOnUserPrompt is true, you must follow ConfirmDevice with an UpdateDeviceStatus API request that sets the user\'s device to remembered or not_remembered.

To sign in with a remembered device, include DEVICE_KEY in the authentication parameters in your user\'s InitiateAuth request. If your app doesn\'t include a DEVICE_KEY parameter, the response from Amazon Cognito includes newly-generated DEVICE_KEY and DEVICE_GROUP_KEY values under NewDeviceMetadata. Store these values to use in future device-authentication requests.

The device-remembering configuration for a user pool. A null value indicates that you have deactivated device remembering in your user pool.

The device-remembering configuration for a user pool. A null value indicates that you have deactivated device remembering in your user pool.

The device-remembering configuration for a user pool. A null value indicates that you have deactivated device remembering in your user pool.

The device key.

The device key.

The device key.

The device key.

The device key.

The device key.

The device key.

The device key.

The device key.

The devices in the list of devices response.

The devices returned in the list devices response.

The device name.

The status indicating whether a device has been remembered or not.

The status of whether a device is remembered.

The device verifier against which it is authenticated.

The configuration of the device secret verifier.

The device type.

The device.

The device.

A container for information about a domain.

A domain description object containing information about the domain.

The domain status.

The domain string. For custom domains, this is the fully-qualified domain name, such as auth.example.com. For Amazon Cognito prefix domains, this is the prefix alone, such as auth.

The Amazon CloudFront endpoint that you use as the target of the alias that you set up with your Domain Name Service (DNS) provider.

The domain string. For custom domains, this is the fully-qualified domain name, such as auth.example.com. For Amazon Cognito prefix domains, this is the prefix alone, such as auth.

The domain string. For custom domains, this is the fully-qualified domain name, such as auth.example.com. For Amazon Cognito prefix domains, this is the prefix alone, such as auth.

The domain string. For custom domains, this is the fully-qualified domain name, such as auth.example.com. For Amazon Cognito prefix domains, this is the prefix alone, such as auth.

The domain name for the custom domain that hosts the sign-up and sign-in pages for your application. One example might be auth.example.com.

This string can include only lowercase letters, numbers, and hyphens. Don\'t use a hyphen for the first or last character. Use periods to separate subdomain names.

The Amazon CloudFront endpoint that Amazon Cognito set up when you added the custom domain to your user pool.

The domain prefix, if the user pool has a domain associated with it.

A custom domain name that you provide to Amazon Cognito. This parameter applies only if you use a custom domain to host the sign-up and sign-in pages for your application. An example of a custom domain name might be auth.example.com.

For more information about adding a custom domain to your user pool, see Using Your Own Domain for the Hosted UI.

The app version.

This exception is thrown when the provider is already supported by the user pool.

The destination to which the receiver of the email should reply.

The email configuration of your user pool. The email configuration type sets your preferred sending method, Amazon Web Services Region, and sender for messages from your user pool.

The email configuration of your user pool. The email configuration type sets your preferred sending method, Amazon Web Services Region, and sender for messages from your user pool.

The email configuration of your user pool. The email configuration type sets your preferred sending method, Amazon Web Services Region, and sender for email invitation and verification messages from your user pool.

The email configuration of your user pool. The email configuration type sets your preferred sending method, Amazon Web Services Region, and sender for messages tfrom your user pool.

The email HTML body.

The email text body.

The email subject.

Specifies whether Amazon Cognito uses its built-in functionality to send your users email messages, or uses your Amazon Simple Email Service email configuration. Specify one of the following values:

COGNITO_DEFAULT

When Amazon Cognito emails your users, it uses its built-in email functionality. When you use the default option, Amazon Cognito allows only a limited number of emails each day for your user pool. For typical production environments, the default email limit is less than the required delivery volume. To achieve a higher delivery volume, specify DEVELOPER to use your Amazon SES email configuration.

To look up the email delivery limit for the default option, see Limits in the Amazon Cognito Developer Guide.

The default FROM address is no-reply@verificationemail.com. To customize the FROM address, provide the Amazon Resource Name (ARN) of an Amazon SES verified email address for the SourceArn parameter.

DEVELOPER

When Amazon Cognito emails your users, it uses your Amazon SES configuration. Amazon Cognito calls Amazon SES on your behalf to send email from your verified email address. When you use this option, the email delivery limits are the same limits that apply to your Amazon SES verified email address in your Amazon Web Services account.

If you use this option, provide the ARN of an Amazon SES verified email address for the SourceArn parameter.

Before Amazon Cognito can email your users, it requires additional permissions to call Amazon SES on your behalf. When you update your user pool with this option, Amazon Cognito creates a service-linked role, which is a type of role in your Amazon Web Services account. This role contains the permissions that allow you to access Amazon SES and send email messages from your email address. For more information about the service-linked role that Amazon Cognito creates, see Using Service-Linked Roles for Amazon Cognito in the Amazon Cognito Developer Guide.

The email message template for sending a confirmation link to the user. You can set an EmailMessageByLink template only if the value of EmailSendingAccount is DEVELOPER. When your EmailSendingAccount is DEVELOPER, your user pool sends email messages with your own Amazon SES configuration.

This parameter is no longer used. See VerificationMessageTemplateType.

The message template for email messages. EmailMessage is allowed only if EmailSendingAccount is DEVELOPER.

This parameter is no longer used. See VerificationMessageTemplateType.

This parameter is no longer used. See VerificationMessageTemplateType.

The template for email messages that Amazon Cognito sends to your users. You can set an EmailMessage template only if the value of EmailSendingAccount is DEVELOPER. When your EmailSendingAccount is DEVELOPER, your user pool sends email messages with your own Amazon SES configuration.

The subject line for the email message template for sending a confirmation link to the user. You can set an EmailSubjectByLink template only if the value of EmailSendingAccount is DEVELOPER. When your EmailSendingAccount is DEVELOPER, your user pool sends email messages with your own Amazon SES configuration.

This parameter is no longer used. See VerificationMessageTemplateType.

The subject line for email messages. EmailSubject is allowed only if EmailSendingAccount is DEVELOPER.

This parameter is no longer used. See VerificationMessageTemplateType.

This parameter is no longer used. See VerificationMessageTemplateType.

The subject line for the email message template. You can set an EmailSubject template only if the value of EmailSendingAccount is DEVELOPER. When your EmailSendingAccount is DEVELOPER, your user pool sends email messages with your own Amazon SES configuration.

This exception is thrown when there is a code mismatch and the service fails to configure the software token TOTP multi-factor authentication (MFA).

Specifies the user context data captured at the time of an event request.

The user context data captured at the time of an event request. This value provides additional information about the client from which event the request is received.

Specifies the event feedback type.

A flag specifying the user feedback captured at the time of an event request is good or bad.

Perform the action for these events. The default is to perform all events if no event filter is specified.

The authentication event ID.

The event ID.

The event response.

The event risk type.

The event risk.

The event type.

This exception is thrown if a code has expired.

The authentication flows that you want your user pool client to support. For each app client in your user pool, you can sign in your users with any combination of one or more flows, including with a user name and Secure Remote Password (SRP), a user name and password, or a custom authentication process that you define with Lambda functions.

Valid values include:

• ALLOW_ADMIN_USER_PASSWORD_AUTH: Enable admin based user password authentication flow ADMIN_USER_PASSWORD_AUTH. This setting replaces the ADMIN_NO_SRP_AUTH setting. With this authentication flow, your app passes a user name and password to Amazon Cognito in the request, instead of using the Secure Remote Password (SRP) protocol to securely transmit the password.

• ALLOW_CUSTOM_AUTH: Enable Lambda trigger based authentication.

• ALLOW_USER_PASSWORD_AUTH: Enable user password-based authentication. In this flow, Amazon Cognito receives the password in the request instead of using the SRP protocol to verify passwords.

• ALLOW_USER_SRP_AUTH: Enable SRP-based authentication.

• ALLOW_REFRESH_TOKEN_AUTH: Enable authflow to refresh tokens.

In some environments, you will see the values ADMIN_NO_SRP_AUTH, CUSTOM_AUTH_FLOW_ONLY, or USER_PASSWORD_AUTH. You can\'t assign these legacy ExplicitAuthFlows values to user pool clients at the same time as values that begin with ALLOW_, like ALLOW_USER_SRP_AUTH.

The authentication flows that you want your user pool client to support. For each app client in your user pool, you can sign in your users with any combination of one or more flows, including with a user name and Secure Remote Password (SRP), a user name and password, or a custom authentication process that you define with Lambda functions.

Valid values include:

• ALLOW_ADMIN_USER_PASSWORD_AUTH: Enable admin based user password authentication flow ADMIN_USER_PASSWORD_AUTH. This setting replaces the ADMIN_NO_SRP_AUTH setting. With this authentication flow, your app passes a user name and password to Amazon Cognito in the request, instead of using the Secure Remote Password (SRP) protocol to securely transmit the password.

• ALLOW_CUSTOM_AUTH: Enable Lambda trigger based authentication.

• ALLOW_USER_PASSWORD_AUTH: Enable user password-based authentication. In this flow, Amazon Cognito receives the password in the request instead of using the SRP protocol to verify passwords.

• ALLOW_USER_SRP_AUTH: Enable SRP-based authentication.

• ALLOW_REFRESH_TOKEN_AUTH: Enable authflow to refresh tokens.

In some environments, you will see the values ADMIN_NO_SRP_AUTH, CUSTOM_AUTH_FLOW_ONLY, or USER_PASSWORD_AUTH. You can\'t assign these legacy ExplicitAuthFlows values to user pool clients at the same time as values that begin with ALLOW_, like ALLOW_USER_SRP_AUTH.

The authentication flows that you want your user pool client to support. For each app client in your user pool, you can sign in your users with any combination of one or more flows, including with a user name and Secure Remote Password (SRP), a user name and password, or a custom authentication process that you define with Lambda functions.

Valid values include:

• ALLOW_ADMIN_USER_PASSWORD_AUTH: Enable admin based user password authentication flow ADMIN_USER_PASSWORD_AUTH. This setting replaces the ADMIN_NO_SRP_AUTH setting. With this authentication flow, your app passes a user name and password to Amazon Cognito in the request, instead of using the Secure Remote Password (SRP) protocol to securely transmit the password.

• ALLOW_CUSTOM_AUTH: Enable Lambda trigger based authentication.

• ALLOW_USER_PASSWORD_AUTH: Enable user password-based authentication. In this flow, Amazon Cognito receives the password in the request instead of using the SRP protocol to verify passwords.

• ALLOW_USER_SRP_AUTH: Enable SRP-based authentication.

• ALLOW_REFRESH_TOKEN_AUTH: Enable authflow to refresh tokens.

In some environments, you will see the values ADMIN_NO_SRP_AUTH, CUSTOM_AUTH_FLOW_ONLY, or USER_PASSWORD_AUTH. You can\'t assign these legacy ExplicitAuthFlows values to user pool clients at the same time as values that begin with ALLOW_, like ALLOW_USER_SRP_AUTH.

The authentication event feedback value.

The event feedback value.

The authentication event feedback value.

This exception is thrown when WAF doesn\'t allow your request based on a web ACL that\'s associated with your user pool.

This parameter is used only if the phone_number_verified or email_verified attribute is set to True. Otherwise, it is ignored.

If this parameter is set to True and the phone number or email address specified in the UserAttributes parameter already exists as an alias with a different user, the API call will migrate the alias from the previous user to the newly created user. The previous user will no longer be able to log in using that alias.

If this parameter is set to False, the API throws an AliasExistsException error if the alias already exists. The default value is False.

Boolean to be specified to force user confirmation irrespective of existing alias. By default set to False. If this parameter is set to True and the phone number/email used for sign up confirmation already exists as an alias with a different user, the API call will migrate the alias from the previous user to the newly created user being confirmed. If set to False, the API will throw an AliasExistsException error.

Represents the request to forget the device.

Represents the request to reset a user\'s password.

The response from Amazon Cognito to a request to reset a password.

Boolean to specify whether you want to generate a secret for the user pool client being created.

Represents the request to get the header information of the CSV file for the user import job.

Represents the response from the server to the request to get the header information of the CSV file for the user import job.

Represents the request to get the device.

Gets the device response.

Request to get a signing certificate from Amazon Cognito.

Response from Amazon Cognito for a signing certificate request.

Represents the request to get user attribute verification.

The verification code response returned by the server response to get the user attribute verification code.

Represents the request to get information about the user.

Represents the response from the server from the request to get information about the user.

Represents the request to sign out all devices.

The response to the request to sign out all devices.

This exception is thrown when Amazon Cognito encounters a group that already exists in the user pool.

The groups that the user belongs to.

The group objects for the groups.

The group name.

The group name.

The name of the group. Must be unique.

The name of the group.

The name of the group.

The name of the group.

The name of the group.

The name of the group.

The group type.

The group object for the group.

The group object for the group.

The group object for the group.

The application ID for an Amazon Pinpoint application.

The HTTP header.

HttpHeaders received on your server in same order.

The ID token time limit. After this limit expires, your user can\'t use their ID token. To specify the time unit for IdTokenValidity as seconds, minutes, hours, or days, set a TokenValidityUnits value in your API request.

For example, when you set IdTokenValidity as 10 and TokenValidityUnits as hours, your user can authenticate their session with their ID token for 10 hours.

The default time unit for AccessTokenValidity in an API request is hours. Valid range is displayed below in seconds.

If you don\'t specify otherwise in the configuration of your app client, your ID tokens are valid for one hour.

The ID token time limit. After this limit expires, your user can\'t use their ID token. To specify the time unit for IdTokenValidity as seconds, minutes, hours, or days, set a TokenValidityUnits value in your API request.

For example, when you set IdTokenValidity as 10 and TokenValidityUnits as hours, your user can authenticate their session with their ID token for 10 hours.

The default time unit for AccessTokenValidity in an API request is hours. Valid range is displayed below in seconds.

If you don\'t specify otherwise in the configuration of your app client, your ID tokens are valid for one hour.

The ID token time limit. After this limit expires, your user can\'t use their ID token. To specify the time unit for IdTokenValidity as seconds, minutes, hours, or days, set a TokenValidityUnits value in your API request.

For example, when you set IdTokenValidity as 10 and TokenValidityUnits as hours, your user can authenticate their session with their ID token for 10 hours.

The default time unit for AccessTokenValidity in an API request is hours. Valid range is displayed below in seconds.

If you don\'t specify otherwise in the configuration of your app client, your ID tokens are valid for one hour.

A container for information about an IdP.

The newly created IdP object.

The identity provider details.

The identity provider details.

The identity provider details.

The IdP type.

The IdP type.

The IdP type.

The IdP identifier.

A list of IdP identifiers.

A list of IdP identifiers.

A list of IdP identifiers.

The uploaded logo image for the UI customization.

The logo image for the UI customization.

Initiates the authentication request.

Initiates the authentication response.

The expiration period of the authentication result in seconds.

A number estimating the size of the user pool.

This exception is thrown when Amazon Cognito encounters an internal error.

This exception is thrown when Amazon Cognito isn\'t allowed to use your email identity. HTTP status code: 400.

This exception is thrown when Amazon Cognito encounters an invalid Lambda response.

This exception is thrown when the specified OAuth flow is not valid.

This exception is thrown when the Amazon Cognito service encounters an invalid parameter.

This exception is thrown when Amazon Cognito encounters an invalid password.

This exception is returned when the role provided for SMS configuration doesn\'t have permission to publish using Amazon SNS.

This exception is thrown when the trust relationship is not valid for the role provided for SMS configuration. This can happen if you don\'t trust cognito-idp.amazonaws.com or the external ID provided in the role does not match what is provided in the SMS configuration for the user pool.

This exception is thrown when the user pool configuration is not valid.

Specifies the configuration for Lambda triggers.

The Lambda trigger configuration information for the new user pool.

The Lambda configuration information from the request to update the user pool.

The Lambda configuration information in a user pool description.

The Lambda triggers associated with the user pool.

This exception is thrown when a user exceeds the limit for a requested Amazon Web Services resource.

Represents the request to list the devices.

Represents the response to list devices.

The header information of the CSV file for the user import job.

The maximum number of IdPs to return.

The maximum number of resource servers to return.

Represents the request to list the user import jobs.

Represents the response from the server to the request to list the user import jobs.

Represents the request to list the user pool clients.

Represents the response from the server that lists user pool clients.

Represents the request to list user pools.

Represents the response to list user pools.

Represents the request to list users.

The response from the request to list users.

A list of allowed logout URLs for the IdPs.

A list of allowed logout URLs for the IdPs.

A list of allowed logout URLs for the IdPs.

The number of users that were successfully imported.

The number of users that were skipped.

The number of users that couldn\'t be imported.

This exception is thrown when Amazon Cognito can\'t find a multi-factor authentication (MFA) method.

This response parameter is no longer supported. It provides information only about SMS MFA configurations. It doesn\'t provide information about time-based one-time password (TOTP) software token MFA configurations. To look up information about either type of MFA configuration, use UserMFASettingList instead.

You can use this parameter only to set an SMS configuration that uses SMS for delivery.

This response parameter is no longer supported. It provides information only about SMS MFA configurations. It doesn\'t provide information about time-based one-time password (TOTP) software token MFA configurations. To look up information about either type of MFA configuration, use UserMFASettingList instead.

You can use this parameter only to set an SMS configuration that uses SMS for delivery.

The MFA options for the user.

This data type is no longer supported. Applies only to SMS multi-factor authentication (MFA) configurations. Does not apply to time-based one-time password (TOTP) software token MFA configurations.

Set to RESEND to resend the invitation message to a user that already exists and reset the expiration limit on the user\'s account. Set to SUPPRESS to suppress sending the message. You can specify only one value.

The message template structure.

The message template to be used for the welcome message to new users.

See also Customizing User Invitation Messages.

The message that Amazon Cognito sends to the user when the value of an alias attribute is already linked to another user profile.

The message sent when a verification code fails to deliver successfully.

The message provided when the code mismatch exception is thrown.

The message provided when the concurrent exception is thrown.

The message returned when the expired code exception is thrown.

The message returned when WAF doesn\'t allow your request based on a web ACL that\'s associated with your user pool.

The message returned when Amazon Cognito throws an internal error exception.

The message returned when you have an unverified email address or the identity policy isn\'t set on an email address that Amazon Cognito can access.

The message returned when Amazon Cognito throws an invalid Lambda response exception.

The message returned when the Amazon Cognito service throws an invalid parameter exception.

The message returned when Amazon Cognito throws an invalid user password exception.

The message returned when the invalid SMS role access policy exception is thrown.

The message returned when the role trust relationship for the SMS message is not valid.

The message returned when the user pool configuration is not valid.

The message returned when Amazon Cognito throws a limit exceeded exception.

The message returned when Amazon Cognito throws an MFA method not found exception.

The message returned when the Amazon Cognito service returns a not authorized exception.

The message returned when a password reset is required.

The message returned when a precondition is not met.

The message returned when the Amazon Cognito service returns a resource not found exception.

The message returned when Amazon Cognito returns a TooManyFailedAttempts exception.

The message returned when the Amazon Cognito service returns a too many requests exception.

The message returned when Amazon Cognito returns an unexpected Lambda exception.

The message returned when the user is in an unsupported state.

The message returned when the user pool has an import job running.

The message returned when the Amazon Cognito service returns a user validation exception with the Lambda service.

The message returned when a user isn\'t confirmed successfully.

The message returned when a user isn\'t found.

The message returned when Amazon Cognito throws a user name exists exception.

The new device metadata type.

The new device metadata from an authentication result.

This exception is thrown when a user isn\'t authorized.

The notify configuration type.

The notify configuration used to construct email notifications.

The notify email type.

Email template used when a detected risk event is blocked.

The email template used when a detected risk event is allowed.

The multi-factor authentication (MFA) email template used when MFA is challenged as part of a detected risk.

The minimum and maximum values of an attribute that is of the number data type.

Specifies the constraints for an attribute of the number type.

The allowed OAuth flows.

code

Use a code grant flow, which provides an authorization code as the response. This code can be exchanged for access tokens with the /oauth2/token endpoint.

implicit

Issue the access token (and, optionally, ID token, based on scopes) directly to your user.

client_credentials

Issue the access token from the /oauth2/token endpoint directly to a non-person user using a combination of the client ID and client secret.

The allowed OAuth flows.

code

Use a code grant flow, which provides an authorization code as the response. This code can be exchanged for access tokens with the /oauth2/token endpoint.

implicit

Issue the access token (and, optionally, ID token, based on scopes) directly to your user.

client_credentials

Issue the access token from the /oauth2/token endpoint directly to a non-person user using a combination of the client ID and client secret.

The allowed OAuth flows.

code

Use a code grant flow, which provides an authorization code as the response. This code can be exchanged for access tokens with the /oauth2/token endpoint.

implicit

Issue the access token (and, optionally, ID token, based on scopes) directly to your user.

client_credentials

Issue the access token from the /oauth2/token endpoint directly to a non-person user using a combination of the client ID and client secret.

An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list.

An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list.

A pagination token.

A pagination token.

An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list.

An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list.

An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list.

An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list.

An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list.

An identifier that you can use in a later request to return the next set of items in the list.

A pagination token.

A pagination token.

A pagination token.

A pagination token.

An identifier that was returned from the previous call to ListUserImportJobs, which can be used to return the next set of import jobs in the list.

An identifier that can be used to return the next set of user import jobs in the list.

An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list.

An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list.

The minimum length of the password in the policy that you have set. This value can\'t be less than 6.

The password policy type.

The password policy.

This exception is thrown when a password reset is required.

The user\'s temporary password. This password must conform to the password policy that you specified when you created the user pool.

The temporary password is valid only once. To complete the Admin Create User flow, the user must enter the temporary password in the sign-in page, along with a new password to be used in all future sign-ins.

This parameter isn\'t required. If you don\'t specify a value, Amazon Cognito generates one for you.

The temporary password can only be used until the user account expiration limit that you specified when you created the user pool. To reset the account after that time limit, you must call AdminCreateUser again, specifying "RESEND" for the MessageAction parameter.

The password for the user.

The old password.

The new password.

The new password that your user wants to set.

The password of the user you want to register.

The maximum number of import jobs you want the request to return.

The maximum number of results you want the request to return when listing the user pools.

The pre-signed URL to be used to upload the .csv file.

A non-negative integer value that specifies the precedence of this group relative to the other groups that a user can belong to in the user pool. Zero is the highest precedence value. Groups with lower Precedence values take precedence over groups with higher or null Precedence values. If a user belongs to two or more groups, it is the group with the lowest precedence value whose role ARN is given in the user\'s tokens for the cognito:roles and cognito:preferred_role claims.

Two groups can have the same Precedence value. If this happens, neither group takes precedence over the other. If two groups with the same Precedence have the same role ARN, that role is used in the cognito:preferred_role claim in tokens for users in each group. If the two groups have different role ARNs, the cognito:preferred_role claim isn\'t set in users\' tokens.

The default Precedence value is null. The maximum Precedence value is 2^31-1.

A non-negative integer value that specifies the precedence of this group relative to the other groups that a user can belong to in the user pool. Zero is the highest precedence value. Groups with lower Precedence values take precedence over groups with higher ornull Precedence values. If a user belongs to two or more groups, it is the group with the lowest precedence value whose role ARN is given in the user\'s tokens for the cognito:roles and cognito:preferred_role claims.

Two groups can have the same Precedence value. If this happens, neither group takes precedence over the other. If two groups with the same Precedence have the same role ARN, that role is used in the cognito:preferred_role claim in tokens for users in each group. If the two groups have different role ARNs, the cognito:preferred_role claim isn\'t set in users\' tokens.

The default Precedence value is null.

The new precedence value for the group. For more information about this parameter, see CreateGroup.

This exception is thrown when a precondition is not met.

Errors and responses that you want Amazon Cognito APIs to return during authentication, account confirmation, and password recovery when the user doesn\'t exist in the user pool. When set to ENABLED and the user doesn\'t exist, authentication returns an error indicating either the username or password was incorrect. Account confirmation and password recovery return a response indicating a code was sent to a simulated destination. When set to LEGACY, those APIs return a UserNotFoundException exception if the user doesn\'t exist in the user pool.

Valid values include:

• ENABLED - This prevents user existence-related errors.

• LEGACY - This represents the early behavior of Amazon Cognito where user existence related errors aren\'t prevented.

Errors and responses that you want Amazon Cognito APIs to return during authentication, account confirmation, and password recovery when the user doesn\'t exist in the user pool. When set to ENABLED and the user doesn\'t exist, authentication returns an error indicating either the username or password was incorrect. Account confirmation and password recovery return a response indicating a code was sent to a simulated destination. When set to LEGACY, those APIs return a UserNotFoundException exception if the user doesn\'t exist in the user pool.

Valid values include:

• ENABLED - This prevents user existence-related errors.

• LEGACY - This represents the early behavior of Amazon Cognito where user existence related errors aren\'t prevented.

Errors and responses that you want Amazon Cognito APIs to return during authentication, account confirmation, and password recovery when the user doesn\'t exist in the user pool. When set to ENABLED and the user doesn\'t exist, authentication returns an error indicating either the username or password was incorrect. Account confirmation and password recovery return a response indicating a code was sent to a simulated destination. When set to LEGACY, those APIs return a UserNotFoundException exception if the user doesn\'t exist in the user pool.

Valid values include:

• ENABLED - This prevents user existence-related errors.

• LEGACY - This represents the old behavior of Amazon Cognito where user existence related errors aren\'t prevented.

A positive integer specifying priority of a method with 1 being the highest priority.

A container for IdP details.

The IdP details. The following list describes the provider detail keys for each IdP type.

• For Google and Login with Amazon:

  • client_id

  • client_secret

  • authorize_scopes

• For Facebook:

  • client_id

  • client_secret

  • authorize_scopes

  • api_version

• For Sign in with Apple:

  • client_id

  • team_id

  • key_id

  • private_key

  • authorize_scopes

• For OpenID Connect (OIDC) providers:

  • client_id

  • client_secret

  • attributes_request_method

  • oidc_issuer

  • authorize_scopes

  • The following keys are only present if Amazon Cognito didn\'t discover them at the oidc_issuer URL.

    • authorize_url

    • token_url

    • attributes_url

    • jwks_uri

  • Amazon Cognito sets the value of the following keys automatically. They are read-only.

    • attributes_url_add_attributes

• For SAML providers:

  • MetadataFile or MetadataURL

  • IDPSignout optional

The IdP details. The following list describes the provider detail keys for each IdP type.

• For Google and Login with Amazon:

  • client_id

  • client_secret

  • authorize_scopes

• For Facebook:

  • client_id

  • client_secret

  • authorize_scopes

  • api_version

• For Sign in with Apple:

  • client_id

  • team_id

  • key_id

  • private_key

    You can submit a private_key when you add or update an IdP. Describe operations don\'t return the private key.

  • authorize_scopes

• For OIDC providers:

  • client_id

  • client_secret

  • attributes_request_method

  • oidc_issuer

  • authorize_scopes

  • The following keys are only present if Amazon Cognito didn\'t discover them at the oidc_issuer URL.

    • authorize_url

    • token_url

    • attributes_url

    • jwks_uri

  • Amazon Cognito sets the value of the following keys automatically. They are read-only.

    • attributes_url_add_attributes

• For SAML providers:

  • MetadataFile or MetadataURL

  • IDPSignout optional

The IdP details to be updated, such as MetadataURL and MetadataFile.

The IdP name.

The IdP name.

The IdP name.

The IdP name.

The name of the provider, such as Facebook, Google, or Login with Amazon.

The IdP name.

The IdP name.

A container for information about an IdP for a user pool.

The user to be disabled.

The existing user in the user pool that you want to assign to the external IdP user account. This user can be a native (Username + Password) Amazon Cognito user pools user or a federated user (for example, a SAML or Facebook user). If the user doesn\'t exist, Amazon Cognito generates an exception. Amazon Cognito returns this user when the new user (with the linked IdP attribute) signs in.

For a native username + password user, the ProviderAttributeValue for the DestinationUser should be the username in the user pool. For a federated user, it should be the provider-specific user_id.

The ProviderAttributeName of the DestinationUser is ignored.

The ProviderName should be set to Cognito for users in Cognito user pools.

An external IdP account for a user who doesn\'t exist yet in the user pool. This user must be a federated user (for example, a SAML or Facebook user), not another native user.

If the SourceUser is using a federated social IdP, such as Facebook, Google, or Login with Amazon, you must set the ProviderAttributeName to Cognito_Subject. For social IdPs, the ProviderName will be Facebook, Google, or LoginWithAmazon, and Amazon Cognito will automatically parse the Facebook, Google, and Login with Amazon tokens for id, sub, and user_id, respectively. The ProviderAttributeValue for the user must be the same value as the id, sub, or user_id value found in the social IdP token.

For SAML, the ProviderAttributeName can be any value that matches a claim in the SAML assertion. If you want to link SAML users based on the subject of the SAML assertion, you should map the subject to a claim through the SAML IdP and submit that claim name as the ProviderAttributeName. If you set ProviderAttributeName to Cognito_Subject, Amazon Cognito will automatically parse the default unique identifier found in the subject from the SAML token.

A list of IdP objects.

The maximum number of results you want the request to return when listing the user pool clients.

The limit of the devices request.

The limit of the request to list groups.

The maximum number of authentication events to return. Returns 60 events if you set MaxResults to 0, or if you don\'t include a MaxResults parameter.

The limit of the device request.

The limit of the request to list groups.

The limit of the request to list users.

Maximum number of users to be returned.

The list of RecoveryOptionTypes.

The recovery method for a user.

A map containing a priority as a key, and recovery method name as a value.

The default redirect URI. Must be in the CallbackURLs list.

A redirect URI must:

• Be an absolute URI.

• Be registered with the authorization server.

• Not include a fragment component.

See OAuth 2.0 - Redirection Endpoint.

Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only.

App callback URLs such as myapp://example are also supported.

The default redirect URI. Must be in the CallbackURLs list.

A redirect URI must:

• Be an absolute URI.

• Be registered with the authorization server.

• Not include a fragment component.

See OAuth 2.0 - Redirection Endpoint.

Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only.

App callback URLs such as myapp://example are also supported.

The default redirect URI. Must be in the CallbackURLs list.

A redirect URI must:

• Be an absolute URI.

• Be registered with the authorization server.

• Not include a fragment component.

See OAuth 2.0 - Redirection Endpoint.

Amazon Cognito requires HTTPS over HTTP except for http://localhost for testing purposes only.

App callback URLs such as myapp://example are also supported.

The refresh token time limit. After this limit expires, your user can\'t use their refresh token. To specify the time unit for RefreshTokenValidity as seconds, minutes, hours, or days, set a TokenValidityUnits value in your API request.

For example, when you set RefreshTokenValidity as 10 and TokenValidityUnits as days, your user can refresh their session and retrieve new access and ID tokens for 10 days.

The default time unit for RefreshTokenValidity in an API request is days. You can\'t set RefreshTokenValidity to 0. If you do, Amazon Cognito overrides the value with the default value of 30 days. Valid range is displayed below in seconds.

If you don\'t specify otherwise in the configuration of your app client, your refresh tokens are valid for 30 days.

The refresh token time limit. After this limit expires, your user can\'t use their refresh token. To specify the time unit for RefreshTokenValidity as seconds, minutes, hours, or days, set a TokenValidityUnits value in your API request.

For example, when you set RefreshTokenValidity as 10 and TokenValidityUnits as days, your user can refresh their session and retrieve new access and ID tokens for 10 days.

The default time unit for RefreshTokenValidity in an API request is days. You can\'t set RefreshTokenValidity to 0. If you do, Amazon Cognito overrides the value with the default value of 30 days. Valid range is displayed below in seconds.

If you don\'t specify otherwise in the configuration of your app client, your refresh tokens are valid for 30 days.

The refresh token time limit. After this limit expires, your user can\'t use their refresh token. To specify the time unit for RefreshTokenValidity as seconds, minutes, hours, or days, set a TokenValidityUnits value in your API request.

For example, when you set RefreshTokenValidity as 10 and TokenValidityUnits as days, your user can refresh their session and retrieve new access and ID tokens for 10 days.

The default time unit for RefreshTokenValidity in an API request is days. You can\'t set RefreshTokenValidity to 0. If you do, Amazon Cognito overrides the value with the default value of 30 days. Valid range is displayed below in seconds.

If you don\'t specify otherwise in the configuration of your app client, your refresh tokens are valid for 30 days.

The Amazon Web Services Region to use with Amazon SNS integration. You can choose the same Region as your user pool, or a supported Legacy Amazon SNS alternate Region.

Amazon Cognito resources in the Asia Pacific (Seoul) Amazon Web Services Region must use your Amazon SNS configuration in the Asia Pacific (Tokyo) Region. For more information, see SMS message settings for Amazon Cognito user pools.

Represents the request to resend the confirmation code.

The response from the server when Amazon Cognito makes the request to resend a confirmation code.

This exception is thrown when the Amazon Cognito service can\'t find the requested resource.

A unique resource server identifier for the resource server. This could be an HTTPS endpoint where the resource server is located, such as https://my-weather-api.example.com.

The identifier for the resource server.

The identifier for the resource server

The identifier for the resource server.

The identifier for the resource server.

A friendly name for the resource server.

The name of the resource server.

The name of the resource server.

A description of the scope.

A list of scopes. Each scope is a key-value map with the keys name and description.

A list of scopes that are defined for the resource server.

The scope values to be set for the resource server.

The name of the scope.

A resource server scope.

A container for information about a resource server for a user pool.

The newly created resource server.

The resource server.

The resource server.

The resource servers.

The request to respond to an authentication challenge.

The response to respond to the authentication challenge.

The risk configuration type.

The risk configuration.

The risk configuration.

The risk decision.

The type of the configuration to override the risk decision.

The configuration to override the risk decision.

The configuration to override the risk decision.

The risk level.

The Amazon S3 bucket where the static files for this domain are stored.

The set of configuration rules that can be applied to emails sent using Amazon Simple Email Service. A configuration set is applied to an email by including a reference to the configuration set in the headers of the email. Once applied, all of the rules in that configuration set are applied to the email. Configuration sets can be used to apply the following types of rules to emails:

Event publishing

Amazon Simple Email Service can track the number of send, delivery, open, click, bounce, and complaint events for each email sent. Use event publishing to send information about these events to other Amazon Web Services services such as and Amazon CloudWatch

IP pool management

When leasing dedicated IP addresses with Amazon Simple Email Service, you can create groups of IP addresses, called dedicated IP pools. You can then associate the dedicated IP pools with configuration sets.

The type used for enabling SMS multi-factor authentication (MFA) at the user level. Phone numbers don\'t need to be verified to be used for SMS MFA. If an MFA type is activated for a user, the user will be prompted for MFA during all sign-in attempts, unless device tracking is turned on and the device has been trusted. If you would like MFA to be applied selectively based on the assessed risk level of sign-in attempts, deactivate MFA for users and turn on Adaptive Authentication for the user pool.

The SMS text message MFA settings.

The SMS text message multi-factor authentication (MFA) settings.

Contains information about the schema attribute.

An array of schema attributes for the new user pool. These attributes can be standard or custom attributes.

A container with the schema attributes of a user pool.

This exception is thrown when the specified scope doesn\'t exist.

The allowed OAuth scopes. Possible values provided by OAuth are phone, email, openid, and profile. Possible values provided by Amazon Web Services are aws.cognito.signin.user.admin. Custom scopes created in Resource Servers are also supported.

The allowed OAuth scopes. Possible values provided by OAuth are phone, email, openid, and profile. Possible values provided by Amazon Web Services are aws.cognito.signin.user.admin. Custom scopes created in Resource Servers are also supported.

The OAuth scopes that your app client supports. Possible values that OAuth provides are phone, email, openid, and profile. Possible values that Amazon Web Services provides are aws.cognito.signin.user.admin. Amazon Cognito also supports custom scopes that you create in Resource Servers.

The pagination token.

The pagination token.

The pagination token for the list request.

The pagination token for the list device response.

An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list.

An identifier that was returned from the previous call to this operation, which can be used to return the next set of items in the list.

An array of strings, where each string is the name of a user attribute to be returned for each user in the search results. If the array is null, all attributes are returned.

A unique generated shared secret code that is used in the TOTP algorithm to generate a one-time code.

A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and username plus the client ID in the message.

A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and username plus the client ID in the message.

A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and username plus the client ID in the message.

A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and username plus the client ID in the message.

A keyed-hash message authentication code (HMAC) calculated using the secret key of a user pool client and username plus the client ID in the message.

The session that should be passed both ways in challenge-response calls to the service. If AdminInitiateAuth or AdminRespondToAuthChallenge 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 AdminRespondToAuthChallenge API call.

The session that should be passed both ways in challenge-response calls to the service. If an InitiateAuth or RespondToAuthChallenge API call determines that the caller must pass another challenge, it returns a session with other challenge parameters. This session should be passed as it is to the next RespondToAuthChallenge API call.

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 RespondToAuthChallenge API call.

The session that should be passed both ways in challenge-response calls to the service. This allows authentication of the user as part of the MFA setup process.

The session that should be passed both ways in challenge-response calls to the service. This allows authentication of the user as part of the MFA setup process.

The session that should pass 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 RespondToAuthChallenge API call.

The session that should be passed both ways in challenge-response calls to the service. If InitiateAuth or RespondToAuthChallenge 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 RespondToAuthChallenge API call.

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 RespondToAuthChallenge API call.

The session that should be passed both ways in challenge-response calls to the service.

The session that should be passed both ways in challenge-response calls to the service.

Represents the request to set user settings.

The response from the server for a set user settings request.

Represents the request to register a user.

The response from the server for a registration request.

Risk detection isn\'t performed on the IP addresses in this range list. The IP range is in CIDR notation.

The SMS configuration type is the settings that your Amazon Cognito user pool must use to send an SMS message from your Amazon Web Services account through Amazon Simple Notification Service. To send SMS messages with Amazon SNS in the Amazon Web Services Region that you want, the Amazon Cognito user pool uses an Identity and Access Management (IAM) role in your Amazon Web Services account.

The SMS configuration with the settings that your Amazon Cognito user pool must use to send an SMS message from your Amazon Web Services account through Amazon Simple Notification Service. To send SMS messages with Amazon SNS in the Amazon Web Services Region that you want, the Amazon Cognito user pool uses an Identity and Access Management (IAM) role in your Amazon Web Services account.

The SMS configuration with the settings that your Amazon Cognito user pool must use to send an SMS message from your Amazon Web Services account through Amazon Simple Notification Service. To request Amazon SNS in the Amazon Web Services Region that you want, the Amazon Cognito user pool uses an Identity and Access Management (IAM) role that you provide for your Amazon Web Services account.

The SMS configuration with the settings that your Amazon Cognito user pool must use to send an SMS message from your Amazon Web Services account through Amazon Simple Notification Service. To send SMS messages with Amazon SNS in the Amazon Web Services Region that you want, the Amazon Cognito user pool uses an Identity and Access Management (IAM) role in your Amazon Web Services account.

The SMS configuration with the settings that your Amazon Cognito user pool must use to send an SMS message from your Amazon Web Services account through Amazon Simple Notification Service. To send SMS messages with Amazon SNS in the Amazon Web Services Region that you want, the Amazon Cognito user pool uses an Identity and Access Management (IAM) role in your Amazon Web Services account.

The SMS text message multi-factor authentication (MFA) configuration type.

The SMS text message multi-factor authentication (MFA) configuration.

The SMS text message MFA configuration.

The SMS text message MFA configuration.

This parameter is no longer used. See VerificationMessageTemplateType.

A string representing the SMS authentication message.

The message template for SMS messages.

The SMS authentication message that will be sent to users with the code they must sign in. The message must contain the ‘{####}’ placeholder, which is replaced with the code. If the message isn\'t included, and default message will be used.

This parameter is no longer used. See VerificationMessageTemplateType.

The contents of the SMS authentication message.

This parameter is no longer used. See VerificationMessageTemplateType.

The contents of the SMS authentication message.

The template for SMS messages that Amazon Cognito sends to your users.

This exception is thrown when the software token time-based one-time password (TOTP) multi-factor authentication (MFA) isn\'t activated for the user pool.

The one- time password computed using the secret code returned by AssociateSoftwareToken.

The type used for enabling software token MFA at the user pool level.

The software token multi-factor authentication (MFA) configuration.

The software token MFA configuration.

The software token MFA configuration.

The type used for enabling software token MFA at the user level. If an MFA type is activated for a user, the user will be prompted for MFA during all sign-in attempts, unless device tracking is turned on and the device has been trusted. If you want MFA to be applied selectively based on the assessed risk level of sign-in attempts, deactivate MFA for users and turn on Adaptive Authentication for the user pool.

The time-based one-time password software token MFA settings.

The time-based one-time password (TOTP) software token MFA settings.

Represents the request to start the user import job.

Represents the response from the server to the request to start the user import job.

The user pool status in a user pool description.

The status of a user pool.

Represents the request to stop the user import job.

Represents the response from the server to the request to stop the user import job.

The constraints associated with a string attribute.

Specifies the constraints for an attribute of the string type.

The user pool ID for the user pool.

The user\'s preferred MFA setting.

The user pool ID for the user pool.

The external ID.

The endpoint ID.

The event ID.

The token type.

The email address or phone number destination where Amazon Cognito sent the code.

The source IP address of your user\'s device.

Your server endpoint where this API is invoked.

Your server path where this API is invoked.

Encoded device-fingerprint details that your app collected with the Amazon Cognito context data collection library. For more information, see Adding user device and session data to API requests.

The password verifier.

The salt

The Amazon Resource Name (ARN) of the Amazon CloudFront distribution.

Either the sender’s email address or the sender’s name with their email address. For example, testuser@example.com or Test User <testuser@example.com>. This address appears before the body of the email.

The source IP address of your user\'s device.

The user\'s device name.

The user\'s time zone.

The user\'s city.

The user\'s country.

The provider.

The signing certificate.

The user\'s preferred MFA setting.

The header name.

The header value.

The device group key.

The email address that is sending the email. The address must be either individually verified with Amazon Simple Email Service, or from a domain that has been verified with Amazon SES.

The destination to which the receiver of an email should reply to.

The minimum value of an attribute that is of the number data type.

The maximum value of an attribute that is of the number data type.

The name of the provider attribute to link to, such as NameID.

The value of the provider attribute to link to, such as xxxxx_account.

The UUID of the authenticated user. This isn\'t the same as username.

The external ID provides additional security for your IAM role. You can use an ExternalId with the IAM role that you use with Amazon SNS to send SMS messages for your user pool. If you provide an ExternalId, your Amazon Cognito user pool includes it in the request to assume your IAM role. You can configure the role trust policy to require that Amazon Cognito, and any principal, provide the ExternalID. If you use the Amazon Cognito Management Console to create a role for SMS multi-factor authentication (MFA), Amazon Cognito creates a role with the required permissions and a trust policy that demonstrates use of the ExternalId.

For more information about the ExternalId of a role, see How to use an external ID when granting access to your Amazon Web Services resources to a third party

The minimum length.

The maximum length.

The source IP address of your user\'s device.

Encoded device-fingerprint details that your app collected with the Amazon Cognito context data collection library. For more information, see Adding user device and session data to API requests.

The reason why the SMS configuration can\'t send the messages to your users.

This message might include comma-separated values to describe why your SMS configuration can\'t send messages to user pool end users.

InvalidSmsRoleAccessPolicyException

The Identity and Access Management role that Amazon Cognito uses to send SMS messages isn\'t properly configured. For more information, see SmsConfigurationType.

SNSSandbox

The Amazon Web Services account is in the SNS SMS Sandbox and messages will only reach verified end users. This parameter won’t get populated with SNSSandbox if the IAM user creating the user pool doesn’t have SNS permissions. To learn how to move your Amazon Web Services account out of the sandbox, see Moving out of the SMS sandbox.

Deprecated. Review error codes from API requests with EventSource:cognito-idp.amazonaws.com in CloudTrail for information about problems with user pool email configuration.

The friendly device name.

A list of provider names for the identity providers (IdPs) that are supported on this client. The following are supported: COGNITO, Facebook, Google, SignInWithApple, and LoginWithAmazon. You can also specify the names that you configured for the SAML and OIDC IdPs in your user pool, for example MySAMLIdP or MyOIDCIdP.

A list of provider names for the IdPs that this client supports. The following are supported: COGNITO, Facebook, Google, SignInWithApple, LoginWithAmazon, and the names of your own SAML and OIDC providers.

A list of provider names for the IdPs that this client supports. The following are supported: COGNITO, Facebook, Google, SignInWithApple, LoginWithAmazon, and the names of your own SAML and OIDC providers.

The number of days a temporary password is valid in the password policy. If the user doesn\'t sign in during this time, an administrator must reset their password.

A time unit of seconds, minutes, hours, or days for the value that you set in the AccessTokenValidity parameter. The default AccessTokenValidity time unit is hours.

A time unit of seconds, minutes, hours, or days for the value that you set in the IdTokenValidity parameter. The default IdTokenValidity time unit is hours.

A time unit of seconds, minutes, hours, or days for the value that you set in the RefreshTokenValidity parameter. The default RefreshTokenValidity time unit is days.

A valid access token that Amazon Cognito issued to the user whose software token you want to generate.

A valid access token that Amazon Cognito issued to the user who you want to authenticate.

The refresh token.

The ID token.

A valid access token that Amazon Cognito issued to the user whose password you want to change.

A valid access token that Amazon Cognito issued to the user whose device you want to confirm.

A valid access token that Amazon Cognito issued to the user whose attributes you want to delete.

A valid access token that Amazon Cognito issued to the user whose user profile you want to delete.

A valid access token that Amazon Cognito issued to the user whose registered device you want to forget.

A valid access token that Amazon Cognito issued to the user whose device information you want to request.

A non-expired access token for the user whose attribute verification code you want to generate.

A non-expired access token for the user whose information you want to query.

A valid access token that Amazon Cognito issued to the user who you want to sign out.

A valid access token that Amazon Cognito issued to the user whose list of devices you want to view.

The refresh token that you want to revoke.

A valid access token that Amazon Cognito issued to the user whose MFA preference you want to set.

A valid access token that Amazon Cognito issued to the user whose user settings you want to configure.

The feedback token.

A valid access token that Amazon Cognito issued to the user whose device status you want to update.

A valid access token that Amazon Cognito issued to the user whose user attributes you want to update.

A valid access token that Amazon Cognito issued to the user whose software token you want to verify.

A valid access token that Amazon Cognito issued to the user whose user attributes you want to verify.

The data type TokenValidityUnits specifies the time units you use when you set the duration of ID, access, and refresh tokens.

The units in which the validity times are represented. The default unit for RefreshToken is days, and default for ID and access tokens are hours.

The units in which the validity times are represented. The default unit for RefreshToken is days, and the default for ID and access tokens is hours.

The time units used to specify the token validity times of each token type: ID, access, and refresh.

This exception is thrown when the user has made too many failed attempts for a given action, such as sign-in.

This exception is thrown when the user has made too many requests for a given operation.

A container for the UI customization information for a user pool\'s built-in app UI.

The UI customization information.

The UI customization information.

Exception that is thrown when the request isn\'t authorized. This can happen due to an invalid access token in the request.

This exception is thrown when Amazon Cognito encounters an unexpected exception with Lambda.

This exception is thrown when the specified identifier isn\'t supported.

Exception that is thrown when you attempt to perform an operation that isn\'t enabled for the user pool client.

Exception that is thrown when an unsupported token is passed to an operation.

The request failed because the user is in an unsupported state.

Represents the request to update the device status.

The response to the request to update the device status.

Represents the request to update user attributes.

Represents the response from the server for the request to update user attributes.

Represents the request to update the user pool client.

Represents the response from the server to the request to update the user pool client.

The UpdateUserPoolDomain request input.

The UpdateUserPoolDomain response output.

Represents the request to update the user pool.

Represents the response from the server when you make a request to update the user pool.

The settings for updates to user attributes. These settings include the property AttributesRequireVerificationBeforeUpdate, a user-pool setting that tells Amazon Cognito how to handle changes to the value of your users\' email address and phone number attributes. For more information, see Verifying updates to email addresses and phone numbers.

The settings for updates to user attributes. These settings include the property AttributesRequireVerificationBeforeUpdate, a user-pool setting that tells Amazon Cognito how to handle changes to the value of your users\' email address and phone number attributes. For more information, see Verifying updates to email addresses and phone numbers.

The settings for updates to user attributes. These settings include the property AttributesRequireVerificationBeforeUpdate, a user-pool setting that tells Amazon Cognito how to handle changes to the value of your users\' email address and phone number attributes. For more information, see Verifying updates to email addresses and phone numbers.

The settings for updates to user attributes. These settings include the property AttributesRequireVerificationBeforeUpdate, a user-pool setting that tells Amazon Cognito how to handle changes to the value of your users\' email address and phone number attributes. For more information, see Verifying updates to email addresses and phone numbers.

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.

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.

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.

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.

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.

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.

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.

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.

A filter string of the form "AttributeName Filter-Type "AttributeValue"". Quotation marks within the filter string must be escaped using the backslash (\\) character. For example, "family_name = \\"Reddy\\"".

• AttributeName: The name of the attribute to search for. You can only search for one attribute at a time.

• Filter-Type: For an exact match, use =, for example, "given_name = \\"Jon\\"". For a prefix ("starts with") match, use ^=, for example, "given_name ^= \\"Jon\\"".

• AttributeValue: The attribute value that must be matched for each user.

If the filter string is empty, ListUsers returns all users in the user pool.

You can only search for the following standard attributes:

• username (case-sensitive)

• email

• phone_number

• name

• given_name

• family_name

• preferred_username

• cognito:user_status (called Status in the Console) (case-insensitive)

• status (called Enabled in the Console) (case-sensitive)

• sub

Custom attributes aren\'t searchable.

For more information, see Searching for Users Using the ListUsers API and Examples of Using the ListUsers API in the Amazon Cognito Developer Guide.

This exception is thrown when you\'re trying to modify a user pool while a user import job is in progress for that pool.

The job ID for the user import job.

The job ID for the user import job.

The job ID for the user import job.

The job ID for the user import job.

The job name for the user import job.

The job name for the user import job.

The status of the user import job. One of the following:

• Created - The job was created but not started.

• Pending - A transition state. You have started the job, but it has not begun importing users yet.

• InProgress - The job has started, and users are being imported.

• Stopping - You have stopped the job, but the job has not stopped importing users yet.

• Stopped - You have stopped the job, and the job has stopped importing users.

• Succeeded - The job has completed successfully.

• Failed - The job has stopped due to an error.

• Expired - You created a job, but did not start the job within 24-48 hours. All data associated with the job was deleted, and the job can\'t be started.

The user import job type.

The job object that represents the user import job.

The job object that represents the user import job.

The job object that represents the user import job.

The job object that represents the user import job.

The user import jobs.

This exception is thrown when the Amazon Cognito service encounters a user validation exception with the Lambda service.

The MFA options that are activated for the user. The possible values in this list are SMS_MFA and SOFTWARE_TOKEN_MFA.

The MFA options that are activated for the user. The possible values in this list are SMS_MFA and SOFTWARE_TOKEN_MFA.

This exception is thrown when a user isn\'t confirmed successfully.

This exception is thrown when a user isn\'t found.

This exception is thrown when user pool add-ons aren\'t enabled.

The user pool add-ons type.

Enables advanced security risk detection. Set the key AdvancedSecurityMode to the value "AUDIT".

Enables advanced security risk detection. Set the key AdvancedSecurityMode to the value "AUDIT".

The user pool add-ons.

The description of the user pool client.

The user pool clients in the response that lists user pool clients.

Contains information about a user pool client.

The user pool client that was just created.

The user pool client from a server response to describe the user pool client.

The user pool client value from the response from the server when you request to update the user pool client.

A user pool description.

The user pool ID for the user pool where you want to add custom attributes.

The user pool ID for the user pool.

The user pool ID for which you want to confirm user registration.

The user pool ID for the user pool where the user will be created.

The user pool ID for the user pool where you want to delete user attributes.

The user pool ID for the user pool where you want to delete the user.

The user pool ID for the user pool where you want to disable the user.

The user pool ID for the user pool where you want to enable the user.

The user pool ID.

The user pool ID.

The user pool ID for the user pool where you want to get information about the user.

The ID of the Amazon Cognito user pool.

The user pool ID.

The user pool ID for the user pool.

The user pool ID.

The user pool ID for the user pool.

The user pool ID for the user pool where you want to reset the user\'s password.

The ID of the Amazon Cognito user pool.

The user pool ID.

The user pool ID for the user pool where you want to set the user\'s password.

The ID of the user pool that contains the user whose options you\'re setting.

The user pool ID.

The user pool ID.

The user pool ID for the user pool where you want to update user attributes.

The user pool ID.

The user pool ID for the user pool.

The user pool ID.

The user pool ID for the user pool.

The user pool ID for the user pool that the users are being imported into.

The user pool ID for the user pool where you want to create a user pool client.

The user pool ID.

The user pool ID for the user pool.

The user pool ID.

The user pool ID for the user pool that hosts the resource server.

The user pool ID for the user pool where you want to delete the client.

The user pool ID.

The user pool ID for the user pool you want to delete.

The user pool ID.

The user pool ID for the user pool that hosts the resource server.

The user pool ID.

The user pool ID for the user pool that the users are being imported into.

The user pool ID for the user pool you want to describe.

The user pool ID for the user pool you want to describe.

The user pool ID.

The user pool ID for the user pool that the users are to be imported into.

The user pool ID for the user pool that the users are to be imported into.

The user pool ID for the user pool.

The user pool ID.

The user pool ID.

The user pool ID for the user pool.

The user pool ID.

The user pool ID for the user pool.

The user pool ID.

The user pool ID for the user pool.

The user pool ID.

The user pool ID for the user pool.

The user pool ID for the user pool that the users are being imported into.

The user pool ID for the user pool where you want to list user pool clients.

The user pool ID for the user pool.

The user pool ID for the user pool on which the search should be performed.

The user pool ID for the user pool that hosts the resource server.

The user pool ID.

The user pool ID.

The user pool ID for the user pool.

The user pool ID.

The user pool ID for the user pool that the users are being imported into.

The user pool ID for the user pool that the users are being imported into.

The user pool ID for the user pool.

The user pool ID.

The user pool ID for the user pool.

The user pool ID.

The user pool ID for the user pool.

The user pool ID for the user pool where you want to update the user pool client.

The ID of the user pool that is associated with the custom domain whose certificate you\'re updating.

The user pool ID for the user pool you want to update.

The user pool ID for the user pool that the users are being imported into.

The user pool ID for the user pool where you want to describe the user pool client.

The user pool ID for the user pool client.

The ID in a user pool description.

The ID of the user pool.

The user pools from the response to list users.

Specifies MFA configuration details.

The multi-factor authentication (MFA) configuration. Valid values include:

• OFF MFA won\'t be used for any users.

• ON MFA is required for all users to sign in.

• OPTIONAL MFA will be required only for individual users who have an MFA factor activated.

The MFA configuration. If you set the MfaConfiguration value to ‘ON’, only users who have set up an MFA factor can sign in. To learn more, see Adding Multi-Factor Authentication (MFA) to a user pool. Valid values include:

• OFF MFA won\'t be used for any users.

• ON MFA is required for all users to sign in.

• OPTIONAL MFA will be required only for individual users who have an MFA factor activated.

The MFA configuration. Valid values include:

• OFF MFA won\'t be used for any users.

• ON MFA is required for all users to sign in.

• OPTIONAL MFA will be required only for individual users who have an MFA factor enabled.

Possible values include:

• OFF - MFA tokens aren\'t required and can\'t be specified during user registration.

• ON - MFA tokens are required for all user registrations. You can only specify ON when you\'re initially creating a user pool. You can use the SetUserPoolMfaConfig API operation to turn MFA "ON" for existing user pools.

• OPTIONAL - Users have the option when registering to create an MFA token.

Can be one of the following values:

• OFF - MFA tokens aren\'t required and can\'t be specified during user registration.

• ON - MFA tokens are required for all user registrations. You can only specify required when you\'re initially creating a user pool.

• OPTIONAL - Users have the option when registering to create an MFA token.

A string used to name the user pool.

The name in a user pool description.

The name of the user pool.

The policy associated with a user pool.

The policies associated with the new user pool.

A container with the policies you want to update in a user pool.

The policies associated with the user pool.

This exception is thrown when a user pool tag can\'t be set or updated.

The keys of the tags to remove from the user pool.

The tag keys and values to assign to the user pool. A tag is a label that you can use to categorize and manage user pools in different ways, such as by purpose, owner, environment, or other criteria.

The tags that are assigned to the user pool.

The tags to assign to the user pool.

The tag keys and values to assign to the user pool. A tag is a label that you can use to categorize and manage user pools in different ways, such as by purpose, owner, environment, or other criteria.

The tags that are assigned to the user pool. A tag is a label that you can apply to user pools to categorize and manage them in different ways, such as by purpose, owner, environment, or other criteria.

A container for information about the user pool.

A container for the user pool details.

The container of metadata returned by the server to describe the pool.

The user status. Can be one of the following:

• UNCONFIRMED - User has been created but not confirmed.

• CONFIRMED - User has been confirmed.

• ARCHIVED - User is no longer active.

• UNKNOWN - User status isn\'t known.

• RESET_REQUIRED - User is confirmed, but the user must request a code and reset their password before they can sign in.

• FORCE_CHANGE_PASSWORD - The user is confirmed and the user can sign in using a temporary password, but on first sign-in, the user must change their password to a new value before doing anything else.

The user status. This can be one of the following:

• UNCONFIRMED - User has been created but not confirmed.

• CONFIRMED - User has been confirmed.

• EXTERNAL_PROVIDER - User signed in with a third-party IdP.

• ARCHIVED - User is no longer active.

• UNKNOWN - User status isn\'t known.

• RESET_REQUIRED - User is confirmed, but the user must request a code and reset their password before they can sign in.

• FORCE_CHANGE_PASSWORD - The user is confirmed and the user can sign in using a temporary password, but on first sign-in, the user must change their password to a new value before doing anything else.

A user profile in a Amazon Cognito user pool.

The newly created user.

Specifies whether a user can use an email address or phone number as a username when they sign up.

Specifies whether a user can use an email address or phone number as a username when they sign up.

The username configuration type.

Case sensitivity on the username input for the selected sign-in option. For example, when case sensitivity is set to False, users can sign in using either "username" or "Username". This configuration is immutable once it has been set. For more information, see UsernameConfigurationType.

Case sensitivity of the username input for the selected sign-in option. For example, when case sensitivity is set to False, users can sign in using either "username" or "Username". This configuration is immutable once it has been set. For more information, see UsernameConfigurationType.

This exception is thrown when Amazon Cognito encounters a user name that already exists in the user pool.

The username for the user.

The user name for which you want to confirm user registration.

The username for the user. Must be unique within the user pool. Must be a UTF-8 string between 1 and 128 characters. After the user is created, the username can\'t be changed.

The user name of the user from which you would like to delete attributes.

The user name of the user you want to delete.

The user name of the user you want to disable.

The user name of the user you want to enable.

The user name.

The user name.

The user name of the user you want to retrieve.

The user name of the user about whom you\'re receiving information.

The user name.

The username for the user.

The user pool username or an alias.

The username for the user.

The user name of the user whose password you want to reset.

The user pool username or alias.

The user name of the user whose password you want to set.

The user name of the user whose options you\'re setting.

The user pool username.

The user name.

The user name of the user for whom you want to update user attributes.

The user name.

The user name of the user for whom you want to enter a code to retrieve a forgotten password.

The user name of the user whose registration you want to confirm.

The user name of the user for whom you want to enter a code to reset a forgotten password.

The user name of the user you want to retrieve from the get user request.

The username attribute of the user to whom you want to resend a confirmation code.

The user name of the user you want to register.

The user pool username.

The user name of the user you want to describe.

The users returned in the request to list users.

The users returned in the request to list users.

The template for verification messages.

The template for the verification message that the user sees when the app requests permission to access the user\'s information.

The template for verification messages.

The template for verification messages.

The attributes to be auto-verified. Possible values: email, phone_number.

The attributes that are automatically verified when Amazon Cognito requests to update user pools.

The attributes that are auto-verified in a user pool.

The status of the verify software token.

Represents the request to verify user attributes.

A container representing the response from the server from the request to verify user attributes.

Activates or deactivates token revocation. For more information about revoking tokens, see RevokeToken.

If you don\'t include this parameter, token revocation is automatically activated for the new user pool client.

Activates the propagation of additional user context data. For more information about propagation of user context data, see Adding advanced security to a user pool. If you don’t include this parameter, you can\'t send device fingerprint information, including source IP address, to Amazon Cognito advanced security. You can only activate EnablePropagateAdditionalUserContextData in an app client that has a client secret.

Indicates whether compromised credentials were detected during an authentication event.

Activates or deactivates token revocation. For more information about revoking tokens, see RevokeToken.

Activates the propagation of additional user context data. For more information about propagation of user context data, see Adding advanced security to a user pool. If you don’t include this parameter, you can\'t send device fingerprint information, including source IP address, to Amazon Cognito advanced security. You can only activate EnablePropagateAdditionalUserContextData in an app client that has a client secret.

Indicates whether token revocation is activated for the user pool client. When you create a new user pool client, token revocation is activated by default. For more information about revoking tokens, see RevokeToken.

When EnablePropagateAdditionalUserContextData is true, Amazon Cognito accepts an IpAddress value that you send in the UserContextData parameter. The UserContextData parameter sends information to Amazon Cognito advanced security for risk analysis. You can send UserContextData when you sign in Amazon Cognito native users with the InitiateAuth and RespondToAuthChallenge API operations.

When EnablePropagateAdditionalUserContextData is false, you can\'t send your user\'s source IP address to Amazon Cognito advanced security with unauthenticated API operations. EnablePropagateAdditionalUserContextData doesn\'t affect whether you can send a source IP address in a ContextData parameter with the authenticated API operations AdminInitiateAuth and AdminRespondToAuthChallenge.

You can only activate EnablePropagateAdditionalUserContextData in an app client that has a client secret. For more information about propagation of user context data, see Adding user device and session data to API requests.

Specifies whether user name case sensitivity will be applied for all users in the user pool through Amazon Cognito APIs.

Valid values include:

True

Enables case sensitivity for all username input. When this option is set to True, users must sign in using the exact capitalization of their given username, such as “UserName”. This is the default value.

False

Enables case insensitivity for all username input. For example, when this option is set to False, users can sign in using either "username" or "Username". This option also enables both preferred_username and email alias to be case insensitive, in addition to the username attribute.