Encrypted Storage and Snapshots
You'll learn how to protect data at rest in cloud VMs by encrypting storage volumes and snapshots using encryption keys you control or the cloud provider manages.
What Is Storage Encryption in Cloud Compute?
When you launch a virtual machine, it uses block storage (like AWS EBS volumes) and sometimes ephemeral instance storage. By default, this data sits on physical disks in plaintext—if someone accesses the underlying hardware or steals a disk, your data is exposed. Storage encryption transforms this data into ciphertext using cryptographic keys, ensuring only authorized users with the right keys can read it.
Cloud providers let you encrypt:
- EBS volumes (persistent block storage attached to instances)
- Instance storage (temporary drives physically attached to the host)
- Snapshots (backups of your volumes stored in object storage)
Key Management Options
You have two primary choices:
AWS/Cloud-Managed Keys
The provider creates and rotates keys automatically. You enable encryption with a checkbox—simple but less control.
Customer-Managed Keys (CMK)
You create keys in the cloud's key management service (like AWS KMS), define usage policies, and control who can encrypt/decrypt. More overhead, but you decide access permissions and can revoke keys independently.
Why Encrypt Snapshots?
Snapshots are copies of your volumes stored for backup. If an unencrypted snapshot leaks or gets shared accidentally, attackers access your entire disk contents. Encrypted snapshots inherit encryption from the source volume—even if someone downloads the snapshot, they can't read it without your key.
Key Takeaway: Always encrypt EBS volumes, instance storage, and snapshots using customer or cloud-managed keys to protect data at rest from physical theft, unauthorized snapshots, or accidental exposure—encryption should be enabled at launch and enforced via policy.