Repository navigation
fix(npmjs): packument processor cannot be deployed - #1946
Merged
cdklabs-automation merged 1 commit intoOct 14, 2026
Merged
Conversation
The packument processor reads its dead-letter queue, but that queue had the default visibility timeout of 30 seconds. Lambda rejects an event source whose queue hides messages for less time than the function runs (5 minutes), so the deployment failed. Both queues the processor reads now use a visibility timeout of 6 times the function timeout.
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
cdklabs-automation
enabled auto-merge
October 14, 2026 09:02
rix0rrr
approved these changes
Oct 14, 2026
cdklabs-automation
deleted the
mrgrain/fix/npmjs/packument-dlq-visibility-timeout
branch
October 14, 2026 09:09
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
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.
Deploying #1942 fails on the event source that connects the packument processor to its dead-letter queue:
The processor reads the dead-letter queue to log and count the requests that were given up on. That queue never set a visibility timeout, so it had the SQS default of 30 seconds, and Lambda requires at least the function timeout. The main queue was fine, because it already used 30 minutes.
Both queues now take their visibility timeout from the function timeout (6 times, as AWS recommends), so they can't drift apart again. A new construct test checks every queue the processor reads; it fails on main with the same 30 seconds against 300.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license