AWS KMS Overview and Key Types
You'll learn how AWS Key Management Service (KMS) structures its key hierarchy and the differences between customer managed, AWS managed, and AWS owned keys.
What is AWS KMS?
AWS KMS is a managed service that creates and controls encryption keys used across AWS services and your applications. Think of it as a secure vault with built-in access controls—instead of storing encryption keys in your code or configuration files, KMS stores them in hardware security modules (HSMs) and lets you define who can use them and for what purpose.
KMS implements the envelope encryption pattern you've already learned: it manages Key Encryption Keys (KEKs) that encrypt your Data Encryption Keys (DEKs), establishing a root of trust for your encryption hierarchy.
Three Key Types
Customer Managed Keys (CMKs)
Keys you create, own, and fully control. You define key policies, enable/disable them, schedule deletion, and manage rotation. These appear in your KMS console and give you complete visibility through CloudTrail logs. Use these when you need audit trails, custom policies, or specific compliance requirements.
AWS Managed Keys
Keys created automatically by AWS services on your behalf (like aws/s3 or aws/rds). AWS handles rotation (every year automatically), but you cannot delete, disable, or change their key policies. They're convenient for server-side encryption with AWS-managed keys, but offer less control.
AWS Owned Keys
Keys owned by AWS, shared across multiple accounts, invisible to you. Used internally by services for default encryption. You never see them in KMS, can't audit their usage, and have zero control—but also zero cost. Most users never interact with these directly.
Key Takeaway: AWS KMS provides three key types with decreasing control but increasing convenience—customer managed keys for full control and compliance, AWS managed keys for service-specific automation, and AWS owned keys for invisible default encryption.