AWS Config Rule with No Evaluations
The rule has never assessed anything, so a control you believe is in force is not actually checking.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Rescope or delete the unused AWS Config rule.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- AWS Config Rules on AWS
- The fix, by hand
- AWS Config → Rules → the resource → review the evaluation history.
- Confirm zero non-compliant findings in the last 90 days AND the rule scope still matches live resources.
- If the rule belongs to a Conformance Pack, edit / delete the pack instead of the rule directly (otherwise it will re-deploy).
- If duplicate, identify the canonical rule and delete this one.
- If misconfigured, fix the parameters rather than delete.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-199- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.