-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[aws-events] Add support for Rule Dead Letter Queue #11612
[aws-events] Add support for Rule Dead Letter Queue #11612
Comments
Added a Draft Pull Request for an idea of the implementation. It's only for the Lambda function. I guess we could move the code to the |
Add DLQ Configuration to Rule targets. Using a DLQ on a rule prevents the application to loose events after all retry attempts are exhausted. Resolves #11612 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Add DLQ Configuration to Rule targets. Using a DLQ on a rule prevents the application to loose events after all retry attempts are exhausted. Resolves aws#11612 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Amazon EventBridge recently added support for dead letter queues.
Use Case
It makes event-driven applications more resilient and durable by storing your events in queues when the events can't be delivered, or the target is unavailable. See the documentation for more information.
Proposed Solution
Following the CloudFormation documentation, it is possible to pass the deadLetterConfig at the rule level and at the target level. I suspect it makes more sense to set it at the target level so we can target different DLQs for targets on the same rule if needed.
A target would have the possibility to pass a Queue as a property. That would be straight forward. Also, we would need to attach a policy to the queue to allow the rule to SendMessage to the queue.
See below a usage example.
Others
I'm happy to have a go at it.
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: