Add support for AWS_LAMBDA_MAX_CONCURRENCY #600
Merged
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.
Description of changes:
This change adds support for the
AWS_LAMBDA_MAX_CONCURRENCYenvironment variable. When present, Lambda will handle up toAWS_LAMBDA_MAX_CONCURRENCYevents concurrently using a single instance of an execution environment. This environment variable is set by Lambda when a function is configured to use Managed InstancesNotes
lambdacontext.MaxConcurrency()returnsAWS_LAMBDA_MAX_CONCURRENCY, or1if not present.go version >= v1.22.0./nextwill be canceled, and inflight requests will be allowed to run to completion.sync.Pool.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.