-
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
Update ElasticCache default limits #488
Comments
I am preparing a pull request for this update |
We ran into the ElastiCache limits as well and it's a false positve. Please merge the pull request. |
Replied to the PR with a question regarding default limits. I'll get it merged this week. Sorry for the delay. |
Seems like the limits I specified in the description should be these updates instead
|
updated PR to match this. |
issue #488 - Update ElasticCache default limits
A fix for this issue has been merged to the develop branch and is slated for release in 10.0.0 on Monday, December 7, 2020. Anyone who is able to test the fix is strongly encouraged to do so, and comment on this issue with their results. Instructions for installing awslimitchecker from a git branch are available in the Installing for Development documentation. |
This has been fixed in 10.0.0, which is now live on PyPI and is being built on the Docker hub right now. Thank you so much for the contribution! |
Bug Report
When reporting a bug in awslimitchecker, please provide all of the following information,
as well as any additional details that may be useful in reproducing or fixing
the issue:
Version
awslimitchecker 9.0.0
Installation Method
Installed through pipenv and executed through python directly
Supporting Software Versions
Actual Output
Expected Output
Based on https://docs.aws.amazon.com/general/latest/gr/elasticache-service.html, these limits are no longer accurate and should be:
4020TrustedAdvisor
Not Applicable
Testing Assistance
Yes, i will be able to assist in testing pre-release code for the feature.
The text was updated successfully, but these errors were encountered: