From 22dc276cb232dfc81ba23305f3798b9d1a2ea248 Mon Sep 17 00:00:00 2001 From: Alex McLean Date: Sat, 11 Feb 2023 18:15:01 -0800 Subject: [PATCH] Adding link to using different authorizers in example Adding a reference to the fact that you can use different authorizers for folks who stumble across this example and don't know (like myself :)). --- .../how-to-add-cognito-authentication-to-a-serverless-api.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/_examples/how-to-add-cognito-authentication-to-a-serverless-api.md b/_examples/how-to-add-cognito-authentication-to-a-serverless-api.md index d99c5fc4e..7a54645ea 100644 --- a/_examples/how-to-add-cognito-authentication-to-a-serverless-api.md +++ b/_examples/how-to-add-cognito-authentication-to-a-serverless-api.md @@ -97,7 +97,9 @@ GET /private GET /public ``` -By default, all routes have the authorization type `AWS_IAM`. This means the caller of the API needs to have the required IAM permissions. The first is a private endpoint. The second is a public endpoint and its authorization type is overriden to `NONE`. +By default, all routes have the authorization type `AWS_IAM`. This means the caller of the API needs to have the required IAM permissions. If you want to use JWT access tokens (seperate from this example doc), see the examples in the Constructs docs [here](https://docs.sst.dev/constructs/Api#adding-jwt-authorization). + +The first `route` is a private endpoint. The second is a public endpoint and its authorization type is overriden to `NONE`. ## Setting up authentication