Course contentsShow
← Security
Lesson 1770 of 3,05236. Cloud Security - Data ProtectionFree lesson

Encryption for Block Storage and Virtual Disks

Learn how encryption works for EBS volumes, persistent disks, and boot volumes with performance considerations.

Encryption for Block Storage and Virtual Disks

What you'll learn: How cloud providers encrypt block storage volumes (like EBS, Azure Disks, and Persistent Disks) and what performance trade-offs you need to consider.

What Is Block Storage Encryption?

Block storage volumes—AWS EBS, Azure Managed Disks, GCP Persistent Disks—act as virtual hard drives attached to your cloud instances. Encryption for these volumes protects data at rest by encrypting every block written to disk using AES-256 or similar algorithms. This happens transparently: your application writes data normally, but the cloud provider intercepts writes, encrypts them using keys from KMS or HSM, and stores encrypted blocks on physical hardware.

How It Works

When you enable encryption (often the default now), the cloud provider:

  1. Generates a data encryption key (DEK) for each volume
  2. Encrypts the DEK with your KMS key (the key encryption key)
  3. Stores the encrypted DEK with the volume metadata
  4. Decrypts blocks on-the-fly when your instance reads data
  5. Encrypts blocks on-the-fly when your instance writes data

Think of it like a locked safe (the disk) with a unique lock (DEK), and only your master keyring (KMS key) can unlock it.

Performance Considerations

Modern cloud providers use hardware-accelerated encryption in their hypervisors, so performance impact is minimal—typically under 5% overhead for most workloads. Boot volumes use the same encryption mechanisms, adding only seconds to boot time as keys are retrieved.

Key differences:

  • Customer-managed keys may add latency if KMS calls are throttled
  • IOPS and throughput limits remain unchanged with encryption
  • Snapshot encryption inherits the volume's encryption state

Key Takeaway: Block storage encryption protects data at rest with negligible performance impact by leveraging hardware acceleration and KMS-managed keys, making it a security baseline you should enable by default.