Skip to main content

If you are using our backend SDK that is lesser than the following versions, please visit the older documentation link here.

Set up Lambda

1) Create a new lambda#

2) Link lambda layer with the lambda function#

  • Scroll to the bottom and look for the Layers tab. Click on Add a layer

    Link Lambda function with the Lambda layer

  • Select Custom Layer and then select the layer we created in the first step:

Link custome layer with Lambda function Node

3) Create a backend config file#

Using the editor provided by AWS, create a new config file and write the following code:

How do you want to identify your users?
Only phone numberOnly emailEmail or phone number
Which authentication type will you use?
OTPMagic linksOTP and Magic link
config.mjs
import ThirdParty from "supertokens-node/recipe/thirdparty"
import Passwordless from "supertokens-node/recipe/passwordless"
import Session from 'supertokens-node/recipe/session'

export function getBackendConfig() {
  return {
    framework: "awsLambda",
    supertokens: {
      connectionURI: "",
      apiKey: "",
    },
    appInfo: {
      // learn more about this on https://supertokens.com/docs/thirdpartypasswordless/appinfo
      appName: "<YOUR_APP_NAME>",
      apiDomain: "<YOUR_API_DOMAIN>",
      websiteDomain: "<YOUR_WEBSITE_DOMAIN>",
      apiBasePath: "/auth",
      websiteBasePath: "/auth",
      apiGatewayPath: "/dev"
    },
    recipeList: [
      Passwordless.init({
        flowType: "USER_INPUT_CODE",
        contactMethod: "PHONE",
      }),
      ThirdParty.init({
        // We have provided you with development keys which you can use for testing.
        // IMPORTANT: Please replace them with your own OAuth keys for production use.
        signInAndUpFeature: {
          providers: [{
              config: {
                  thirdPartyId: "google",
                  clients: [{
                      clientId: "1060725074195-kmeum4crr01uirfl2op9kd5acmi9jutn.apps.googleusercontent.com",
                      clientSecret: "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"
                  }]
              }
          }, {
              config: {
                  thirdPartyId: "github",
                  clients: [{
                      clientId: "467101b197249757c71f",
                      clientSecret: "e97051221f4b6426e8fe8d51486396703012f5bd"
                  }]
              }
          }, {
              config: {
                  thirdPartyId: "apple",
                  clients: [{
                      clientId: "4398792-io.supertokens.example.service",
                      additionalConfig: {
                          keyId: "7M48Y4RYDL",
                          privateKey:
                              "-----BEGIN PRIVATE KEY-----\nMIGTAgEAMBMGByqGSM49AgEGCCqGSM49AwEHBHkwdwIBAQQgu8gXs+XYkqXD6Ala9Sf/iJXzhbwcoG5dMh1OonpdJUmgCgYIKoZIzj0DAQehRANCAASfrvlFbFCYqn3I2zeknYXLwtH30JuOKestDbSfZYxZNMqhF/OzdZFTV0zc5u5s3eN+oCWbnvl0hM+9IW0UlkdA\n-----END PRIVATE KEY-----",
                          teamId: "YWQCXGJRJL",
                      }
                  }]
              }
          }],
        }
      }),
      Session.init(),
    ],
    isInServerlessEnv: true,
  }
}
important

In the above code, notice the extra config of apiGatewayPath that was added to the appInfo object. The value of this should be whatever you have set as the value of your AWS stage which scopes your API endpoints. For example, you may have a stage name per dev environment:

  • One for development (/dev).
  • One for testing (/test).
  • One for prod (/prod).

So the value of apiGatewayPath should be set according to the above based on the env it's running under.

You also need to change the apiBasePath on the frontend config to append the stage to the path. For example, if the frontend is query the development stage and the value of apiBasePath is /auth, you should change it to /dev/auth.

note

You may edit the apiBasePath and apiGatewayPath value later if you haven't setup the API Gateway yet.

4) Add the SuperTokens auth middleware#

Using the editor provided by AWS, create/replace the handler file contents with the following code:

index.mjs
import supertokens from "supertokens-node";
import { middleware } from "supertokens-node/framework/awsLambda";
import { getBackendConfig } from "./config.mjs";
import middy from "@middy/core";
import cors from "@middy/http-cors";

supertokens.init(getBackendConfig());

export const handler = middy(
    middleware((event) => {
      // SuperTokens middleware didn't handle the route, return your custom response
      return {
        body: JSON.stringify({
            msg: "Hello!",
        }),
        statusCode: 200,
      };
    })
)
    .use(
        cors({
            origin: getBackendConfig().appInfo.websiteDomain,
            credentials: true,
            headers: ["Content-Type", ...supertokens.getAllCORSHeaders()].join(", "),
            methods: "OPTIONS,POST,GET,PUT,DELETE",
        })
    )
    .onError((request) => {
        throw request.error;
    });
Add Supertokens auth middleware UI
important

Since, we are using esm imports, we will need to set NODE_OPTIONS="--experimental-specifier-resolution=node" flag in the lambda environment variables. See the Node.js documentation for more information.

Configuring env variables UI
Looking for older versions of the documentation?
Which UI do you use?
Custom UI
Pre built UI