Note: If you create or update an SMS MFA configuration for your Cognito user pool, the Cognito service will send a test SMS message to an internal number in order to verify your configuration. You will be charged for these test messages by Amazon SNS. For information about Amazon SNS pricing, see [Worldwide SMS Pricing](https://aws.amazon.com/sns/sms-pricing/). There are a few ways to integrate phone numbers into an Amplify project's sign-in and verification process. - **As a username**\*: Users login with a username and password where their phone number acts as the username. - **As a verification method**: Users login by any means, but must verify their account with an OTP (one time password) sent to their phone. - **MFA (Multi-Factor Authentication)**: Users must verify every login with an OTP sent to their phone. \**Note: This is different from using a phone number [alias](https://docs.aws.amazon.com/cognito/latest/developerguide/user-pool-settings-attributes.html#user-pool-settings-aliases), which is currently unsupported by the Amplify CLI.* These methods may be combined with each other or used independently but they all require the same prerequisites for sending SMS messages via Amazon SNS, the notification service used by Amplify. ## Prerequisites ### Sandbox Mode Upon enabling any of the above settings in Amplify, the CLI may prompt you with the following message: ```bash You have enabled SMS based auth workflow. Verify your SNS account mode in the SNS console: https://console.aws.amazon.com/sns/v3/home#/mobile/text-messaging If your account is in "Sandbox" mode, you can only send SMS messages to verified recipient phone numbers. ``` Follow the [link](https://console.aws.amazon.com/sns/v3/home#/mobile/text-messaging) to visit your SNS account. If your account is in "Sandbox" mode, you'll need to verify a phone number before you're able to send SMS messages. ### Set up an Origination Entity If you see the following banner at the top of your SNS homepage, you'll need to perform some additional steps before adding a phone number. If not, you can skip to **Verify a Phone Number**.  Clicking **Manage origination entities** will bring you to Pinpoint, where you can register an [originating entity](https://docs.aws.amazon.com/sns/latest/dg/channels-sms-originating-identities.html). Depending on which country you'll be sending SMS messages from, you may choose to register either a **Sender ID** or an **Origination number**. > You can find the complete list of supported options for your country [here](https://docs.aws.amazon.com/pinpoint/latest/userguide/channels-sms-countries.html). #### Sender ID If your country supports using sender IDs, follow the instructions [here](https://docs.aws.amazon.com/pinpoint/latest/userguide/channels-sms-countries.html) to request one and enable it in your account. #### Origination number If your country does not support sender IDs, you must purchase an origination number. In Pinpoint, scroll to `Number settings` and click on **Request phone number**. This will bring you to a page where you can obtain a Toll-free number for sending SMS messages. Choose the country from which you'll be sending SMS messages, then follow the prompts for requesting a new number. After successfully requesting a toll-free number, you can return to SNS to verify your phone number. ### Verify a Phone Number Return to SNS, and scroll to the `Sandbox destination phone numbers` section. Click **Add phone number** and follow the instructions to verify your phone number. You are now ready to setup auth for OTP. ## Setup The following options are only available when starting a new project (via `amplify add auth`). You will not have access to these settings after creation (via `amplify update`). - Required MFA - Phone Number Sign-In Run `amplify add auth` to create a new Cognito Auth resource, and follow the prompts below depending on how you want to integrate phone numbers into your flow. ### As a username import all0 from "/src/fragments/lib-v1/auth/common/sms/add_username.mdx"; ### As a verification method import all1 from "/src/fragments/lib-v1/auth/common/sms/add_verification.mdx"; ### MFA import all2 from "/src/fragments/lib-v1/auth/common/sms/add_mfa.mdx"; Run `amplify update auth` and follow the prompts as guided below. ### As a username import all3 from "/src/fragments/lib-v1/auth/common/sms/update_username.mdx"; ### As a verification method import all4 from "/src/fragments/lib-v1/auth/common/sms/update_verification.mdx"; ### MFA import all5 from "/src/fragments/lib-v1/auth/common/sms/update_mfa.mdx"; ## Sign Up Sign up users normally with the chosen `Username` type and password. Certain attributes may be required in the `userAttributes` map depending on the options chosen above: - `"email"` is **required** if: - One of the following are true: - Email verification is enabled (default) - Email was marked as a required attribute (default) - **and** users sign up with a chosen username or phone number - `"phone_number"` is **required** if: - One of the following are true: - MFA is ON, or manually enabled for the user - Phone number verification is enabled - Phone number was marked as a required attribute - **and** users sign up with a chosen username or email import flutter6 from "/src/fragments/lib-v1/auth/flutter/sms/sign_up.mdx"; Verification of user accounts is done via the `confirmSignUp` method with the OTP sent to their phone or email. import flutter7 from "/src/fragments/lib-v1/auth/flutter/sms/confirm_sign_up.mdx"; ## Sign In Sign in users normally with the chosen `Username` type and password. import flutter8 from "/src/fragments/lib-v1/auth/flutter/sms/sign_in.mdx"; If MFA is **ON** or enabled for the user, you must call `confirmSignIn` with the OTP sent to their phone. import flutter9 from "/src/fragments/lib-v1/auth/flutter/sms/confirm_sign_in.mdx";