Ability to send specific notifications to a different slack channel

[ddemaret-plaid]

Is your feature request related to a problem? Please describe.

We send notifications to 1 specific slack channel in our company. It would be nice if we can send specific notifications (for example any sagemaker notification) to a different slack channel.

Describe the feature you'd like

Similar to how we specify silences for notifications as described in https://docs.aws.amazon.com/solutions/latest/quota-monitor-for-aws/step-6.-configure-notifications-optional.html, it would be nice to specific different slack notifacations

For example

sagemaker:$WEBHOOKURL_1, *:$WEBHOOKURL_2

This would send everything sagemaker to $WEBHOOKURL_1 which is for example the slack channel #ml-notifications and then everything else goes to $WEBHOOKURL_2 which is #infra-notifications

[sanjay-reddy-kandi]

Thanks for this request. We will add this as a backlog item for the next release.

[G-Lenz]

hi @ddemaret-plaid

SNS contains filter policies that allow you to filter messages on subscriptions. This should allow you to subscribe a webhook to the SNS topic and add a filter policy so that the subscription only receives the desired notifications. In our upcoming release for 6.3.0 we will also have optional SNS stacks so that you can decentralize your notifications at an account level, this will add an SNS topic to the spoke account which will allow you to have different subscribers in each SNS such that they only get the notifications for that account, and will allow that SNS topic to be managed from the spoke account. The hub SNS will still exist if you wish to have centralized notifications managed from the hub account.

[shujacks]

The above mentioned new feature is requested by customers who have different teams owning different spoke accounts. Please let us know if that would be helpful for you.

[ddemaret-plaid]

Aaah that would be good. The setup would be a bit more elaborate than "Just put a webhook in this param" but might be worth it. I think the use case "different teams owning different spoke accounts" is something that we will hit eventually so this feature would help.