Check ID:
Provider: AWS
Service:
Severity: HIGH
Categories:
Resource type:
ec2_ebs_volume_snapshots_existsProvider: AWS
Service:
ec2Severity: HIGH
Categories:
resilience, forensics-readyResource type:
AwsEc2VolumeWhat this check verifies
EBS volumes are evaluated for the existence of at least one associated snapshot, identifying volumes without any point-in-time backup available.Risk
Missing EBS snapshots removes point-in-time recovery. Accidental deletion, corruption, or ransomware can cause irrecoverable data loss and prolonged service outages, degrading data integrity and availability and complicating recovery and forensics.Recommendation
Establish automated, policy-based EBS snapshot coverage for all volumes aligned to businessRPO/RTO.
- Schedule regular snapshots with retention controls
- Encrypt snapshots and enforce least privilege access
- Replicate to another Region/account for DR
- Periodically test restores and document procedures
Remediation
- CLI
- Terraform
- Native IaC
- Dashboard steps
aws ec2 create-snapshot —region <REGION> —volume-id <VOLUME_ID>
References
- https://docs.aws.amazon.com/ebs/latest/userguide/ebs-snapshots.html
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/aws/EBS/ebs-volumes-recent-snapshots.html
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_ebs_volume_snapshots_exists. 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