Different alerts for different accounts

[bear176174]

I currently have this installed in our AWS environment to 3 separate spoke accounts. As a note there are also other accounts within our ORG that do not have Qutoa monitor monitoring them. The problem im running into is we do not want all alerts for each separate account to go into the same channel. The way it currently looks is it has the prerequisite account, and the hub account, followed by 3 spoke accounts, lets call them A, B, and C all pointed to a single slack channel for alerts. The way I would like it to look is spoke account A pointing to slack channel A, and spoke account B and C alerts pointing to slack channel B. Is this possible to configure while deploying this to our environments

[abewub]

Thanks for the request. This is currently not possible via configuration. The slack integration is central on the hub. However, if you specify SNS Spoke Region, the solution creates SNS topics per account. You can set up subscribers to each topic / account. A custom integration that posts to a slack channel can be added to these subscriptions.

[bear176174]

Can you please clarify about the SNS Spoke Region. Are you saying that during the install I can make it so each accounts gets a separate event bus that will let the alerts go to separate channels?

[abewub]

Yes, you can make the alerts to SNS topics per account. Specifying the SNS Spoke Region parameter enables that feature. If you are not using orgs and manually deploying spoke templates, you will have to deploy the quota-monitor-sns-spoke.template on each spoke account / region.

[bear176174]

I believe we are currently using the no-ou hub template so that we can specify which exact accounts we want to monitor as we dont want to see the alerts for all of them.But the hub account is where we deploy the templates at to create the infrastructure in the spoke accounts.

[bear176174]

To clarify the process, I would deploy the prerequisite to the appropriate account. Then the hub-no-ou to the hub account. I would then deploy the quota-monitor-sq-spoke template inside of the hub account, specifying which spoke accounts I want it to be in. Then finally deploy the SNS-spoke template using the hub account, specifying which spoke accounts I want to change the notifications in. I would then edit SNS topics in each of the spoke accounts to specify which slack channel I want them to post to. Does that look correct?

[abewub]

1. Since you are not using orgs, you don't need the prerequisite template.
2. Deploy the hub-no-ou template on your hub account.
3. Deploy the the sq-spoke template on your spoke accounts.
4. Deploy the sns-spoke template on your spoke accounts.
5. Update the SSM parameter /QuotaMonitor/Accounts with the list of accounts.

This will create separate SNS topics on each account. Then you can subscribe to those topics with different protocols. Here are some ways to integrate with slack.

[bear176174]

Thank you. I will be doing this today, if there are no issues I will marked this as answered.

[bear176174]

I was able to successfully deploy the Quota monitor infrastructure as instructed. However it is no longer actively sends the alerts. I created 5 test vpc in one of my accounts to try to trigger the message and it did not send it. We did not add the prerequisite to our root account as instructed, could this be the reason why?