Encryption at Rest
What You'll Learn
You'll learn how to enable storage encryption using KMS (Key Management Service) keys to protect your managed database data at rest—so even if someone physically accessed your storage, they couldn't read your data.
What Is Encryption at Rest?
Encryption at rest means encrypting data when it's stored on disk—as opposed to when it's traveling over a network. For managed databases like RDS, this protects your data files, automated backups, snapshots, and replicas from unauthorized access.
Think of it like storing your valuables in a locked safe rather than leaving them on a shelf. Even if someone breaks into the room (gains physical access to the storage hardware), they can't access what's inside without the key.
How It Works in Managed Databases
When you enable encryption at rest for a managed database:
- You choose a KMS key during database creation (or use the default service key)
- The database engine encrypts all data before writing it to storage
- Decryption happens automatically when authorized applications read the data
- Backups and snapshots inherit encryption from the source database
The database engine handles encryption/decryption transparently—your applications don't need to change how they read or write data.
Why Enable It?
Encryption at rest protects against:
- Physical theft of storage devices
- Unauthorized access by cloud provider employees (defense in depth)
- Compliance requirements (HIPAA, PCI-DSS, GDPR often mandate it)
Important: Encryption must be enabled at database creation time—you can't add it to an existing unencrypted database without recreating it or restoring from an encrypted snapshot.
Key Takeaway: Encryption at rest uses KMS keys to automatically encrypt your database storage, protecting data even if physical media is compromised, and is essential for security compliance.