EBS Volume Not Encrypted
The volume and every snapshot taken from it are readable if copied or shared, including by accident.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Encrypt EBS volume.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- EBS Volumes on AWS
- The fix, by hand
- Confirm the workload can tolerate a maintenance window (stop / detach / attach cycle).
- EC2 → Volumes → select unencrypted volume → Actions → Create snapshot.
- EC2 → Snapshots → select → Actions → Copy snapshot → tick "Encrypt this snapshot" + pick KMS key → Copy.
- From the encrypted snapshot → Create volume → ensure same size + same AZ.
- Stop the instance → detach the old volume → attach the new encrypted volume at the same device name → start.
- Verify the workload, then enable EBS default encryption for the region: EC2 → Settings → EBS encryption → Manage → Always encrypt new EBS volumes.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-172- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.