Removing DLQ check rule #394
Open
Conversation
This file contains 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
Hello, currently the recommended way for handling failures of Lambda functions is to use Lambda Destinations, not DLQs. I couldn't find an AWS managed rule for Lambda Destinations, so currently the replacement would be to create a custom rule that checks if you are using Destinations for your Lambdas. https://aws.amazon.com/blogs/compute/introducing-aws-lambda-destinations/ "...Dead Letter Queues (DLQ) have been available since 2016 and are a great way to handle asynchronous failure situations. Destinations provide more useful capabilities by passing additional function execution information, including code exception stack traces, to more destination services. Destinations and DLQs can be used together and at the same time although Destinations should be considered a more preferred solution..."
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.
Hello, currently the recommended way for handling failures of Lambda functions is to use Lambda Destinations, not DLQs. I couldn't find an AWS managed rule for Lambda Destinations, so currently the replacement would be to create a custom rule that checks if you are using Destinations for your Lambdas.
https://aws.amazon.com/blogs/compute/introducing-aws-lambda-destinations/
I confirm these files are made available under CC0 1.0 Universal (https://creativecommons.org/publicdomain/zero/1.0/legalcode)