-
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
Uncaught error from SES limit checks #397
Comments
I just tried with eu-central-1 and still getting AccessDenied error. |
If I recall correctly from some previous issue, error messages for services generally change before a service is enabled in a new region, and 503s are the last step before a service goes live. If anyone else can verify that SES in Given what we've seen on previous similar issues, I think we should definitely skip for both error messages. As I saw in #382, there are even cases where different accounts see different error messages for the same region... Unfortunately I don't think I'm going to be able to get to implementing and/or releasing a fix for this for a few days, as I have some personal commitments. @TimGebert until a fix is out, assuming you're using the CLI to run awslimitchecker, you can bypass this in the affected region with the |
i just tested with ap-southeast-2 and getting same error as reported. |
I've been able to reproduce this myself and am working on a fix now. Should have something out soon. |
This has been released as 6.1.5 and is now live on PyPI. Thanks so much for your help with this @TimGebert and @bergkampsliew |
Bug Report
SES Limit checks crash in regions where the service is not available. Similar issue to #375
First noticed the error on Friday 1st March at 12:23PM (AEDT)
If I swap to a different region (us-east-1), that supports SES, the error doesn't occur.
The error returned is a 503, Service Unavailable:
{'Error': {'Code': '503', 'Message': 'Service Unavailable'}, 'ResponseMetadata': {'HTTPStatusCode': 503, 'HTTPHeaders': {'content-length': '0', 'connection': 'keep-alive'}, 'MaxAttemptsReached': True, 'RetryAttempts': 4}}
It appears AWS might have changed their API, should the AccessDenied error that is currently caught in ses.py be changed to 503, or should a second check be added?
Version
awslimitchecker version: 6.1.4
AWS Region
ap-southeast-2 (Sydney)
Installation Method
awslimitchecker installed with command
pip install awslimitchecker==6.1.4
Supporting Software Versions
Python Version: 2.7.15
Also tested on 3.7.2
Actual Output
Expected Output
Limit Checker handle the error gracefully.
Testing Assistance
Can help to test if required.
The text was updated successfully, but these errors were encountered: