Is it possible to update the user-defined authorizer context (i.e., event.requestContext.authorizer.context) after the initial authorizer lambda has already run?

0

I have a NodeJS/Websocket/API Gateway/Lambda application that is making use of the authorizer lambda's context capability (i.e., event.requestContext.authorizer.context) to store certain session data. This context data is conveniently available for every subsequent lambda invocation after (and including) the websocket's $connect event.

The problem is that some of the session data we have stored in the context will eventually become stale. Is there a way to update this authorizer context data after the authorizer has already run? I am honestly just trying to avoid unnecessary calls to DynamoDB.

답변 없음

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠