-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fails checking the region ap-northeast-3 #544
Comments
hey, I quickly checked and directory services isn't listed as a supported service for Osaka (ap-northeast-3): https://docs.amazonaws.cn/en_us/general/latest/gr/ds_region.html Does it fix anything if you ran this with |
It works. thanks. But I assumed that awslimitchecker can determine by itself which services are available in a region. |
Apologies for letting this sit so long. Unfortunately, awslimitchecker can't currently figure out on its own which services are available in a region. The real problem here is that AWS seems to have deployed endpoint DNS for every service in every region. It used to be that if a service wasn't supported in a region, either the DNS (i.e. There is now a solution for this built in to boto3; we can call My concern with that, though, is that it will require a boto3/botocore update to recognize new regions for a service. And, for anyone using the Docker image, it would require a new awslimitchecker release... which has been very infrequent lately. I think my gut reaction is to recommend just using |
seems that something was changed on AWS side because it worked a while ago.
awslimitchecker 11.0.0
Installation Method
virtualenv
Actual Output
The text was updated successfully, but these errors were encountered: