Service Quota Automatic Management issue

Hello.

There is a blog in Japanese that is testing the settings for the automatic service quota management feature.
According to this blog, there seems to be a time lag of about one day before the notification is sent.
It's difficult to determine whether this behavior is normal or a malfunction, but why not try waiting a day or so?
https://dev.classmethod.jp/articles/automatic-quota-management-service-quotas/

There could be several reasons why you're not receiving Service Quotas Automatic Management notifications in Slack:

1. Notification thresholds: Service Quotas Automatic Management sends notifications when quota usage reaches 80% and 95% utilization thresholds. If your VPC usage hasn't reached these thresholds, no notifications would be triggered.

2. Notification channel configuration: When enabling Automatic Management, you need to specifically enable the User Notification Service and select your preferred notification method (in this case, Slack). Make sure you've completed this step during setup.

3. Slack hook configuration: If you're using Slack for notifications, verify that the Slack webhook is correctly configured. You can check this by:

• Going to the AWS Systems Manager console
• Navigating to Parameter Store
• Verifying that the Slack hook parameter has the correct value

4. Mode selection: When setting up Automatic Management, ensure you've selected "Notify Only" mode (currently the only available option).

5. Exceptions: Check if you've added the VPC service to the exceptions list during setup, which would prevent monitoring and notifications for that service.

To troubleshoot further, check the AWS Health personal health dashboard where notifications should also appear, and consider reviewing any EventBridge events that might have been triggered by the quota usage change.
Sources
Service Quotas Automatic Management - Service Quotas
Troubleshooting - Quota Monitor for AWS
Getting started with Service Quotas Automatic Management - Service Quotas