Cognito for user authentication in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is AWS Cognito used for?

AWS Cognito is a service that helps you add user sign-up, sign-in, and access control to your web and mobile apps easily.

beginner

What are the two main components of AWS Cognito?

User Pools (for user directory and authentication) and Identity Pools (for temporary AWS credentials to access other AWS services).

intermediate

How does AWS Cognito User Pool help secure an application?

It manages user registration and sign-in, verifies user identities, and issues JSON Web Tokens (JWT) to control access securely.

intermediate

What is the role of Identity Pools in AWS Cognito?

Identity Pools provide temporary AWS credentials to users so they can access AWS resources like S3 or DynamoDB securely.

intermediate

Why is it important to configure app clients in Cognito User Pools?

App clients define how your app interacts with the user pool, including allowed authentication flows and token expiration settings.

Which AWS Cognito component manages user sign-up and sign-in?

A User Pool

B Identity Pool

C S3 Bucket

D Lambda Function

User Pools handle user registration and authentication.

What type of token does Cognito User Pool issue after successful authentication?

A JWT (JSON Web Token)

B API Key

C OAuth Token

D Session Cookie

Cognito User Pools issue JWTs to securely represent user identity.

What is the main purpose of an Identity Pool in AWS Cognito?

A Store user passwords

B Manage user groups

C Provide temporary AWS credentials

D Send email notifications

Identity Pools provide temporary AWS credentials for accessing AWS services.

Which of the following is NOT a feature of Cognito User Pools?

A User registration and sign-in

B Password recovery

C Multi-factor authentication

D Temporary AWS credentials for S3 access

Temporary AWS credentials are provided by Identity Pools, not User Pools.

Why should you configure app clients in a Cognito User Pool?

A To store user data

B To define how your app authenticates users

C To create AWS Lambda functions

D To manage billing

App clients specify authentication flows and token settings for your app.

Explain the difference between AWS Cognito User Pools and Identity Pools.

Think about authentication vs authorization roles.

Describe how AWS Cognito helps secure a mobile or web application.

Focus on user identity and access control.

Practice

1. What is the main purpose of AWS Cognito in user authentication?

easy

A. To manage user sign-up and sign-in securely

B. To store application data in the cloud

C. To create virtual servers for applications

D. To monitor network traffic

Solution

1. Step 1: Understand AWS Cognito's role

   AWS Cognito is designed to handle user authentication, including sign-up and sign-in processes securely.

2. Step 2: Compare options with Cognito's function

   Options A, B, and D describe other AWS services or functions unrelated to user authentication.

3. Final Answer:

   To manage user sign-up and sign-in securely -> Option A

4. Quick Check:

   Cognito = User sign-up/sign-in management [OK]

Hint: Remember: Cognito = user login management [OK]

Common Mistakes:

• Confusing Cognito with storage services
• Thinking Cognito manages servers
• Mixing Cognito with network monitoring

2. Which AWS Cognito component stores and verifies user information?

easy

A. Identity pool

B. User pool

C. Lambda function

D. API Gateway

Solution

1. Step 1: Identify the component for user data

   User pools in Cognito are designed to store and verify user information like usernames and passwords.

2. Step 2: Eliminate unrelated components

   Identity pools provide temporary AWS credentials, Lambda runs code, and API Gateway manages APIs, none store user info.

3. Final Answer:

   User pool -> Option B

4. Quick Check:

   User pool = stores user info [OK]

Hint: User pool = user info storage and verification [OK]

Common Mistakes:

• Confusing identity pool with user pool
• Thinking Lambda stores user data
• Mixing API Gateway with user management

3. Given this AWS CLI command:
aws cognito-idp create-user-pool-client --user-pool-id us-east-1_123456789 --client-name MyAppClient
What does this command do?

medium

A. Lists all user pools

B. Creates a new user pool

C. Deletes a user pool client

D. Creates a new user pool client for an existing user pool

Solution

1. Step 1: Analyze the command action

   The command uses 'create-user-pool-client' which creates a client app for an existing user pool identified by --user-pool-id.

2. Step 2: Understand the client role

   User pool clients connect apps to user pools for login; this command does not create or delete user pools themselves.

3. Final Answer:

   Creates a new user pool client for an existing user pool -> Option D

4. Quick Check:

   create-user-pool-client = new client for user pool [OK]

Hint: Look for 'create-user-pool-client' to identify client creation [OK]

Common Mistakes:

• Confusing client creation with user pool creation
• Assuming deletion instead of creation
• Misreading the command as a list operation

4. You wrote this code snippet to authenticate a user with Cognito but get an error:

client = boto3.client('cognito-idp')
response = client.initiate_auth(
    ClientId='abc123',
    AuthFlow='USER_PASSWORD_AUTH',
    AuthParameters={'USERNAME': 'user1'}
)

What is missing to fix the error?

medium

A. Add 'PASSWORD' in AuthParameters

B. Change AuthFlow to 'ADMIN_NO_SRP_AUTH'

C. Remove ClientId parameter

D. Add 'SECRET_HASH' in AuthParameters

Solution

1. Step 1: Check required AuthParameters for USER_PASSWORD_AUTH

   This flow requires both 'USERNAME' and 'PASSWORD' parameters to authenticate.

2. Step 2: Identify missing parameter

   The code only provides 'USERNAME' but misses 'PASSWORD', causing the error.

3. Final Answer:

   Add 'PASSWORD' in AuthParameters -> Option A

4. Quick Check:

   USER_PASSWORD_AUTH needs USERNAME and PASSWORD [OK]

Hint: USER_PASSWORD_AUTH needs both username and password [OK]

Common Mistakes:

• Forgetting to include password in parameters
• Changing AuthFlow unnecessarily
• Removing ClientId which is required

5. You want to allow users to sign in with social providers like Google using AWS Cognito. Which setup is required?

hard

A. Use only an identity pool without a user pool

B. Create only a user pool client without identity providers

C. Configure a user pool with identity providers and set up an identity pool for AWS credentials

D. Set up Lambda triggers to handle social login manually

Solution

1. Step 1: Understand social login with Cognito

   Social login requires configuring user pools with external identity providers like Google.

2. Step 2: Connect user pool to identity pool for AWS credentials

   Identity pools provide AWS credentials after authentication; both are needed for full setup.

3. Final Answer:

   Configure a user pool with identity providers and set up an identity pool for AWS credentials -> Option C

4. Quick Check:

   Social login = user pool + identity pool setup [OK]

Hint: Social login needs user pool + identity pool configured [OK]

Common Mistakes:

• Skipping identity providers in user pool
• Using only identity pool without user pool
• Trying to handle social login only with Lambda