AWS Config Recorder Not Enabled
Resource configuration history is not recorded, so you cannot tell what a resource looked like before a change.
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: Enable AWS Config recorder.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- Config Recorders on AWS
- The fix, by hand
- AWS Config → Settings → enable recorder → All resources + global resources (only on the home region).
- Choose an S3 delivery channel with lifecycle policy (transition over 90 days to Glacier).
- Repeat in every active region (or use a CloudFormation StackSet for the org).
- Optionally enable conformance packs (CIS, PCI-DSS, NIST 800-53) for managed compliance rules.
- Verify the recorder is healthy (Status → green).
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-1520- 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.