Other question/concern… Is anybody using “Simple” Lambda Authorizer? It works fine for the most part, but this is strange… On my lambda integration, this is what I receive on the `event`:

...
requestContext: {
    accountId: 'xxx',
    apiId: 'xxx',
    authorizer: { lambda: [Object] },
    domainName: 'xxx',
...

As you can see, there is an object

authorizer

which has a child `lambda`… the object inside

lambda

it’s totally fine, it’s exactly what I expect to receive. The problem is, apparently this

lambda

object doesn’t exists on TS interface

APIGatewayProxyEventV2

. As you can see here, this is the interface definition:

...
    requestContext: {
        accountId: string;
        apiId: string;
        authorizer?: {
            jwt: {
                claims: { [name: string]: string | number | boolean | string[] };
                scopes: string[];
            };
        } | undefined;
        domainName: string;
        domainPrefix: string;
...

Apparently the interface

APIGatewayProxyEventV2

only supports

jwt

, but not

lambda

? anybody else had this issue?

Hm that's annnoying. I think AWS says this is the official format as you can see here: https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html

Well, the JWT authorizer doesn’t work for me.

ah got it

@thdxr I been checking this again, apparently the type is missing on

@types

.

Yeah I did check the underlying library

Mmm.

Yeah it's just a type issue. I'd suggest making your own type

Ok cool.