HTTP API (v2) has no JWT authorizer configured

Severity: High
Service: API Gateway
Check ID: APIGW_HTTP_API_NO_JWT

What this check finds

This API Gateway HTTP API has no JWT authorizer. Without JWT validation, any caller can invoke the API without presenting a valid token.

Passing looks like: HTTP API has a JWT authorizer.

How to fix it

Create a JWT authorizer for the HTTP API and attach it to routes.

AWS CLI

aws apigatewayv2 create-authorizer --api-id API_ID --name AUTHORIZER_NAME --authorizer-type JWT --identity-source "$request.header.Authorization" --jwt-configuration Issuer=ISSUER_URL,Audience=AUDIENCE

Names in capitals are placeholders for your own resource. Review a command before you run it.

AWS console

API Gateway → HTTP API → Authorization.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to HTTP API (v2) has no JWT authorizer configured
Framework	Controls
NIST SP 800-53 Rev5 (Moderate)	AC-3 Access Enforcement IA-2 Identification and Authentication (Organizational Users)
NIST Cybersecurity Framework 2.0	PR.AA-03 Users, services, and hardware are authenticated PR.AA-05 Access permissions and authorizations are enforced with least privilege
ISO/IEC 27001:2022 Annex A	A.5.15 Access control A.8.5 Secure authentication

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More API Gateway checks

All API Gateway checks