Skip to content
Nubent

/AWS · Nov 17, 2026

API Gateway REST validates JWTs without Lambda

Amazon API Gateway REST APIs now have a native JWT authorizer: they validate tokens from any OpenID Connect or OAuth 2.0 provider without writing a Lambda authorizer.

What changes

Before, validating tokens from a provider other than Amazon Cognito in a REST API required your own Lambda authorizer. Now you configure issuers, audiences, signing algorithms and required claims, and API Gateway verifies the signature, issuer, audience, expiration and claims on every request. A single authorizer can be attached to many methods with different scopes, and it works on regional, edge and private APIs.

How to implement it

  1. Inventory the Lambda authorizers that only check signature, issuer and audience.

  2. Configure the JWT authorizer with the same issuers and audiences, starting on a test stage.

  3. Define scopes per method and test expired tokens, tokens for another audience and tokens with missing claims.

  4. Once traffic passes cleanly, retire the Lambda authorizer and its code.

Nubent's take

Less custom code in the critical authentication path means less surface for errors and lower latency. If your authorizer also applies business logic, that part still needs Lambda.

Next step

Should we implement it in your account?

We check whether it fits, how much work it takes and what risks it carries. 30 minutes with an engineer.