You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is what I got from AWS support. It seems this solution does not send new findings to slack automatically
AWS support reply:
"I understand that your saying that any new findings are not automatically sent to Slack and that you need to always manually trigger the custom action. Please let me know if I am not understanding your issue correctly. In that case, I need to inform you that custom action always need to be triggered manually, meaning that for all new findings you would need to select them and then trigger the custom action to send to Slack. New findings will not be automatically sent to Slack since the custom action has not been triggered. Once the custom action has been triggered manually, then the new findings will be sent to Slack."
Expected behavior is that new alerts are sent to the slack channel automatically.
Using the latest cloudformation template and following the setup guide automatic alert notification does not get sent to the slack channel.
Updates to the slack channel must be initiated from the page https://console.aws.amazon.com/securityhub/home?region=us-east-1#/insights/arn:aws:securityhub:::insight/securityhub/default/ and after all messages are selected the Action drop down menu selected and the slack bot name clicked on.
The text was updated successfully, but these errors were encountered: