AWS announced on November 17, 2026 that Amazon API Gateway REST APIs now include a built-in JWT authorizer. The new authorizer type checks JSON Web Tokens inside the gateway itself, so REST APIs can accept tokens from OpenID Connect and OAuth 2.0 providers through configuration alone.
Until this change, REST APIs had a native token option only for Amazon Cognito user pools. Teams that used Okta, Auth0, Microsoft Entra ID or any other identity provider had to write and run a Lambda authorizer to validate tokens. That extra function is now optional for this common case.
What Changed
The JWT authorizer joins the existing Lambda and Cognito authorizer types for REST APIs. Instead of writing code that downloads signing keys, decodes tokens and compares claims, you describe the rules and API Gateway enforces them on every call.
According to AWS, the configuration covers:
- One or more token issuers, each with its own list of accepted audiences.
- The signing algorithms you are willing to accept.
- Extra claims that a token may carry.
- Per-method scope requirements, so one authorizer can protect many methods with different scopes.
On each request the gateway verifies the token signature, the issuer, the audience, the expiry time and the configured claims. A request that fails any of those checks is rejected before it reaches your backend.
Where It Works
AWS says the feature supports all three REST API endpoint types: Regional, edge-optimized and private. It is available in every commercial AWS Region and in the AWS GovCloud (US) Regions from launch, so there is no regional rollout to wait for.
AWS lists machine-to-machine APIs, backends for mobile and web apps, and multi-tenant APIs that trust tokens from several identity providers as the main fits. The support for several issuers in one authorizer is what makes the multi-tenant case practical.
How It Compares With HTTP APIs
HTTP APIs, the lighter API Gateway product, have offered JWT authorizers for some time, and their documentation shows the general model. There, the gateway reads the token from the configured identity source, with or without a Bearer prefix, and checks the signature against a public key it downloads from the JWKS address the issuer publishes.
The HTTP API guide notes that the gateway may hold a signing key in its cache for as long as two hours, so key rotation needs an overlap period. It also warns that access tokens and OpenID Connect ID tokens look alike, and recommends requiring scopes on routes unless you really want ID tokens accepted.
AWS has not yet published a separate REST API guide that confirms the same caching and claim rules. Treat the HTTP API behavior as a likely guide, and confirm details such as supported algorithms in the REST API documentation before you depend on them.
What It Means for Developers
The clearest benefit is less code to own. A Lambda authorizer is a security-critical function that needs JWT libraries, key caching, patching and monitoring, and it adds cold-start latency and cost to protected calls. Moving that work into the gateway removes all of it for the common validation case.
You still need a Lambda authorizer when the decision depends on data outside the token, such as a database lookup of account status or custom tenant rules. A sensible pattern is to let the JWT authorizer handle signature and claim checks, and keep finer-grained permission logic in the backend.
Teams running REST APIs mainly for features HTTP APIs lack, such as usage plans, API keys or request validation, gain the most. They no longer have to pick between those features and native JWT validation. If your backend reads user data from tokens, plan to switch it to the claims the gateway passes through after validation.
How to Get Started
Start by registering your API as a client or resource with your identity provider and noting the issuer URL and audience values it uses. Then create a JWT authorizer on the REST API with those values and the allowed algorithms.
Attach the authorizer to the methods you want to protect and set the scopes each one needs. Test with valid, expired and wrong-audience tokens in a non-production stage before you remove any existing Lambda authorizer, and redeploy the stage so the change takes effect.
Conclusion
Native JWT authorizers close a long-standing gap between API Gateway REST APIs and HTTP APIs. For most teams that use a third-party identity provider, token validation becomes a setting instead of a Lambda function to maintain, which cuts code, latency and cost.
Sources
- AWS What's New: Amazon API Gateway REST APIs now support JWT authorizers
- AWS Documentation: Control access to HTTP APIs with JWT authorizers
See my articles more often when you search Google.
