Multiple emails for single Limit Code

[aj-max-svg]

Quota Service Monitor sends 12 emails for a single Limit Code.

Deployed the following templates in a single account:
us-west-2
(SO0005-NoOU) - quota-monitor-for-aws version:v6.2.2 - Hub Template, use it when you are not using AWS Organizations
(SO0005-SQ) - quota-monitor-for-aws version:v6.2.2 - Service Quotas Template

us-east-1
(SO0005-TA) - quota-monitor-for-aws version:v6.2.2 - Trusted Advisor Template

When the event rule fires, only one Limit Code is found, but I receive 12 emails for it. It appears there is a record logged every hour of the limit code, and each one gets sent as a notification. (see the timestamp fields in the screenshot)

To Reproduce

Deploy the solution and wait for the event rule to fire.

Expected behavior

A single email for each limit code
Please complete the following information about the solution:

• [ 6.2.2 ] Version: [e.g. v1.0.0]

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

• [ us-west-2 ] Region: [e.g. us-east-1]
• [ No ] Was the solution modified from the version published on this repository?
• 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?
• [ No ] Were there any errors in the CloudWatch Logs? How to enable debug mode?

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]

Thanks for the feedback. Those emails are have timestamps which are 1 hour apart - thus 12 for the day. Quota Monitor can be configured to run every 6 or 12 hours. So you will get 6 or 12 email for the past 6 or 12 hour periods. At this point that 1 hour period is not configurable. It could be a good idea to expose that as a template parameter.

[KadalurSupreeth]

Hello,
The latest version 6.3.0 still lacks a customized solution to prevent multiple email notifications. It would be ideal to have a template parameter that allows users to set their preferred notification frequency. Could you let me know if this issue has been resolved or is it still in the backlog? It would be great to address this issue as soon as possible, as receiving numerous email notifications for the same LimitCode is quite frustrating.

Example: I have scheduled the CW Poller Lambda to run every 24 hours.

1. CloudTrail usage metrics are generated every hour by design, resulting in 24 notifications per day.
2. Firehose usage metrics are generated every minute.
3. Elastic IP usage metrics are generated every 24 hours.
   Therefore, the number of emails generated per day varies depending on the AWS services.

I have made changes in the CW Lambda file to meet the immediate need but would prefer to expose this value through the CFT template.

Lambda: cwPoller
File: exports.ts

The below constant may not be used at all.

/**

• @description period of 1hr for metric stats
  */
  export const METRIC_STATS_PERIOD = 3600;

Additionally, there is another hardcoded value in the same file, as shown below. By changing this value to 86400, I was able to limit the notifications to one email per LimitCode per day.

/**

• @description generates CW GetMetricData queries for all quotas
• @param quotas
  */
  export function generateCWQueriesForAllQuotas(quotas: ServiceQuota[]) {
  const sq = new ServiceQuotasHelper();
  const queries: MetricDataQuery[] = [];
  quotas.forEach((quota) => {
  try {
  queries.push(...sq.generateCWQuery(quota, 3600));
  } catch (_) {
  // quota throws error with generating query
  }
  });
  return queries;
  }

I recognize the difference between aggregating value hourly versus daily, but this approach meets my needs.

[mikejavadivastspace]

Thank you @KadalurSupreeth for the workaround. Perhaps if this was in python, I would have fixed it. But not a node person. I had the frequency at rate(12 hours) and we were getting 12 emails instead of one. This fixed it.

[JSChronicles]

I'm having the same issue with my org. This is pretty painful when you hit iam percentage limits

[tjsching]

I'm running into the same issue with my organization. Thank you for posting this.

[abewub]

Thanks for the feedback. I have added a backlog item to make this a template parameter with the current hard coded value (1hr) being the default.