Prompt
How do I troubleshoot password reset emails not arriving from Cognito?
Latest observation
Here’s a practical troubleshooting checklist for Cognito password reset emails not arriving.
1) Confirm Cognito is actually sending the reset
For a password reset, the usual flow is:
ForgotPasswordis called- Cognito attempts to send a verification code/email
ConfirmForgotPasswordis called with the code
Make sure your app is successfully calling ForgotPassword and not swallowing an error.
Check for errors like:
CodeDeliveryFailureExceptionInvalidParameterExceptionUserNotFoundException- Note: depending on your app/client settings, Cognito may not reveal whether the user exists.
2) Verify the user pool email configuration
In the Cognito User Pool, check Message delivery / Email settings:
A. If using the default Cognito email configuration
- Cognito sends from an AWS-managed email source.
- This is easiest to set up, but delivery can be less reliable for some domains.
B. If using SES
If you configured Amazon SES:
- Confirm the SES identity/domain is verified
- If SES is in sandbox mode, you can only send to verified recipients
- Check the SES region matches your Cognito user pool region or the configured sending setup
- Review SES sending limits, bounces, and complaints
3) Check the email address on the user
Make sure:
- The user’s email attribute is correct
- It is marked as verified if your flow requires it
- The account is using email as a sign-in attribute or alias as expected
If the user record has a typo or old email, Cognito will send to the wrong address.
4) Look at the user pool “Message delivery” and template settings
In the Cognito console:
- Check the email configuration
- Check any custom email message templates
- Make sure there are no placeholder/template errors
- Verify the subject/body are valid and not empty
If you use a custom message Lambda trigger, inspect it for failures.
5) Review Lambda triggers, if enabled
If you have triggers such as:
- Custom Message
- Custom Email Sender
- Pre Sign-up
- Post Confirmation
Then a problem in one of these can prevent or alter delivery.
Check:
- CloudWatch logs for trigger errors
- That the trigger returns the expected response format
- That it doesn’t suppress or replace the reset code incorrectly
6) Check CloudWatch / CloudTrail for failures
Useful places to inspect:
- CloudWatch logs for Lambda triggers
- CloudTrail for Cognito API calls
- SES sending metrics if using SES
Look for:
- rejected messages
- throttling
- configuration errors
- authorization failures
7) Check spam/junk and mail filtering
Sometimes the email is sent but filtered out:
- Spam/Junk folder
- Quarantine
- Enterprise mail gateway
- DMARC/SPF/DKIM issues
If using SES, make sure SPF/DKIM are configured for your domain and aligned properly.
8) Validate the sender identity and domain reputation
If using a custom domain or SES:
- Confirm SPF, DKIM, and DMARC records are set correctly
- Check whether your domain has a poor reputation
- Review SES bounce/complaint rates
9) Confirm the region and app client settings
Ensure:
- The app is calling the correct Cognito User Pool region
- The client ID matches the user pool app client
- The app client is allowed to use the auth flows you expect
A mismatch can lead to requests hitting the wrong pool.
10) Reproduce with AWS CLI
Try the API directly to isolate your app from Cognito:
aws cognito-idp forgot-password \
--client-id YOUR_APP_CLIENT_ID \
--username user@example.com
If this returns an error, that error is usually the key clue.
11) If using SES, check these common issues
- SES sandbox not exited
- Identity not verified
- Sending quota exceeded
- Suppression list has the recipient
- Bounce/complaint causing future suppression
12) Ask: is the issue delivery, or generation?
Separate the problem into:
- Cognito didn’t generate/send the email
- Email was sent but not received
That determines where to debug:
- API / user pool / Lambda / SES for #1
- mailbox, spam, DNS, reputation, suppression for #2
Quick triage path
If you want the fastest path:
- Call
ForgotPasswordmanually with AWS CLI - Check the response/error
- Verify the user email in Cognito
- Check whether you use default email or SES
- Inspect CloudWatch logs for any Lambda triggers
- Check SES bounce/suppression if applicable
- Check spam/junk
If you want, I can also give you a step-by-step debugging flowchart or help you debug a specific Cognito error message.