EBS volumes not encrypted at rest
EBS volumes back your EC2 instances' disks. When a volume is unencrypted, its data — and any snapshot taken from it — is stored without encryption at rest.
Why it matters
A snapshot copied or shared from an unencrypted volume exposes the raw data; encryption at rest is a baseline control for regulated workloads.
Encryption by default is a single account/region setting, so there's little reason to leave new volumes unencrypted.
How to check for it
- aws ec2 describe-volumes --query "Volumes[?Encrypted==\`false\`].VolumeId" per region.
- Check 'EBS encryption by default' in the EC2 account attributes for each region.
How to fix it
- Enable encryption by default: aws ec2 enable-ebs-encryption-by-default (per region).
- Re-encrypt existing volumes by creating an encrypted snapshot copy and replacing the volume.
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
- Does encryption by default cover existing volumes?
- No — it applies to newly created volumes and snapshots. Existing unencrypted volumes must be migrated via an encrypted snapshot copy.