1 回答
- 最新
- 投票最多
- 评论最多
0
Have you considered Lambda Destinations? With Destinations, you can move messages to SNS and then fan out to SQS and send automated alerts to concerned teams. When the issue is fixed, the messages can then be picked up from the SQS and moved to the EventBridge.
已回答 1 年前
相关内容
- AWS 官方已更新 8 个月前
So my concern with this is that A) multiple things may subscribe to the event and some of those may be successful. So I don't want those other things to trigger again if the event is placed back on EventBridge. And B), this requires an SNS and another SQS resource (for each lambda i setup this way). That sounds like a lot of additional resources just to redrive events back to the lambda. SQS supports this nicely with the redrive features, thinks that land on the DLQ can easily be sent back to the main queue. With Lambda DLQ, it would be great if you could redrive the events back to the lambda internal queue, but that feature just doesn't exist (yet). Its just interesting that AWS offers this DLQ feature on lambdas but no real examples or best practices on how to utilize it.