aws-sdk-cognitoidentityprovider 1.51.0 → 1.55.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6d3d64050f79e1fcb7d4883eca09cc07d23444b08f7c9d761904372451c9cebb
-  data.tar.gz: bd98c31f566339d42c190942a3ebeea3411b1c4351bb375b446a8efcc9474d07
+  metadata.gz: fedc103987a4d3119af6d33edf01c5380584d1e91006a184a6e7fb69d15a4258
+  data.tar.gz: e013698d7ec62c13e4c96572518a113236bf1282fc079e50818dabfcece53af6
 SHA512:
-  metadata.gz: e9f46f53363bea3ec058191702966534af925eb4e20d23f5f8689abf95b1ff58f8f5d55be5358919715d43a7f336dbac28b47981cbd5b8db857921c443303164
-  data.tar.gz: e5275ea362c4655546c887233ef8b5494f1e474903a769539b7b4f86a4ea97d76fa95bd287eb6df64d24921cc685d7f7f2e665be95619be61741ac7828b24e6e
+  metadata.gz: '05862d8f895fa37ce38ef7b235e491d550bafbc2479d156786701e562bde8cd5e54e28455c788fd371f185e731c3c142aca155a4698be2f2bb9d8f23caffe500'
+  data.tar.gz: 07d98630eea8ac53427d07d4da7ee94b7731c86dc311979729e305e607eef967706a9a8a7b45f3752f07ea54b0fca8c1e7da03fc19d6033cce9089d7be1a7384

data/CHANGELOG.md

@@ -1,6 +1,26 @@
 Unreleased Changes
 ------------------
 
+1.55.0 (2021-07-28)
+------------------
+
+* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
+
+1.54.0 (2021-07-15)
+------------------
+
+* Feature - Documentation updates for cognito-idp
+
+1.53.0 (2021-06-10)
+------------------
+
+* Feature - Amazon Cognito now supports targeted sign out through refresh token revocation
+
+1.52.0 (2021-06-08)
+------------------
+
+* Feature - Documentation updates for cognito-idp
+
 1.51.0 (2021-04-22)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.51.0
+1.55.0

data/lib/aws-sdk-cognitoidentityprovider.rb

@@ -48,6 +48,6 @@ require_relative 'aws-sdk-cognitoidentityprovider/customizations'
 # @!group service
 module Aws::CognitoIdentityProvider
 
-  GEM_VERSION = '1.51.0'
+  GEM_VERSION = '1.55.0'
 
 end

data/lib/aws-sdk-cognitoidentityprovider/client.rb

@@ -428,14 +428,14 @@ module Aws::CognitoIdentityProvider
     #   custom workflows that this action triggers.
     #
     #   If your user pool configuration includes triggers, the
-    #   AdminConfirmSignUp API action invokes the AWS Lambda function that is
+    #   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 AWS Lambda,
-    #   you can process the ClientMetadata value to enhance your workflow for
-    #   your specific needs.
+    #   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][1] in the *Amazon Cognito Developer Guide*.
@@ -444,9 +444,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -486,6 +486,27 @@ module Aws::CognitoIdentityProvider
     # If `MessageAction` is not set, the default is to send a welcome
     # message via email or phone (SMS).
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
     # 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
@@ -499,6 +520,11 @@ module Aws::CognitoIdentityProvider
     #
     # `AdminCreateUser` requires developer credentials.
     #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :user_pool_id
     #   The user pool ID for the user pool where the user will be created.
     #
@@ -604,14 +630,14 @@ module Aws::CognitoIdentityProvider
     #   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 AWS 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
+    #   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 AWS Lambda, you can process the `clientMetadata`
+    #   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
@@ -621,9 +647,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -1015,8 +1041,34 @@ module Aws::CognitoIdentityProvider
 
     # Initiates the authentication flow, as an administrator.
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
     # Calling this action requires developer credentials.
     #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :user_pool_id
     #   The ID of the Amazon Cognito user pool.
     #
@@ -1087,11 +1139,11 @@ module Aws::CognitoIdentityProvider
     #   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 AWS Lambda functions to user
-    #   pool triggers. When you use the AdminInitiateAuth API action, Amazon
-    #   Cognito invokes the AWS Lambda functions that are specified for
-    #   various triggers. The ClientMetadata value is passed as input to the
-    #   functions for only the following 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
     #
@@ -1103,9 +1155,9 @@ module Aws::CognitoIdentityProvider
     #   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 AWS Lambda, you
-    #   can process the `validationData` value to enhance your workflow for
-    #   your specific needs.
+    #   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 does not
@@ -1130,9 +1182,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -1526,8 +1578,34 @@ module Aws::CognitoIdentityProvider
     # in sending a message to the end user with the code to change their
     # password.
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
     # Calling this action requires developer credentials.
     #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :user_pool_id
     #   The user pool ID for the user pool where you want to reset the user's
     #   password.
@@ -1539,16 +1617,16 @@ module Aws::CognitoIdentityProvider
     #   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 AWS 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 AWS Lambda,
-    #   you can process the `clientMetadata` value to enhance your workflow
-    #   for your specific needs.
+    #   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][1] in the *Amazon Cognito Developer Guide*.
@@ -1557,9 +1635,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -1596,8 +1674,34 @@ module Aws::CognitoIdentityProvider
 
     # Responds to an authentication challenge, as an administrator.
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
     # Calling this action requires developer credentials.
     #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :user_pool_id
     #   The ID of the Amazon Cognito user pool.
     #
@@ -1659,9 +1763,9 @@ module Aws::CognitoIdentityProvider
     #   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 AWS Lambda functions to user
-    #   pool triggers. When you use the AdminRespondToAuthChallenge API
-    #   action, Amazon Cognito invokes any functions that are assigned to the
+    #   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 are assigned to the
     #   following triggers: *pre sign-up*, *custom message*, *post
     #   authentication*, *user migration*, *pre token generation*, *define
     #   auth challenge*, *create auth challenge*, and *verify auth challenge
@@ -1669,9 +1773,9 @@ module Aws::CognitoIdentityProvider
     #   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
-    #   AdminRespondToAuthChallenge request. In your function code in AWS
-    #   Lambda, you can process the `clientMetadata` value to enhance your
-    #   workflow for your specific needs.
+    #   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][1] in the *Amazon Cognito Developer Guide*.
@@ -1680,9 +1784,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -1974,8 +2078,34 @@ module Aws::CognitoIdentityProvider
     # In addition to updating user attributes, this API can also be used to
     # mark phone and email as verified.
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
     # Calling this action requires developer credentials.
     #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :user_pool_id
     #   The user pool ID for the user pool where you want to update user
     #   attributes.
@@ -1993,16 +2123,16 @@ module Aws::CognitoIdentityProvider
     #   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 AWS Lambda functions to user
-    #   pool triggers. When you use the AdminUpdateUserAttributes API action,
+    #   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 AWS
-    #   Lambda, you can process the `clientMetadata` value to enhance your
-    #   workflow for your specific needs.
+    #   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][1] in the *Amazon Cognito Developer Guide*.
@@ -2011,9 +2141,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -2089,6 +2219,16 @@ module Aws::CognitoIdentityProvider
     # account. The request takes an access token or a session string, but
     # not both.
     #
+    # <note markdown="1"> Calling AssociateSoftwareToken immediately disassociates the existing
+    # software token from the user account. If the user doesn't
+    # subsequently verify the software token, their account is essentially
+    # set up to authenticate without MFA. If MFA config is set to Optional
+    # at the user pool level, the user can then login without MFA. However,
+    # if MFA is set to Required for the user pool, the user will be asked to
+    # setup a new software token MFA during sign in.
+    #
+    #  </note>
+    #
     # @option params [String] :access_token
     #   The access token.
     #
@@ -2237,16 +2377,16 @@ module Aws::CognitoIdentityProvider
     #   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 AWS Lambda functions to user
-    #   pool triggers. When you use the ConfirmForgotPassword API action,
-    #   Amazon Cognito invokes the function that is assigned to the *post
+    #   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 AWS Lambda,
-    #   you can process the `clientMetadata` value to enhance your workflow
-    #   for your specific needs.
+    #   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][1] in the *Amazon Cognito Developer Guide*.
@@ -2255,9 +2395,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -2341,16 +2481,15 @@ module Aws::CognitoIdentityProvider
     #   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 AWS 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 AWS Lambda, you can
-    #   process the `clientMetadata` value to enhance your workflow for your
-    #   specific needs.
+    #   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][1] in the *Amazon Cognito Developer Guide*.
@@ -2359,9 +2498,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -2704,6 +2843,32 @@ module Aws::CognitoIdentityProvider
     # Creates a new Amazon Cognito user pool and sets the password policy
     # for the pool.
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :pool_name
     #   A string used to name the user pool.
     #
@@ -2723,7 +2888,7 @@ module Aws::CognitoIdentityProvider
     #    For more information on using the Lambda API to add permission, see [
     #   AddPermission ][1].
     #
-    #    For adding permission using the AWS CLI, see [ add-permission ][2].
+    #    For adding permission using the CLI, see [ add-permission ][2].
     #
     #    </note>
     #
@@ -3029,6 +3194,14 @@ module Aws::CognitoIdentityProvider
 
     # Creates the user pool client.
     #
+    # When you create a new user pool client, token revocation is
+    # automatically enabled. For more information about revoking tokens, see
+    # [RevokeToken][1].
+    #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_RevokeToken.html
+    #
     # @option params [required, String] :user_pool_id
     #   The user pool ID for the user pool where you want to create a user
     #   pool client.
@@ -3171,8 +3344,8 @@ module Aws::CognitoIdentityProvider
     # @option params [Array<String>] :allowed_o_auth_scopes
     #   The allowed OAuth scopes. Possible values provided by OAuth are:
     #   `phone`, `email`, `openid`, and `profile`. Possible values provided by
-    #   AWS are: `aws.cognito.signin.user.admin`. Custom scopes created in
-    #   Resource Servers are also supported.
+    #   Amazon Web Services are: `aws.cognito.signin.user.admin`. Custom
+    #   scopes created in Resource Servers are also supported.
     #
     # @option params [Boolean] :allowed_o_auth_flows_user_pool_client
     #   Set to true if the client is allowed to follow the OAuth protocol when
@@ -3213,6 +3386,17 @@ module Aws::CognitoIdentityProvider
     #
     #    </note>
     #
+    # @option params [Boolean] :enable_token_revocation
+    #   Enables or disables token revocation. For more information about
+    #   revoking tokens, see [RevokeToken][1].
+    #
+    #   If you don't include this parameter, token revocation is
+    #   automatically enabled for the new user pool client.
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_RevokeToken.html
+    #
     # @return [Types::CreateUserPoolClientResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
     #   * {Types::CreateUserPoolClientResponse#user_pool_client #user_pool_client} => Types::UserPoolClientType
@@ -3249,6 +3433,7 @@ module Aws::CognitoIdentityProvider
     #       user_data_shared: false,
     #     },
     #     prevent_user_existence_errors: "LEGACY", # accepts LEGACY, ENABLED
+    #     enable_token_revocation: false,
     #   })
     #
     # @example Response structure
@@ -3289,6 +3474,7 @@ module Aws::CognitoIdentityProvider
     #   resp.user_pool_client.analytics_configuration.external_id #=> String
     #   resp.user_pool_client.analytics_configuration.user_data_shared #=> Boolean
     #   resp.user_pool_client.prevent_user_existence_errors #=> String, one of "LEGACY", "ENABLED"
+    #   resp.user_pool_client.enable_token_revocation #=> Boolean
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/cognito-idp-2016-04-18/CreateUserPoolClient AWS API Documentation
     #
@@ -3905,6 +4091,7 @@ module Aws::CognitoIdentityProvider
     #   resp.user_pool_client.analytics_configuration.external_id #=> String
     #   resp.user_pool_client.analytics_configuration.user_data_shared #=> Boolean
     #   resp.user_pool_client.prevent_user_existence_errors #=> String, one of "LEGACY", "ENABLED"
+    #   resp.user_pool_client.enable_token_revocation #=> Boolean
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/cognito-idp-2016-04-18/DescribeUserPoolClient AWS API Documentation
     #
@@ -3986,10 +4173,33 @@ module Aws::CognitoIdentityProvider
     # `InvalidParameterException` is thrown. To use the confirmation code
     # for resetting the password, call [ConfirmForgotPassword][2].
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][3]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][4] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
     #
     #
     # [1]: https://docs.aws.amazon.com/cognito/latest/developerguide/how-to-recover-a-user-account.html
     # [2]: https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_ConfirmForgotPassword.html
+    # [3]: https://console.aws.amazon.com/pinpoint/home/
+    # [4]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
     #
     # @option params [required, String] :client_id
     #   The ID of the client associated with the user pool.
@@ -4016,15 +4226,15 @@ module Aws::CognitoIdentityProvider
     #   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 AWS 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
+    #   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 AWS Lambda, you can process the `clientMetadata`
+    #   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
@@ -4034,9 +4244,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -4354,6 +4564,32 @@ module Aws::CognitoIdentityProvider
     # Gets the user attribute verification code for the specified attribute
     # name.
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :access_token
     #   The access token returned by the server response to get the user
     #   attribute verification code.
@@ -4366,14 +4602,14 @@ module Aws::CognitoIdentityProvider
     #   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 AWS Lambda functions to user
-    #   pool triggers. When you use the GetUserAttributeVerificationCode API
+    #   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 AWS
+    #   GetUserAttributeVerificationCode request. In your function code in
     #   Lambda, you can process the `clientMetadata` value to enhance your
     #   workflow for your specific needs.
     #
@@ -4384,9 +4620,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -4490,6 +4726,32 @@ module Aws::CognitoIdentityProvider
 
     # Initiates the authentication flow.
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :auth_flow
     #   The authentication flow for this call to execute. The API action will
     #   depend on this value. For example:
@@ -4548,11 +4810,11 @@ module Aws::CognitoIdentityProvider
     #   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 AWS Lambda functions to user
-    #   pool triggers. When you use the InitiateAuth API action, Amazon
-    #   Cognito invokes the AWS Lambda functions that are specified for
-    #   various triggers. The ClientMetadata value is passed as input to the
-    #   functions for only the following 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
     #
@@ -4564,7 +4826,7 @@ module Aws::CognitoIdentityProvider
     #   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 AWS Lambda, you can process the
+    #   request. In your function code in Lambda, you can process the
     #   `validationData` value to enhance your workflow for your specific
     #   needs.
     #
@@ -4591,9 +4853,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -4991,7 +5253,7 @@ module Aws::CognitoIdentityProvider
       req.send_request(options)
     end
 
-    # Lists the user pools associated with an AWS account.
+    # Lists the user pools associated with an account.
     #
     # @option params [String] :next_token
     #   An identifier that was returned from the previous call to this
@@ -5226,6 +5488,32 @@ module Aws::CognitoIdentityProvider
     # Resends the confirmation (for confirmation of registration) to a
     # specific user in the user pool.
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :client_id
     #   The ID of the client associated with the user pool.
     #
@@ -5251,16 +5539,16 @@ module Aws::CognitoIdentityProvider
     #   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 AWS 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 AWS Lambda,
-    #   you can process the `clientMetadata` value to enhance your workflow
-    #   for your specific needs.
+    #   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][1] in the *Amazon Cognito Developer Guide*.
@@ -5269,9 +5557,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -5323,6 +5611,32 @@ module Aws::CognitoIdentityProvider
 
     # Responds to the authentication challenge.
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :client_id
     #   The app client ID.
     #
@@ -5385,18 +5699,18 @@ module Aws::CognitoIdentityProvider
     #   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 AWS 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 AWS Lambda,
-    #   you can process the `clientMetadata` value to enhance your workflow
-    #   for your specific needs.
+    #   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][1] in the *Amazon Cognito Developer Guide*.
@@ -5405,9 +5719,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -5471,6 +5785,39 @@ module Aws::CognitoIdentityProvider
       req.send_request(options)
     end
 
+    # Revokes all of the access tokens generated by the specified refresh
+    # token. After the token is revoked, you can not use the revoked token
+    # to access Cognito authenticated APIs.
+    #
+    # @option params [required, String] :token
+    #   The token that you want to revoke.
+    #
+    # @option params [required, String] :client_id
+    #   The client ID for the token that you want to revoke.
+    #
+    # @option params [String] :client_secret
+    #   The secret for the client ID. This is required only if the client ID
+    #   has a secret.
+    #
+    # @return [Struct] Returns an empty {Seahorse::Client::Response response}.
+    #
+    # @example Request syntax with placeholder values
+    #
+    #   resp = client.revoke_token({
+    #     token: "TokenModelType", # required
+    #     client_id: "ClientIdType", # required
+    #     client_secret: "ClientSecretType",
+    #   })
+    #
+    # @see http://docs.aws.amazon.com/goto/WebAPI/cognito-idp-2016-04-18/RevokeToken AWS API Documentation
+    #
+    # @overload revoke_token(params = {})
+    # @param [Hash] params ({})
+    def revoke_token(params = {}, options = {})
+      req = build_request(:revoke_token, params)
+      req.send_request(options)
+    end
+
     # Configures actions on detected risks. To delete the risk configuration
     # for `UserPoolId` or `ClientId`, pass null values for all four
     # configuration types.
@@ -5704,6 +6051,32 @@ module Aws::CognitoIdentityProvider
 
     # Set the user pool multi-factor authentication (MFA) configuration.
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :user_pool_id
     #   The user pool ID.
     #
@@ -5808,6 +6181,32 @@ module Aws::CognitoIdentityProvider
     # Registers the user in the specified user pool and creates a user name,
     # password, and user attributes.
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, String] :client_id
     #   The ID of the client associated with the user pool.
     #
@@ -5844,16 +6243,16 @@ module Aws::CognitoIdentityProvider
     #   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 AWS 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
+    #   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 AWS Lambda, you can process the `clientMetadata`
-    #   value to enhance your workflow for your specific needs.
+    #   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][1] in the *Amazon Cognito Developer Guide*.
@@ -5862,9 +6261,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -6170,9 +6569,6 @@ module Aws::CognitoIdentityProvider
     #
     # Calling this action requires developer credentials.
     #
-    # If you don't provide a value for an attribute, it will be set to the
-    # default value.
-    #
     # @option params [required, String] :group_name
     #   The name of the group.
     #
@@ -6342,6 +6738,32 @@ module Aws::CognitoIdentityProvider
 
     # Allows a user to update a specific attribute (one at a time).
     #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][1]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][2] in
+    # the *Amazon Cognito Developer Guide*.
+    #
+    #  </note>
+    #
+    #
+    #
+    # [1]: https://console.aws.amazon.com/pinpoint/home/
+    # [2]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
+    #
     # @option params [required, Array<Types::AttributeType>] :user_attributes
     #   An array of name-value pairs representing user attributes.
     #
@@ -6355,16 +6777,15 @@ module Aws::CognitoIdentityProvider
     #   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 AWS 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 AWS Lambda, you
-    #   can process the `clientMetadata` value to enhance your workflow for
-    #   your specific needs.
+    #   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][1] in the *Amazon Cognito Developer Guide*.
@@ -6373,9 +6794,9 @@ module Aws::CognitoIdentityProvider
     #   ClientMetadata parameter:
     #
     #    * Amazon Cognito does not store the ClientMetadata value. This data is
-    #     available only to AWS Lambda triggers that are assigned to a user
-    #     pool to support custom workflows. If your user pool configuration
-    #     does not include triggers, the ClientMetadata parameter serves no
+    #     available only to Lambda triggers that are assigned to a user pool
+    #     to support custom workflows. If your user pool configuration does
+    #     not include triggers, the ClientMetadata parameter serves no
     #     purpose.
     #
     #   * Amazon Cognito does not validate the ClientMetadata value.
@@ -6426,14 +6847,35 @@ module Aws::CognitoIdentityProvider
 
     # Updates the specified user pool with the specified attributes. You can
     # get a list of the current user pool settings using
-    # [DescribeUserPool][1].
+    # [DescribeUserPool][1]. If you don't provide a value for an attribute,
+    # it will be set to the default value.
+    #
+    # <note markdown="1"> This action might generate an SMS text message. Starting June 1, 2021,
+    # U.S. telecom carriers require that you register an origination phone
+    # number before you can send SMS messages to U.S. phone numbers. If you
+    # use SMS text messages in Amazon Cognito, you must register a phone
+    # number with [Amazon Pinpoint][2]. Cognito will use the the registered
+    # number automatically. Otherwise, Cognito users that must receive SMS
+    # messages might be unable to sign up, activate their accounts, or sign
+    # in.
+    #
+    #  If you have never used SMS text messages with Amazon Cognito or any
+    # other Amazon Web Service, Amazon SNS might place your account in SMS
+    # sandbox. In <i> <a
+    # href="https://docs.aws.amazon.com/sns/latest/dg/sns-sms-sandbox.html">sandbox
+    # mode</a> </i>, you’ll have limitations, such as sending messages to
+    # only verified phone numbers. After testing in the sandbox environment,
+    # you can move out of the SMS sandbox and into production. For more
+    # information, see [ SMS message settings for Cognito User Pools][3] in
+    # the *Amazon Cognito Developer Guide*.
     #
-    # If you don't provide a value for an attribute, it will be set to the
-    # default value.
+    #  </note>
     #
     #
     #
     # [1]: https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_DescribeUserPool.html
+    # [2]: https://console.aws.amazon.com/pinpoint/home/
+    # [3]: https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-identity-pools-sms-userpool-settings.html
     #
     # @option params [required, String] :user_pool_id
     #   The user pool ID for the user pool you want to update.
@@ -6442,8 +6884,8 @@ module Aws::CognitoIdentityProvider
     #   A container with the policies you wish to update in a user pool.
     #
     # @option params [Types::LambdaConfigType] :lambda_config
-    #   The AWS Lambda configuration information from the request to update
-    #   the user pool.
+    #   The Lambda configuration information from the request to update the
+    #   user pool.
     #
     # @option params [Array<String>] :auto_verified_attributes
     #   The attributes that are automatically verified when the Amazon Cognito
@@ -6619,9 +7061,14 @@ module Aws::CognitoIdentityProvider
     # If you don't provide a value for an attribute, it will be set to the
     # default value.
     #
+    # You can also use this operation to enable token revocation for user
+    # pool clients. For more information about revoking tokens, see
+    # [RevokeToken][2].
+    #
     #
     #
     # [1]: https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_DescribeUserPoolClient.html
+    # [2]: https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_RevokeToken.html
     #
     # @option params [required, String] :user_pool_id
     #   The user pool ID for the user pool where you want to update the user
@@ -6748,8 +7195,8 @@ module Aws::CognitoIdentityProvider
     # @option params [Array<String>] :allowed_o_auth_scopes
     #   The allowed OAuth scopes. Possible values provided by OAuth are:
     #   `phone`, `email`, `openid`, and `profile`. Possible values provided by
-    #   AWS are: `aws.cognito.signin.user.admin`. Custom scopes created in
-    #   Resource Servers are also supported.
+    #   Amazon Web Services are: `aws.cognito.signin.user.admin`. Custom
+    #   scopes created in Resource Servers are also supported.
     #
     # @option params [Boolean] :allowed_o_auth_flows_user_pool_client
     #   Set to true if the client is allowed to follow the OAuth protocol when
@@ -6790,6 +7237,14 @@ module Aws::CognitoIdentityProvider
     #
     #    </note>
     #
+    # @option params [Boolean] :enable_token_revocation
+    #   Enables or disables token revocation. For more information about
+    #   revoking tokens, see [RevokeToken][1].
+    #
+    #
+    #
+    #   [1]: https://docs.aws.amazon.com/cognito-user-identity-pools/latest/APIReference/API_RevokeToken.html
+    #
     # @return [Types::UpdateUserPoolClientResponse] Returns a {Seahorse::Client::Response response} object which responds to the following methods:
     #
     #   * {Types::UpdateUserPoolClientResponse#user_pool_client #user_pool_client} => Types::UserPoolClientType
@@ -6826,6 +7281,7 @@ module Aws::CognitoIdentityProvider
     #       user_data_shared: false,
     #     },
     #     prevent_user_existence_errors: "LEGACY", # accepts LEGACY, ENABLED
+    #     enable_token_revocation: false,
     #   })
     #
     # @example Response structure
@@ -6866,6 +7322,7 @@ module Aws::CognitoIdentityProvider
     #   resp.user_pool_client.analytics_configuration.external_id #=> String
     #   resp.user_pool_client.analytics_configuration.user_data_shared #=> Boolean
     #   resp.user_pool_client.prevent_user_existence_errors #=> String, one of "LEGACY", "ENABLED"
+    #   resp.user_pool_client.enable_token_revocation #=> Boolean
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/cognito-idp-2016-04-18/UpdateUserPoolClient AWS API Documentation
     #
@@ -6885,7 +7342,7 @@ module Aws::CognitoIdentityProvider
     #
     # 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 AWS
+    # 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.
     #
@@ -6899,7 +7356,7 @@ module Aws::CognitoIdentityProvider
     # 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 AWS Region.
+    # Virginia) as the Region.
     #
     # After you submit your request, Amazon Cognito requires up to 1 hour to
     # distribute your new certificate to your custom domain.
@@ -7048,7 +7505,7 @@ module Aws::CognitoIdentityProvider
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-cognitoidentityprovider'
-      context[:gem_version] = '1.51.0'
+      context[:gem_version] = '1.55.0'
       Seahorse::Client::Request.new(handlers, context)
     end