S3 general purpose buckets ServiceQuota check doesn't work outside of us-east-1

[rfairburn]

AWS no longer reports the s3 generalpurposebuckets servicequote as valid metric for s3 outside of us-east-1, but the us-east-1 test doesn't look at global buckets, so this no longer works as intended. The quota in us-east-1 is intended to be account-wide for the buckets.

[rfairburn]

From what I can tell, the number of used buckets is polled correctly in us-east-2, but the graph in the dashboard can't function because there is no corresponding region-specific quota anymore. I believe this is a recent change on the AWS side, but it breaks this functionality.

[max-rocket-internet]

From what I can tell, the number of used buckets is polled correctly in us-east-2

Are your buckets in this region?

[rfairburn]

All of my buckets are in us-east-2, but recently (as of the last month or 2), it appears that the ServiceQuota for buckets no longer exists at all in us-east-2, but has to be set globally in us-east-1 only. So the metrics error when trying to apply and I have to actually exclude the service s3 in us-east-2 for the terraform to even apply.

So I can poll the number of buckets with the graph, but it is divided by the service quota, which generates an error.

This is what I mean under service quotas:

Notice that General purpose buckets no longer even exists outside of us-east-1 and is an Account-level quota now.

There is a concept of Global quotas in the trusted advisors alarms currently, but this one is managed by usage alarms which doesn't currently have a concept of global.

If I get some time I may be able to PR what I would do to address it, but I wanted to make sure the problem was stated in an issue first.

[max-rocket-internet]

If I get some time I may be able to PR what I would do to address it

That would be great 🙂