search

brennerm / aws-quota-checker

Keep an eye on your AWS quotas before you hit their limits
https://pypi.org/project/aws-quota-checker/
MIT License
84 stars 36 forks source link

limit overrides #21

Open charleshepner opened 3 years ago

charleshepner commented 3 years ago

Some AWS services have not integrated with the quota service so the current implementation cannot get the applied limit and falls back to the default limit. For example we have gotten an S3 bucket limit increase to 300 buckets, so this quota checker will always indicate we are at the limit for number of s3 buckets.

Do you have any plans to implement a way to override individual checks to handle this type of scenario? Asking since we have a need for it and might tackle it in our fork (https://github.com/northwoodspd/aws-quota-checker). If you have ideas about how you'd like to see that approached, we'd have a better chance of getting such a feature accepted into your repo.

Per aws support:

------------------------------------------------------------------------
% aws service-quotas get-service-quota --service-code s3 --quota-code L-DC2B2D3D

An error occurred (NoSuchResourceException) when calling the GetServiceQuota operation:
------------------------------------------------------------------------

I then contacted an S3 SME regarding the above - please note, S3 has not yet been onboarded onto the get-service-quota API. Therefore, you will only not be able to view any increased limits for S3 buckets.

[snip]

Therefore, for the time being, it will only be possible to use the get-aws-default-service-quota API until the get-service-quota API is onboarded with S3. Additionally, although this feature is not currently available, I recommend you to follow our news channels to be updated on all service releases from us (please note we cannot give timelines for new feature releases):
charleshepner commented 3 years ago

We think lambda may be the same way (not integrated with the quota service), have a ticket open now.

brennerm commented 3 years ago

Well that's a bummer. Expected that this would have been implemented properly by AWS. Have to think about how a solution could look like.