Check ID:
Provider: AWS
Service:
Severity: LOW
Categories:
Resource type:
ec2_instance_detailed_monitoring_enabledProvider: AWS
Service:
ec2Severity: LOW
Categories:
logging, forensics-readyResource type:
AwsEc2InstanceWhat this check verifies
EC2 instances are assessed for CloudWatch detailed monitoring, indicating whether 1-minute metrics collection is enabled. Instances lacking this setting provide only 5-minute metrics.Risk
Without 1-minute metrics, visibility drops, delaying detection of:- Sudden CPU/network/disk spikes affecting availability
- Malicious workloads (crypto-mining, brute force)
- Data exfiltration patterns Slower detection expands blast radius, raising incident impact and response cost.
Recommendation
Enable detailed monitoring to collect1-minute metrics on critical instances. Use defense in depth: baseline normal behavior, create alerts for anomalies, and correlate metrics with logs and traces. Review dashboards regularly. If costs matter, prioritize production, internet-facing, and autoscaling fleets.
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws ec2 monitor-instances —instance-ids <EC2_INSTANCE_ID>
References
- https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cloudwatch-new.html
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/EC2/instance-detailed-monitoring.html
- https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cloudwatch-new.html#enable-detailed-monitoring-instance
Where this check fires
This check runs on every scheduled scan against your AWS account. Findings appear at Cloud Security → Findings filterable byCheck ID = ec2_instance_detailed_monitoring_enabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to AWS checks