Dead letter queues for promotions-lambdas #3332
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
tomrf1
added
the
maintenance
juabara
approved these changes
Jan 9, 2026
sookburt
approved these changes
Jan 9, 2026
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.
We have 3 lambdas which process events from DynamoDb streams.
Currently each lambda will retry a failed event 3 times.
We have alarms for when the lambda fails, but not if an event cannot be processed after 3 retries.
The solution here is to add a dead letter queue for each lambda, and a cloudwatch alarm for each queue.
This will mean we receive a notification if an event ends up on the dead letter queue because it cannot be processed.
Tested in CODE by triggering an invalid event and observing the event landing in the DLQ after 3 retries.