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.
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
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)