Skip to content

docs(lambda): correct ESM behaviour coverage (ScalingConfig, ProvisionedPollerConfig, FunctionResponseTypes) - #750

Merged
quetzalliwrites merged 1 commit into
aws-docs-release-julyfrom
docs/lambda-esm-scaling-coverage
Jul 7, 2026
Merged

docs(lambda): correct ESM behaviour coverage (ScalingConfig, ProvisionedPollerConfig, FunctionResponseTypes)#750
quetzalliwrites merged 1 commit into
aws-docs-release-julyfrom
docs/lambda-esm-scaling-coverage

Conversation

@joe4dev

@joe4dev joe4dev commented Jul 2, 2026

Copy link
Copy Markdown
Member

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.

Parameter Source Was Now Reason
ScalingConfig SQS Standard 🟠 🟡 Config accepted, but poller count is hard-coded — not auto-scaled from MaximumConcurrency
ScalingConfig SQS FIFO 🟠 🟡 Single poller always used to preserve message-group ordering; config accepted but ignored
ProvisionedPollerConfig SQS Standard 🟡 MinimumPollers honored; MaximumPollers has no effect
ProvisionedPollerConfig SQS FIFO 🟡 Single-poller model ignores the config
FunctionResponseTypes Amazon MSK 🟠 AWS supports ReportBatchItemFailures for Kafka; not yet implemented in LocalStack
FunctionResponseTypes Self-Managed 🟠 Same as above

Adds footnotes [^3]/[^4] explaining the partial SQS behaviour.

Notes / open questions

  • ProvisionedPollerConfig for SQS (➖ → 🟡): framed as LocalStack behavioural coverage (the code partially honors MinimumPollers). If reviewers prefer strict AWS-parity framing (ProvisionedPollerConfig as Kafka-only, hence for SQS), this can be reverted.
  • ProvisionedPollerConfig for Kafka intentionally left 🟠 (not ): AWS supports it there, LocalStack doesn't implement it.
  • Deliberately not touched: Batch ≥ 6 MB (mini-batching isn't a true by-size implementation) and MaximumRecordAgeInSeconds (fix landing soon).

Preview

https://d13ec91a.localstack-docs.pages.dev/aws/services/lambda/#behaviour-coverage
Screenshot 2026-07-02 at 15 04 38

🤖 Generated with Claude Code

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 2, 2026

Copy link
Copy Markdown

Deploying localstack-docs with  Cloudflare Pages  Cloudflare Pages

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

View logs

@joe4dev
joe4dev changed the base branch from main to aws-docs-release-july July 2, 2026 13:08
@joe4dev
joe4dev requested a review from nik-localstack July 2, 2026 13:09
@joe4dev
joe4dev marked this pull request as ready for review July 2, 2026 13:09
@joe4dev
joe4dev force-pushed the docs/lambda-esm-scaling-coverage branch from 838a8be to 0472b83 Compare July 2, 2026 13:10
@joe4dev
joe4dev marked this pull request as draft July 2, 2026 13:10
…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
joe4dev force-pushed the docs/lambda-esm-scaling-coverage branch from 0472b83 to 202d5fd Compare July 2, 2026 13:12
@joe4dev
joe4dev marked this pull request as ready for review July 2, 2026 13:13

@nik-localstack nik-localstack left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updating this 🚀

@nik-localstack

Copy link
Copy Markdown
Contributor

btw, shouldn't go in the main branch since the feature is already released in the june release ?

joe4dev commented Jul 3, 2026

Copy link
Copy Markdown
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.

@quetzalliwrites
quetzalliwrites merged commit 7d4487d into aws-docs-release-july Jul 7, 2026
1 check passed
@quetzalliwrites

Copy link
Copy Markdown
Collaborator

tyvm @joe4dev, awesome contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants