Which UI do you use?

Custom UI

Pre built UI

Using JWT Authorizers

caution

AWS supports JWT authorizers for HTTP APIs and not REST APIs on the API Gateway service. For REST APIs follow the Lambda authorizer guide

1) Update the backend config

Update the backend config, created here, to enable the JWT feature.

NodeJS

config.ts

import Session from 'supertokens-node/recipe/session'
import SuperTokensTypes from 'supertokens-node/types';

function getBackendConfig(): SuperTokensTypes.TypeInput {
  return {
    framework: "awsLambda",
    supertokens: {
        connectionURI: "",
        apiKey: "",
    },
    appInfo: {
        // learn more about this on https://supertokens.com/docs/session/appinfo
        appName: "<YOUR_APP_NAME>",
        apiDomain: "<YOUR_API_DOMAIN>",
        websiteDomain: "<YOUR_WEBSITE_DOMAIN>",
        apiBasePath: "/auth",
        websiteBasePath: "/auth",
    },
    recipeList: [
      Session.init({
          jwt: {
              enable: true,
          },
          override: {
            functions: function (originalImplementation) {
                return {
                    ...originalImplementation,
                    createNewSession: async function (input) {
                        input.accessTokenPayload = {
                            ...input.accessTokenPayload,
                            /*
                            * AWS requires JWTs to contain an audience (aud) claim
                            * The value for this claim should be the same
                            * as the value you set when creating the
                            * authorizer
                            */
                            aud: "jwtAuthorizers",
                        };

                        return originalImplementation.createNewSession(input);
                    },
                };
            }
        },
      }),
    ],
    isInServerlessEnv: true,
  }
}

module.exports.getBackendConfig = getBackendConfig;

Python

config.py

from supertokens_python.recipe import session
from supertokens_python import (
    InputAppInfo,
    SupertokensConfig,
)

from typing import Any, Dict, Optional

supertokens_config = SupertokensConfig(
    connection_uri="",
    api_key=""
)

app_info = InputAppInfo(
    # learn more about this on https://supertokens.com/docs/session/appinfo
    app_name="<YOUR_APP_NAME>",
    api_domain="<YOUR_API_DOMAIN>",
    website_domain="<YOUR_WEBSITE_DOMAIN>",
    api_base_path="/auth",
    website_base_path="/auth",
    api_gateway_path="/dev",
)

framework = "fastapi"

from supertokens_python.recipe.session.interfaces import RecipeInterface as SessionRecipeInterface, SessionContainer

def override_session_functions(oi: SessionRecipeInterface) -> SessionRecipeInterface:
    oi_create_new_session = oi.create_new_session

    async def create_new_session(
            request: Any, user_id: str, access_token_payload: Optional[Dict[str, Any]], 
            session_data: Optional[Dict[str, Any]], user_context: Dict[str, Any]
        ) -> SessionContainer:
        # AWS requires JWTs to contain an audience (aud) claim
        # The value for this claim should be the same as the
        # value you set when creating the authorizer

        if access_token_payload is None:
            access_token_payload = {}

        access_token_payload["aud"] = "jwtAuthorizers"
        return await oi_create_new_session(request, user_id, access_token_payload, session_data, user_context)
    
    oi.create_new_session = create_new_session
    return oi

recipe_list = [
    session.init(
        jwt=session.JWTConfig(enable=True),
        override=session.InputOverrideConfig(
            functions=override_session_functions,
        )
    ),
]

2) Configure your authorizer

• Go to the "Authorizers" tab in the API Gateway configuration and select the "Manage authorizers" tab
• Click "Create", in the creation screen select "JWT" as the "Authorizer type"
• Enter a name for your authorizer (You can enter any name for this field)
• Use $request.header.Authorization for the "Identity source". This means that API requests will contain the JWT as a Bearer token under the request header "Authorization".
• Use {apiDomain}/{apiGatewayPath}/{apiBasePath} for the "Issuer URL", read here to know more
• Set a value for the "Audience" field, this will be the value you expect the JWT to have under the aud claim. In the backend config above the value is set to "jwtAuthorizers"

3) Add the authorizer to your API

• In the "Authorization" section select the "Attach authorizers to routes" tab
• Click on the route you want to add the authorizer to and select the authorizer you created from the dropdown
• Click "Attach authorizer"
• Deploy your changes and test your API