docs(lambda): correct ESM behaviour coverage (ScalingConfig, ProvisionedPollerConfig, FunctionResponseTypes)#750
Open
joe4dev wants to merge 1 commit into
Open
Conversation
Deploying localstack-docs with
|
| Latest commit: |
202d5fd
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://66cca2d9.localstack-docs.pages.dev |
| Branch Preview URL: | https://docs-lambda-esm-scaling-cove.localstack-docs.pages.dev |
joe4dev
requested review from
HarshCasper,
dfangl,
quetzalliwrites,
remotesynth and
viren-nadkarni
as code owners
joe4dev
force-pushed
the
docs/lambda-esm-scaling-coverage
branch
from
838a8be to
0472b83
Compare
…sionedPollerConfig, FunctionResponseTypes - ScalingConfig: SQS Standard/FIFO 🟠 → 🟡 (config accepted but poller count hard-coded / single-poller FIFO, not auto-scaled) - ProvisionedPollerConfig: SQS Standard/FIFO ➖ → 🟡 (MinimumPollers honored; MaximumPollers / FIFO ignored) - FunctionResponseTypes: MSK & Self-Managed ➖ → 🟠 (AWS supports ReportBatchItemFailures for Kafka; not implemented in LocalStack) - Add footnotes [^3]/[^4] explaining the partial SQS behaviour Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
joe4dev
force-pushed
the
docs/lambda-esm-scaling-coverage
branch
from
0472b83 to
202d5fd
Compare
nik-localstack
approved these changes
Jul 3, 2026
nik-localstack
left a comment
nik-localstack
left a comment
Contributor
There was a problem hiding this comment.
Thanks for updating this 🚀
Contributor
|
btw, shouldn't go in the main branch since the feature is already released in the june release ? |
Member
Author
|
most yes with a nit no:
Given that merging to main is blocked; I don't think that's urgent enough to opt for an exception here. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
The Lambda ESM behavior coverage docs became outdated after AWS released new features (e.g., FunctionResponseTypes support for MSK/Kafka), and @nik-localstack shipped provisioned poller support for SQS
Summary
Corrects the Lambda Event Source Mapping Behaviour Coverage table (
aws/services/lambda→ Behaviour Coverage) based on a review of LocalStack's actual ESM implementation.MaximumConcurrencyMinimumPollershonored;MaximumPollershas no effectReportBatchItemFailuresfor Kafka; not yet implemented in LocalStackAdds footnotes
[^3]/[^4]explaining the partial SQS behaviour.Notes / open questions
➖ → 🟡): framed as LocalStack behavioural coverage (the code partially honorsMinimumPollers). If reviewers prefer strict AWS-parity framing (ProvisionedPollerConfig as Kafka-only, hence➖for SQS), this can be reverted.🟠(not➖): AWS supports it there, LocalStack doesn't implement it.Batch ≥ 6 MB(mini-batching isn't a true by-size implementation) andMaximumRecordAgeInSeconds(fix landing soon).Preview
https://d13ec91a.localstack-docs.pages.dev/aws/services/lambda/#behaviour-coverage
🤖 Generated with Claude Code