Create Cognito User Pool and Use Cognito Access Token for JWT Authorizer in HTTP API Gateway

🌟 *Master AWS Fundamentals!* 🌟
Ready to dive into the world of cloud computing? Check out this comprehensive course on Coursera: AWS Fundamentals Specialization
imp.i384100.net/WqnRe3
This course covers everything you need to know about Amazon Web Services, from the basics to advanced concepts, making it perfect for both beginners and those looking to enhance their cloud skills. Enroll now and elevate your career with in-demand AWS expertise! 📚🚀
In this video we will take a look at how to create Cognito user pool. We will get access token and use it JWT authorizer for HTTP API Gateway.

[@CeliaLevelab]

Thank you so much! this is the only resource I've found with the updated console. Very well explained

[@alexrusin]

You're welcome!

[@watchparty1]

Loved that video intro. Was that you with your co-workers? Good video. Lot of great help.

[@alexrusin]

No, that's not me 😀

[@mercadoalex]

Hey Alex, what would be your advice if we need to change the JWT issuer dynamically ? I mean if I have different environments (dev, test, staging, prod) how can I change and validate the JWT issuer according to the env, (I'm trying using AWS CDK). ....a custom claim perhaps?

[@alexrusin]

Hey. I usually use different Cognito pools for local dev, stage and prod. All you have to do is to put different env variables.

[@mercadoalex]

​@@alexrusin Thanks for your response, so there is no need to customize the JWT, correct? I see there is a “iss” (issuer) claim that identifies the principal that issued the JWT, correct me if I'm wrong, if the user pool lets say in PRO issues a jwt, it can't be used /read in other envs. This is the expected behavior by default.