# Key Management

Key management is the controlled creation, protection, use, rotation, and retirement of cryptographic keys throughout their lifecycle.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/key-management

> Encryption depends on keeping cryptographic keys protected while making them available to authorized systems. Key management defines who controls those keys, how applications use them, and how access is audited and recovered, supporting both encryption at rest and encryption in transit.

Practice exams covering Key Management: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate).

## 6 key aspects of Key Management

Effective key management combines protected key material, controlled access, lifecycle governance, and recovery planning for encrypted data and communications.

1. **Lifecycle control**: Manage keys from secure generation through activation, rotation, retirement, and destruction. Retention decisions must preserve decryption access for data and backups that are still required.
2. **Protected key storage**: Keep key material out of source code, logs, and unprotected configuration files. Managed key services and hardware security modules can protect keys and perform cryptographic operations without exposing the protecting key to applications.
3. **Least-privilege key access**: Authorize only the identities and operations required for each workload. Separate permission to administer a key from permission to decrypt application data where practical.
4. **Protection at rest and in transit**: Use storage encryption for persisted data and protocols such as TLS for network connections. Each requires appropriate key controls; enabling one does not automatically enable the other.
5. **Envelope encryption**: Encrypt data with a data key and protect that data key with a separate key-encryption key. This supports efficient bulk encryption while centralizing control over the protecting key.
6. **Auditability and availability**: Record key administration and cryptographic operations where supported, and investigate unexpected usage. Test the effects of denied permissions, disabled keys, and recovery procedures before they cause production outages.

## Cloud services for Key Management

AWS KMS centralizes key authorization for integrated services such as Amazon S3, while S3 applies encryption to stored objects. AWS Certificate Manager addresses a different layer by managing TLS certificates used by supported endpoints to protect traffic in transit. AWS CloudHSM supports workloads that require dedicated HSMs and more direct cryptographic control rather than serving as a mandatory component of every encryption design. AWS CloudTrail supplies audit records for KMS activity. Together, these services illustrate the separation between encrypting data, controlling keys, securing connections, and monitoring access; each layer still requires appropriate configuration and permissions.

- **[AWS CloudHSM](https://blowstack.com/tools/cloud-services-hub/aws-cloudhsm)**: AWS CloudHSM provides dedicated hardware security modules for workloads that need direct control over cryptographic keys and operations. Customers manage HSM users, keys, and application integration, accepting more operational responsibility than with a typical integrated key service.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon S3 supports server-side encryption at rest, including options using S3-managed keys or AWS KMS keys. With SSE-KMS, access can depend on both S3 authorization and the required KMS permissions; HTTPS separately protects transfers.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records AWS KMS API activity, supporting investigation of key administration and cryptographic use. Engineers can use these records to review unexpected decrypt requests, policy changes, or key deletion scheduling.

## Key Management exam questions

Real practice exam questions on Key Management, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A company stores documents in Amazon S3 using server-side encryption with a customer managed encryption key. An application's IAM role has permission to read the required S3 objects, but requests fail because the role is not authorized to decrypt them. The company must allow the application to read the documents without changing their encryption. Which solution meets this requirement?

**Correct answer:** Grant the application's role permission to decrypt using the customer managed key in AWS KMS.

**Explanation:** Reading objects encrypted with a customer managed KMS key requires both S3 read permission and authorization to use the key for decryption. Allowing the role to decrypt with the relevant key addresses the missing authorization without changing encryption.

### Question 2 (DEA-C01)

**Question:**

A company's data lake stores Amazon S3 objects encrypted with a symmetric customer managed AWS KMS key. An administrator accidentally schedules the key for deletion with a 30-day waiting period. The next day, analytics jobs can no longer read the objects. The key is in the PendingDeletion state, and the jobs' S3 and KMS permissions have not changed. A data engineer must restore access using the existing key without copying or re-encrypting the objects. Which action should the data engineer take?

**Correct answer:** Cancel the scheduled key deletion, and then enable the existing KMS key.

**Explanation:** Canceling deletion moves the KMS key to the Disabled state. Enabling it then restores its availability for cryptographic operations, allowing authorized jobs to decrypt the existing objects without rewriting them.

### Question 3 (SCS-C03)

**Question:**

A company archives confidential records encrypted directly with the AWS KMS Encrypt API. One archive uses a single-Region symmetric KMS key with AWS-generated material. A second archive uses a single-Region symmetric KMS key with imported material. The company retains a protected external backup of the imported material.

An administrator schedules both KMS keys for deletion, and the waiting periods expire. Both key resources are permanently deleted. The company retains the ciphertext and original alias names but has no other copies of the records.

The recovery team proposes creating replacement KMS keys and recreating the original aliases. Which assessment of the company's ability to recover the records through AWS KMS APIs is correct?

**Correct answer:** Neither archive can be recovered through AWS KMS. A replacement key cannot decrypt ciphertext bound to a permanently deleted KMS key, even if the replacement contains the same imported material.

**Explanation:** Permanent deletion destroys the KMS key resource and prevents AWS KMS from decrypting ciphertext associated with it. AWS-generated symmetric material cannot be exported for customer recovery. An external backup of imported material can restore deleted or expired material to an existing compatible key, but it cannot recreate a permanently deleted KMS key's identity.

### Question 4 (SAA-C03)

**Question:**

A company is temporarily suspending an application that encrypts confidential records with a dedicated symmetric customer managed AWS KMS key. The key material was generated by AWS KMS. During the suspension, all encryption and decryption operations that use this key must be blocked, even for principals that retain their existing key-use permissions. The suspension might last several months. The company must be able to restore access to existing records afterward without re-encrypting data or changing the application's configured key ARN. Which action should a solutions architect take?

**Correct answer:** Disable the KMS key for the duration of the suspension, and enable it when the application resumes.

**Explanation:** Disabling a customer managed KMS key blocks its use for cryptographic operations regardless of existing key-use permissions. The key material and ARN remain intact. Enabling the key afterward restores the ability to decrypt existing records without re-encryption or application configuration changes.

### Question 5 (DOP-C02)

**Question:**

A company is deploying an application in two AWS Regions. The application uses client-side envelope encryption: each record is encrypted with a data key, and the encrypted data key is stored with the record. The encrypted records and encrypted data keys are replicated unchanged to the recovery Region.

During a complete outage of the primary Region, recovery workers must decrypt existing records by making AWS KMS requests only to the recovery Region. Replication must not require cryptographic API calls or access to plaintext data keys. Security policy requires automatic annual rotation of the protecting key material. An infrastructure-as-code pipeline must provision the keys and permissions before the application launches.

Which key-management design meets these requirements?

**Correct answer:** Create a symmetric multi-Region KMS primary key and a replica in the recovery Region. Enable annual automatic rotation on the primary key. Configure each key's regional policy and the workers' permissions, and configure recovery workers to use the replica's regional ARN for decryption.

**Explanation:** Related multi-Region KMS keys share key material and a key ID, allowing the recovery replica to decrypt data keys encrypted by the primary without re-encryption or a request to the primary Region. Automatic rotation is configured on the primary and AWS KMS synchronizes the rotated key material to its replicas. Key policies and permissions must be configured independently for each regional key.

## Practice Key Management in a full exam

Questions on Key Management in each practice exam, with every answer option and an explanation for each:

- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 4 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 4 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 2 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 2 questions
- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 1 question

## What is Key Management

Key management is the operational discipline behind secure encryption. A strong encryption algorithm provides little protection if its keys are exposed alongside the encrypted data or available to unauthorized users. Effective key management covers secure generation, storage, distribution, authorized use, rotation, recovery, and eventual destruction. It also assigns responsibility for each stage so that neither the cloud provider nor the customer assumes the other has handled a required control.

Encryption at rest protects stored information, such as objects, database files, disks, and backups. Cloud services can often encrypt this data automatically, but engineers must still understand which keys are used and who can authorize decryption. Provider-controlled keys reduce administrative work. Customer-managed keys offer more direct control over permissions, lifecycle settings, and auditability, but introduce configuration and availability responsibilities. Customer-managed does not necessarily mean the customer holds or can export the underlying key material.

Encryption in transit protects information moving between endpoints, commonly through TLS for HTTPS connections. TLS uses certificates and asymmetric cryptography to authenticate endpoints and establish shared session keys that encrypt traffic. Protecting certificate private keys and renewing certificates are therefore important management tasks. Encrypting a storage volume does not encrypt network traffic, and enabling HTTPS does not automatically encrypt the destination database or its backups.

Cloud systems frequently use envelope encryption. A data key encrypts the actual data, and a separate key-encryption key protects that data key. The encrypted data key can be stored with the ciphertext because access to the protecting key is still required to recover it. This approach allows efficient local encryption of large datasets while centralizing protection and authorization for higher-level keys. Plaintext data keys should exist only where needed and should not be written into logs, source repositories, or application configuration.

For example, an application might upload reports to object storage using server-side encryption with a customer-managed key. Its workload identity needs the relevant storage permissions and the required key permissions. A user who can retrieve an encrypted object might still be unable to decrypt it, depending on the encryption configuration and authorization path. Conversely, encryption does not stop a compromised application identity that already has permission to read and decrypt the reports.

Key rotation introduces new key material to limit continued reliance on an older key. It does not inherently re-encrypt existing data or undo a previous disclosure. Older key material may need to remain available to decrypt retained records and backups. Disabling a key can interrupt applications immediately, while permanently deleting necessary key material can make data unrecoverable. Recovery plans must therefore account for both encrypted data and access to its keys.

The practical trade-off is control versus operational burden. Dedicated hardware security modules can satisfy specialized custody or cryptographic requirements, but require more design and administration than an integrated managed key service. Apply least privilege, separate key administration from data access where practical, audit key operations, and test recovery. For exam scenarios, first identify whether the requirement concerns stored data, network traffic, or control over cryptographic keys; these are related but distinct concerns.

## Learn Key Management in lessons

5 short lessons on Key Management in 5 certification courses.

- CLF-C02: Key Management: ownership and control of encryption keys (Premium), https://app.blowstack.com/lessons/key-management-ownership-and-control-of-encryption-keys-clf-c02
- DEA-C01: Key Management: authorized key use (Premium), https://app.blowstack.com/lessons/key-management-authorized-key-use-dea-c01
- SCS-C03: Key Management: key material origin (Premium), https://app.blowstack.com/lessons/key-management-key-material-origin-scs-c03
- SAA-C03: Key Management: control throughout the key lifecycle (Premium), https://app.blowstack.com/lessons/key-management-control-throughout-the-key-lifecycle-saa-c03
- DOP-C02: Key Management: policy-driven key lifecycles (Premium), https://app.blowstack.com/lessons/key-management-policy-driven-key-lifecycles-dop-c02
