Hi, for websocket api authorizers there is wrong documentation I guess. I may did something wrong aswell. Can u please check I'm getting error AuthorizerResultTtlInSeconds cannot be set for WEBSOCKET protocol Apis. Documentation : https://docs.serverless-stack.com/constructs/WebSocketApi#adding-lambda-authorization

this.wsAuthorizerFn = new sst.Function(this, "ws-authorizer", {
  handler: "src/services/messenger.wsAuthorizer",
})


this.messengerApi = new sst.WebSocketApi(this, "messenger-service", {
  accessLog: false,
  authorizationType: sst.WebSocketApiAuthorizationType.CUSTOM,
  authorizer: new HttpLambdaAuthorizer({
    authorizerName: `LambdaAuthorizer`,
    handler: this.wsAuthorizerFn
  }),
  routes: {
    $connect: {
      handler: "src/services/messenger.onWebsocketConnected",
      environment: {
        WEBSOCKET_CONNECTION_TABLE: this.connectionTable.tableName
      }
    },
    $disconnect: {
      handler: "src/services/messenger.onWebsocketDisconnected",
      environment: {
        WEBSOCKET_CONNECTION_TABLE: this.connectionTable.tableName
      }
    },
  }
})
failed: AuthorizerResultTtlInSeconds cannot be set for WEBSOCKET protocol Apis. (Service: AmazonApiGatewayV2; Status Code: 400; Error Code: BadRequestException; Request ID: d46f8a9a-e138-4a00-8b9e-fc60c36e9da9; Proxy: null)

Hey @Mehmet Ali SARAÇ, you are right, the doc is wrong. Both IAM and Custom Lambda authorizers are supported.

I coulnt find any solution. I created authorizer from console 🙂

I can confirm same issue here.

AuthorizerResultTtlInSeconds cannot be set for WEBSOCKET protocol Apis. (Service: AmazonApiGatewayV2; Status Code: 400; Error Code: BadRequestException; Request ID: 5a7ab438-c502-4494-a779-1e798b178382; Proxy: null)

With the same custom authorizer, I've been deploying it through SLS for the time being.

Any updates on this topic ? @Frank

Hey @Mehmet Ali SARAÇ, yeah I put a fix in last night https://github.com/serverless-stack/serverless-stack/issues/905