Some limits are not appearing

[ddemaret-plaid]

Describe the bug

I've deploy the solution into multiple accounts but can't find any trace of any Amazon SageMaker or Amazon CloudFront quota's in the DynamoDB. More could be missing, I haven't checked them all.

To Reproduce

Deploy the solution, then query the data that has been collected and look for any traces of Amazon SageMaker or Cloudfront quotas. For example "Cookies per cache policy".

Expected behavior

All quota's are collected in the dynamodb table QMTable.

Please complete the following information about the solution:

• Version: [e.g. v1.0.0]
  v6.2.9

• Region: [e.g. us-east-1]
  us-east-1

• Was the solution modified from the version published on this repository?
  no

• Have you checked your service quotas for the services this solution uses?

• Were there any errors in the CloudWatch Logs? How to enable debug mode?
  None that I could find

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

SELECT distinct(service)
FROM "default"."quota-monitor-hub-qmtable336670b0-1n3u9ljhx0m6l"

"service"
"DynamoDB"
"Bedrock"
"Connect"
"SSM"
"Route53"
"DiagnosticTools"
"Kinesis"
"SNS"
"Location"
"ECR"
"SES"
"AppSync"
"Fargate"
"IoT"
"CloudWatch"
"NeptuneGraph"
"Lightsail"
"KMS"
"RDS"
"RoboMaker"
"VPC"
"CloudTrail"
"EMR"
"EBS"
"Braket"
"Textract"
"ELB"
"NetworkMonitor"
"Firehose"
"EventBridge"
"IVS"
"AutoScaling"
"FIS"
"IAM"
"Athena"
"CloudFormation"
"IVSChat"
"AppIntegrations"
"RolesAnywhere"
"TrustedAdvisor"
"Logs"
"EC2"
"CloudHSM"

Additional context
Add any other context about the problem here.
All services have been enabled in SQServiceTable including sagemaker and cloudfront.

[sanjay-reddy-kandi]

Thank you for reporting this issue and providing detailed information. We understand that you're unable to find any traces of Amazon SageMaker or Amazon CloudFront quotas in the DynamoDB table, despite having enabled these services in the SQServiceTable.

We will investigate this issue and work on identifying the root cause. In the meantime, we would appreciate if you could provide us with any additional information or logs(specifically QM-ListManager-Function logs) that might be helpful in troubleshooting this issue.

[ddemaret-plaid]

Sure. Here's some logs

[sanjay-reddy-kandi]

When I run aws service-quotas list-service-quotas --service-code cloudfront , I see no quotas, so we do not monitor Cloudfront service. Even for the services supported by service quotas, we filter out metrics that do not have CloudWatch AWS/Usage. For the SageMaker and the Warnings in the logs, we are releasing a patch this week. Hope it helps!

[ddemaret-plaid]

When I run aws service-quotas list-service-quotas --service-code cloudfront , I see no quotas, so we do not monitor Cloudfront service. Even for the services supported by service quotas, we filter out metrics that do not have CloudWatch AWS/Usage. For the SageMaker and the Warnings in the logs, we are releasing a patch this week. Hope it helps!

Oh it seems you are right. Is that a bug in the aws cli since cloudfront does have quotas?

[sanjay-reddy-kandi]

yeah this could be a bug or a temporary issue with the Service Quotas API for CloudFront.

[ddemaret-plaid]

Created an issue here: aws/aws-cli#8941

[sanjay-reddy-kandi]

Just pointing it out again, Even if that cli works, we will not monitor cloudfront because its quotas have got no Utilization metrics

[ddemaret-plaid]

Aaah sorry I misunderstood. Is this because all utilisation metrics come from cloudwatch? And cloudfront metrics aren't there? (failing this check i assume) Would you have a list of which other metrics are missing and would you have any idea if they will ever be added?

[sanjay-reddy-kandi]

Yes that is the right code check. I don't know the specifics but Service quota team is the right team to answer that question but based our team discussion with the them, they are onboarding lot of AWS services

[sanjay-reddy-kandi]

This issue is fixed in the latest version v6.2.11