Account does not block public sharing of EBS snapshots
- Severity
- High
- Service
- EC2
- Check ID
- EBS_SNAPSHOT_PUBLIC_ACCESS_NOT_BLOCKED
What this check finds
EBS snapshot block public access is set to "unblocked" for this account, so any snapshot can be shared publicly. The per-snapshot check only sees snapshots that exist today; this default governs every snapshot created from now on, including by automation nobody is watching.
Passing looks like: Account blocks public EBS snapshot sharing.
How to fix it
Enable snapshot block public access.
AWS CLI
aws ec2 enable-snapshot-block-public-access --state block-all-sharing
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
EC2 → EC2 Dashboard → Data protection and security → Block public access for EBS snapshots → Edit.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs
More EC2 checks
- HighAMI is publicly shared
- HighEBS snapshot is public
- HighEC2 instance CPU spiked abnormally — possible compromise or runaway process
- HighEC2 instance has an IAM role with admin privileges
- MediumAccount default for instance metadata does not require IMDSv2
- MediumEBS default encryption is not enabled for this region
- MediumEBS volume is not encrypted at rest
- MediumEBS volume is unattached and incurring storage cost