Course contentsShow
← Cloud and Infrastructure
Lesson 2300 of 2,98949. KMS and EncryptionFree lesson

Server-Side Encryption with Customer-Managed Keys

Master using KMS-managed keys you control for encryption, balancing security and operational convenience.

Server-Side Encryption with Customer-Managed Keys

What you'll learn: How to use your own KMS-managed keys to encrypt cloud data, giving you control over encryption while the provider handles the operations.

The Sweet Spot Between Control and Convenience

Server-Side Encryption with Customer-Managed Keys (SSE-CMK, sometimes called SSE-C in AWS or CMK-based encryption) represents a middle ground: the cloud provider still performs encryption/decryption on their infrastructure, but you control the key through a Key Management Service (KMS) like AWS KMS, Azure Key Vault, or Google Cloud KMS.

Unlike Server-Side Encryption with Provider Keys (where the provider owns everything), or Server-Side Encryption with Customer Keys (where you supply raw keys with every request), CMK gives you:

  • Policy control – You define who can use your keys via IAM and key policies
  • Audit trails – Every encryption/decryption operation is logged
  • Rotation flexibility – Enable automatic key rotation on your schedule
  • Revocation power – Delete or disable keys to make encrypted data inaccessible

How It Works in Practice

When you create a storage bucket, database, or disk and enable CMK encryption:

  1. You specify a KMS key ARN/ID that you created
  2. The service requests encryption operations from KMS on your behalf
  3. KMS checks policies to ensure the service has permission to use your key
  4. Data Encryption Keys (DEKs) are generated using your key encryption key (KEK)
  5. All operations are logged to CloudTrail/Activity Logs

The cloud provider handles the cryptographic heavy lifting, but you retain the "master switch."

Key Takeaway: Customer-Managed Keys give you meaningful control over encryption keys through KMS policies and audit logs, without the operational burden of supplying keys manually with every API call—ideal for regulated environments requiring key governance.