01
Email-first defaults
Required and auto-verified email reduces per-application setup.
Component 03
Cognito Auth
Add email-based sign-in and configurable user authentication.
Status
Available module
Deployment scope
Regional user pool; plan user recovery separately
What it deploys
The resources this component creates, and how they connect. Drag to pan, scroll to zoom.
Usage example
Inputs in, outputs out. Illustrative wiring, not a standalone deployment.
Configure an AWS provider for the user pool region. Integrate the returned pool and client identifiers with your application auth flow. Configure provider requirements and credentials in your root module; check the documentation for all required inputs and version changes.
main.tf
module "auth" {
source = "pomo-studio/cognito-auth/aws"
version = "~> 1.0"
name = "my-app-users"
client_name = "my-app"
mfa_configuration = "OPTIONAL"
}Key inputs
- name
- client_name
- mfa_configuration
- enable_hosted_ui
- oauth_callback_urls
Useful outputs
- user_pool_id
- client_id
- lambda_env_vars
- hosted_ui_signin_url
What you get
02
Flexible security
Tune MFA, password policy, and token validity with variables.
03
Application-ready outputs
Consume pool and client details directly from your runtime.
Built with
- Amazon Cognito
- JWT
- Lambda
- Terraform