Step 3. Add Social Sign-in to a User Pool (Optional)

You can enable your app users to sign in through a social identity provider (IdP) such as Facebook, Google, and Login with Amazon. Whether your users sign in directly or through a third party, all users have a profile in the user pool. Skip this step if you don't want to add sign in through a social sign-in identity provider.

Before you create a social IdP with Amazon Cognito, you must register your application with the social IdP to receive a client ID and client secret.

Create a developer account with Facebook.
Sign in with your Facebook credentials.
From the My Apps menu, choose Create New App.
Give your Facebook app a name and choose Create App ID.
On the left navigation bar, choose Settings and then Basic.
Note the App ID and the App Secret. You will use them in the next section.
Choose + Add Platform from the bottom of the page.
Choose Website.
Under Website, type your user pool domain with the /oauth2/idpresponse endpoint into Site URL.
```
https://<your-user-pool-domain>/oauth2/idpresponse
```
Choose Save changes.
Type your user pool domain into App Domains.
```
https://<your-user-pool-domain>
```
Choose Save changes.
From the navigation bar choose Products and then Set up from Facebook Login.
From the navigation bar choose Facebook Login and then Settings.

Type your redirect URL into Valid OAuth Redirect URIs. It will consist of your user pool domain with the /oauth2/idpresponse endpoint.
```
https://<your-user-pool-domain>/oauth2/idpresponse
```
Choose Save changes.

Create a developer account with Amazon.
Sign in with your Amazon credentials.
You need to create an Amazon security profile to receive the Amazon client ID and client secret.

Choose Apps and Services from navigation bar at the top of the page and then choose Login with Amazon.
Choose Create a Security Profile.
Type in a Security Profile Name, a Security Profile Description, and a Consent Privacy Notice URL.
Choose Save.
Choose Client ID and Client Secret to show the client ID and secret. You will use them in the next section.
Hover over the gear and choose Web Settings, and then choose Edit.
Type your user pool domain into Allowed Origins.
```
https://<your-user-pool-domain>
```
Type your user pool domain with the /oauth2/idpresponse endpoint into Allowed Return URLs.
```
https://<your-user-pool-domain>/oauth2/idpresponse
```
Choose Save.

Create a developer account with Google.
Sign in with your Google credentials.
Choose CONFIGURE A PROJECT.
Type in a project name and choose NEXT.
Type in your product name and choose NEXT.
Choose Web browser from the Where are you calling from? drop-down list.
Type your user pool domain into Authorized JavaScript origins.
```
https://<your-user-pool-domain>
```
Choose CREATE. You will not use the Client ID and Client Secret from this step.
Choose DONE.
Sign in to the Google Console.
On the left navigation bar, choose Credentials.
Create your OAuth 2.0 credentials by choosing OAuth client ID from the Create credentials drop-down list.
Choose Web application.
Type your user pool domain into Authorized JavaScript origins.
```
https://<your-user-pool-domain>
```
Type your user pool domain with the /oauth2/idpresponse endpoint into Authorized Redirect URIs.
```
https://<your-user-pool-domain>/oauth2/idpresponse
```
Choose Create twice.
Note the OAuth client ID and client secret. You will need them for the next section.
Choose OK.

In this section, you configure a social IdP in your user pool using the client ID and client secret from the previous section.

To configure a user pool social identity provider with the AWS Management Console

Go to the Amazon Cognito console. You might be prompted for your AWS credentials.
Choose Manage your User Pools.
Choose an existing user pool from the list, or create a user pool.
On the left navigation bar, choose Identity providers.
Choose a social identity provider: Facebook, Google, or Login with Amazon.
Type the app client ID and app client secret that you received from the social identity provider in the previous section.

Type the names of the scopes that you want to authorize. Scopes define which user attributes (such as name and email) you want to access with your app. For Facebook, these should be separated by commas. For Google and Login with Amazon, they should be separated by spaces.

Social identity provider	Example scopes
Facebook	`public_profile, email`
Google	`profile email openid`
Login with Amazon	`profile postal_code`

Your app user is asked to consent to providing these attributes to your app. For more information about their scopes, see the documentation from Google, Facebook, and Login with Amazon.

Choose Enable for the social identity provider that you're configuring.
Choose App client settings from the navigation bar.
Select your social identity provider as one of the Enabled Identity Providers for your user pool app.
Type your callback URL into Callback URL(s) for your user pool app. This is the URL of the page where your user will be redirected after a successful sign-in.
```
https://www.example.com
```
Choose Save changes.
On the Attribute mapping tab, add mappings for at least the required attributes, typically email, as follows:
1. Select the check box to choose the Facebook, Google, or Amazon attribute name. You can also type the names of additional attributes that aren't listed in the Amazon Cognito console.
2. Choose the destination user pool attribute from the drop-down list.
3. Choose Save changes.
4. Choose Go to summary.

You can create a login URL by using the elements from the previous two sections. Use it to test your social IdP configuration.



https://your_user_pool_domain/login?response_type=code&client_id=your_client_id&redirect_uri=https://www.example.com

You can find your domain on the user pool Domain name console page. The client_id is on the App client settings page. Use your callback URL for the redirect_uri parameter. The callback URL address will be different from your user pool domain.

Step 4. Add Sign-in with a SAML Identity Provider to a User Pool (Optional)