EC2 Detailed Monitoring Not Enabled
Metrics arrive at five-minute granularity, so short spikes that cause user-visible errors never appear on the graph.
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 detailed monitoring on EC2 instance.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- EC2 Instances on AWS
- The fix, by hand
- Decide whether 1-minute granularity is worth the per-instance cost (~$2-3/month). Production-tier services usually yes, dev/test rarely.
- EC2 → select the resource → Actions → Monitor and troubleshoot → Manage detailed monitoring.
- Toggle Detailed monitoring → Enable → Save.
- CloudWatch → Metrics → EC2. Confirm the 1-minute resolution appears within 5 min.
- Update any CloudWatch alarms that previously depended on 5-minute granularity (Period / EvaluationPeriods).
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-151- 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.