Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of Remove the Lambda SnapStart incompatibility notice. into release/1.13.x #19420

Merged
merged 1 commit into from
Mar 1, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions website/content/docs/platform/aws/lambda-extension.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -268,10 +268,6 @@ synchronously refresh its own token before proxying requests if the token is
expired (including a grace window), and it will attempt to renew its token if the
token is nearly expired but renewable.

~> **Note**: The Vault Lambda Extension is currently incompatible with
[AWS SnapStart](https://docs.aws.amazon.com/lambda/latest/dg/snapstart.html).
This is because AWS SnapStart does not support the Lambda Extensions API.

## Performance impact

AWS Lambda pricing is based on [number of invocations, time of execution and memory
Expand Down