A developer has an application that uses WebSocket APIs in Amazon API Gateway. The developer wants to use an API Gateway Lambda authorizer to control access to the application. The developer needs…

A token-based Lambda authorizer accepts a single token (such as a JWT or API key) and supports a configurable cache TTL, so the authorizer result is reused for subsequent requests with the same token rather than invoking the Lambda on every call.

A request parameter-based Lambda authorizer caches results based on a combination of multiple request parameters, which is more complex and less suited to simple token-based credential caching for WebSocket APIs.

Configuring an integration request mapping template to reference the context map from the Lambda authorizer allows downstream integrations to use the authorization data (such as user identity) that was already computed and cached, preventing redundant secret-key lookups.

Referencing the identity API key value from the method request in a mapping template exposes the raw API key downstream rather than the richer cached authorization context produced by the Lambda authorizer.

VPC endpoint policies control network-level access to API Gateway from within a VPC and have no effect on credential caching or token reuse at the application layer.