EBS snapshot shared publicly
EBS snapshots can be shared with specific accounts or made public. A public snapshot can be copied by any AWS user, exposing whatever was on the volume.
Why it matters
Public snapshots have leaked source code, credentials and customer data; researchers routinely scan for them.
It's easy to make a snapshot public by mistake when trying to share it with one account.
How to check for it
- aws ec2 describe-snapshots --owner-ids self --restorable-by-user-ids all --query "Snapshots[].SnapshotId" lists snapshots shared with everyone.
- Check each region separately.
How to fix it
- Remove public access: aws ec2 modify-snapshot-attribute --snapshot-id <id> --attribute createVolumePermission --operation-type remove --group-names all.
- Share with specific account IDs only, and encrypt snapshots so they can't be shared publicly at all.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.
FAQ
- Can encrypted snapshots be made public?
- No — AWS does not allow encrypted snapshots to be shared publicly, which is another reason to encrypt by default.