Multiple CloudFormation Throttle rate limit for * Alerts

[tivanov-qb]

Describe the bug

We recently started seeing alerts firing for AWS CloudFormation service for multiple "Throttle rate limit for *" quotas. For example, it includes Throttle rate limit for DescribeStacks, Throttle rate limit for UpdateStack, Throttle rate limit for ListStackResources, etc. I tried to mute the alert updating the SSM param with adding: cloudformation:Throttle rate limit for*,CloudFormation:Throttle rate limit for* but this did not work :(

To Reproduce

Deploy the solution, configure it to report in slack and alerts will start firing

Expected behavior

I'd expect alerts like above to be not send to slack due to the fact they cannot be modified and have default value of 2. Or if this isn't possible, it would be great to allow muting all "Throttle rate limit" quotas at once using *

Please complete the following information about the solution:

• Version: v6.3.1

To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SOXXXX) - The AWS CloudFormation template for deployment of the AWS Solution. Version vx.y.z". You can also find the version from releases

• Region: QuotaMonitorHub is deployed into us-west-2, and Spokes are in multiple regions such as us-east-1, us-east-2, eu-central-1, eu-west-1
• Was the solution modified from the version published on this repository? No
• If the answer to the previous question was yes, are the changes available on GitHub?
• Have you checked your service quotas for the services this solution uses? Yes, solution sends alerts for quotas that are not modifiable
• Were there any errors in the CloudWatch Logs? How to enable debug mode? No

Screenshots
If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).

Additional context
Add any other context about the problem here.

[abewub]

Currently only * or an exact match is supported, but supporting a more general match for something like Throttle rate limit for* would be a good enhancement. I will add that to backlog.

In the mean time, you can have a comma separated list as in CloudFormation:L-6AD11AD7,CloudFormation:<ANOTHER_QUOTA>.

[tivanov-qb]

@abewub Do you think we could add an enhancement to allow filtering by specific accounts?
For example, if there’s a dev account in the organization, we might want to exclude only the Concurrent State Manager associations for that account, and only for certain regions.

[abewub]

Thanks for the request, I will add this to our backlog for prioritization.