-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
[extra7132, extra7133, extra7113] Fails for DocumentDB instances #811
Comments
Thanks for let me know, in the meantime you can use the whitelist feature to prevent that fail. |
Can you please try changing the checks with this query instead and see if that fixes the issue? |
It almost worked - I just had to set the string in single quotes: |
Hi,
the rds describe-db-instances command (as used by the checks extra7132, extra7133, and extra7113) also lists DocumentDB instances which do not support enhanced monitoring/multi-AZ/deletion protection [1]. So these checks fail if you have a DocumentDB cluster and it's not possible to fix the checks.
Proposed solution:
[1] DocumentDB does support deletion protection, but it's a configuration option for clusters, not individual instances. See result of docdb describe-db-clusters.
The text was updated successfully, but these errors were encountered: