Design a sign-in door — Cognito

Your goal

Create a user-pool configuration and set its minimum password length.

Why this matters

An application user directory has its own sign-in policies. You will configure an empty pool’s password length and read the saved value. This is separate from CloudArcade’s own account system.

Words you will use

A user pool holds app users and supports sign-in. Authentication asks who you are. Authorization asks what you may access.

How to proceed

Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.

1. Create a practice user pool

Create a Cognito user pool. A pool stores application user identities and sign-in settings. This lab configures an empty pool and does not store real visitor passwords.

2. Set the password length

Choose a minimum length for this practice pool and save its password policy. Length is one part of sign-in security; recovery, MFA, abuse controls, and session handling also matter.

Minimum password length: Choose 12–30 characters. You are setting a policy, not entering a password. Suggested practice value: 15.

3. Read the pool policy

Describe the pool and compare MinimumLength with your choice. This lab verifies the stored policy, not a complete sign-in flow.

Practice, then check your understanding

Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.

Read the official AWS documentation for service behavior and production details.