Repository navigation
Description
Expected Behaviour
When a REST API uses a Lambda authorizer, API Gateway puts the authorizer's principalId, the integrationLatency and every key from the authorizer's context map into requestContext.authorizer. APIGatewayProxyEventModel should keep them, so a handler can read something like a tenant ID the authorizer set. The Lambda authorizer output docs cover the context map.
Current Behaviour
APIGatewayEventAuthorizer only declares claims and scopes, so everything else in requestContext.authorizer is dropped. The repo's tests/events/apiGatewayProxyEventPrincipalId.json has this shape (principalId, integrationLatency and a custom user_id).
The APIGatewayProxyEvent data class already exposes these through principal_id, integration_latency and get_context(), and the TypeScript schema keeps them since aws-powertools/powertools-lambda-typescript#5749.
Code snippet
import json
from aws_lambda_powertools.utilities.parser import parse
from aws_lambda_powertools.utilities.parser.models import APIGatewayProxyEventModel
with open("tests/events/apiGatewayProxyEvent.json") as f:
event = json.load(f)
# What API Gateway sends when a Lambda authorizer returns principalId "user-123"
# and context {"tenantId": "t-9"}
event["requestContext"]["authorizer"] = {
"principalId": "user-123",
"integrationLatency": 42,
"tenantId": "t-9",
}
parsed = parse(event=event, model=APIGatewayProxyEventModel)
print(parsed.requestContext.authorizer)claims=None scopes=None
Possible Solution
Declare the two fields API Gateway always sends and allow extra keys for the custom context:
class APIGatewayEventAuthorizer(BaseModel):
model_config = ConfigDict(extra="allow")
claims: dict[str, Any] | None = None
scopes: list[str] | None = None
principalId: str | None = None
integrationLatency: int | None = NoneWith that, the snippet prints principalId='user-123' integrationLatency=42 tenantId='t-9' and the custom keys are in model_extra. It only adds fields, so Cognito authorizer events parse the same as before.
I'm happy to send a PR with tests if that sounds good.
Steps to Reproduce
Run the snippet above from the repo root.
Powertools for AWS Lambda (Python) version
3.40.0
AWS Lambda function runtime
3.13
Packaging format used
PyPi
Metadata
Metadata
Assignees
Labels
Type
Projects
- StatusShow more project fieldsComing soon
Activity
dropps07 commentedon Nov 14, 2026
hii @leandrodamascena pls assign me on this issue. i can work on it. I have looked at the parser model and the missing authorizer fields are clear. Thanks!
Manishram-ai commentedon Nov 15, 2026
Thanks for offering, @dropps07! I'd said in the issue I'd send a PR for this, so I opened #8813 with a test. If @leandrodamascena would rather you take it, that's fine with me too.
powertools-for-aws-oss-automation commentedon Nov 15, 2026
Warning
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
github-actions commentedon Nov 18, 2026
This is now released under 3.41.0 version!