De-duplicate detection and omission about terraform-aws-notify-slack HOT 5 CLOSED

Note: This feature depending how it is implemented may end up making this stack cost quite a bit more to host by having to have an ElasticCache deployed. Alternatively, could use something more serverless-friendly like DynamoDB which would have minimal added cost and complexity to this stack. Either way it adds to this stack's complexity.

from terraform-aws-notify-slack.

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

from terraform-aws-notify-slack.

un-stale

from terraform-aws-notify-slack.

I don't think we will be adding such deduplication logic into the module because this module does just one thing - forward messages to Slack.

In order to achieve the deduplication logic, it has to happen before calling this module.

Something like, GuardDuty/CloudTrail/etc -> SNS topic -> SQS queue to implement deduplication (read more) -> SNS topic clean -> This module to deliver message to Slack.

So, I am going to close this issue.

from terraform-aws-notify-slack.

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

from terraform-aws-notify-slack.