Debug Your Infrastructure

Get Instant Solutions for Kubernetes, Databases, Docker and more

AWS CloudWatch
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Pod Stuck in CrashLoopBackOff
Database connection timeout
Docker Container won't Start
Kubernetes ingress not working
Redis connection refused
CI/CD pipeline failing

Amazon Cognito ResourceNotFoundException

The specified resource (e.g., user pool or client) does not exist.

Understanding Amazon Cognito

Amazon Cognito is a powerful authentication provider offered by AWS, designed to manage user sign-up, sign-in, and access control. It allows developers to add user authentication to their applications quickly and securely. Cognito supports various authentication methods, including social identity providers and enterprise identity providers via SAML 2.0.

Identifying the Symptom: ResourceNotFoundException

When working with Amazon Cognito, you might encounter the ResourceNotFoundException error. This error typically manifests when attempting to access a resource that Cognito cannot find, such as a user pool or a client application.

Common Scenarios

  • Attempting to access a user pool that has been deleted or never existed.
  • Using an incorrect client ID when trying to authenticate users.

Exploring the Issue: What is ResourceNotFoundException?

The ResourceNotFoundException is an error code returned by AWS services when a specified resource cannot be located. In the context of Amazon Cognito, this often means that the identifiers provided for a user pool or client are incorrect or the resources have been removed.

Root Causes

  • Incorrect user pool ID or client ID in your application configuration.
  • Resources have been deleted or not yet created.

Steps to Resolve ResourceNotFoundException

To resolve the ResourceNotFoundException, follow these steps:

Step 1: Verify Resource Identifiers

Ensure that the user pool ID and client ID used in your application match those in the AWS Cognito console:

  1. Log in to the AWS Management Console.
  2. Navigate to Cognito under the Services menu.
  3. Check the User Pools section for the correct user pool ID.
  4. In the App clients section, verify the client ID.

Step 2: Check Resource Existence

Ensure that the resources you are trying to access exist:

  1. Confirm that the user pool has not been deleted.
  2. Ensure that the client application is correctly configured and active.

Step 3: Update Application Configuration

If identifiers are incorrect, update your application configuration files or environment variables with the correct values:

USER_POOL_ID=us-east-1_example
CLIENT_ID=exampleclientid123

Additional Resources

For further assistance, consider the following resources:

Master 

Amazon Cognito ResourceNotFoundException

 debugging in Minutes

— Grab the Ultimate Cheatsheet

(Perfect for DevOps & SREs)

Most-used commands
Real-world configs/examples
Handy troubleshooting shortcuts
Your email is safe with us. No spam, ever.

Thankyou for your submission

We have sent the cheatsheet on your email!
Oops! Something went wrong while submitting the form.

🚀 Tired of Noisy Alerts?

Try Doctor Droid — your AI SRE that auto-triages alerts, debugs issues, and finds the root cause for you.

Heading

Your email is safe thing.

Thank you for your Signing Up

Oops! Something went wrong while submitting the form.

MORE ISSUES

Deep Sea Tech Inc. — Made with ❤️ in Bangalore & San Francisco 🏢

Doctor Droid