Make Lambda reusable for CloudFront Lambda@Edge #12409
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
c484845 to
d40be45
Compare
d40be45 to
39a6cf9
Compare
180f008 to
40b0040
Compare
dfangl
approved these changes
Mar 24, 2025
40b0040 to
e1bae6d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
CloudFront Lambda@Edge requires some changes in Lambda to be able to re-use the existing Lambda infrastructure.
Changes
Functionobject optional incounting_service::get_invocation_leasesuch that we can re-use the counting service for Lambda@Edge, and skip reserved and provisioned concurrencyfunctionis only used for the counting service