# Key Rotation

Key rotation is the controlled replacement of cryptographic key material while preserving required access to data protected by earlier keys.

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

> Key rotation limits how long a cryptographic key is used to protect new data and supports security policies, compliance requirements, and incident response. A safe rotation process directs new operations to fresh key material, retains older material when necessary for decryption or verification, and retires it only after its dependencies are resolved.

Practice exams covering Key Rotation: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DEA-C01 AWS Certified Data Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate), [DVA-C02 AWS Certified Developer - Associate](https://blowstack.com/practice-exams/aws-certified-developer-associate), [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), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 6 key aspects of Key Rotation

Effective rotation combines fresh key material, origin-aware lifecycle management, backward access, and verified retirement without confusing rotation with data migration.

1. **Defined cryptoperiods**: Set rotation intervals according to sensitivity, usage, algorithm constraints, and policy rather than assuming one interval fits every key. Support event-driven rotation when compromise or administrative changes warrant it.
2. **Logical keys and material versions**: A stable key identifier can refer to successive material versions, allowing applications to adopt fresh material without configuration changes. Creating a separate key resource instead requires migration of references and permissions.
3. **Material origin determines responsibilities**: Provider-generated material generally enables more service-managed lifecycle operations. Imported material places responsibility for external generation, backup, expiration management, and supported rotation workflows on the organization.
4. **Backward decryption and verification**: Retain earlier material for as long as protected data, signatures, or backups require it. Test recovery paths before disabling or deleting old versions.
5. **Rotation is not re-encryption**: Changing the active key material normally affects new operations, not all existing ciphertext. Rewrapping data keys or re-encrypting data requires a separate, explicitly planned process.
6. **Controlled retirement and evidence**: Track rotation events, active versions, failures, and dependencies. Retire old material only after validating retention requirements, application behavior, and disaster-recovery access.

## Cloud services for Key Rotation

Managed key services such as AWS KMS, Azure Key Vault, and Google Cloud KMS maintain key identities and versions, reducing application changes when supported rotation workflows are used. Their capabilities differ by key type and material origin, so imported-key workflows require explicit validation. AWS CloudHSM provides lower-level control but leaves more lifecycle orchestration to the organization. CloudTrail supplies audit evidence for AWS key-management activity. Across these services, storage systems and applications still determine when new keys are adopted and whether existing encrypted data must be migrated; enabling rotation alone does not complete that migration.

- **[AWS CloudHSM](https://blowstack.com/tools/cloud-services-hub/aws-cloudhsm)**: AWS CloudHSM lets organizations generate and manage keys in dedicated hardware security modules. Applications or management workflows must orchestrate replacement keys, consumer updates, and retention of earlier keys rather than relying on KMS-style transparent automatic rotation.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: CloudTrail records KMS management activity and rotation-related events for auditing and investigation. These records help engineers validate lifecycle changes and investigate unexpected key administration.

## Key Rotation exam questions

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

### Question 1 (SOA-C03)

**Question:**

A company encrypts application records by using a symmetric customer managed AWS KMS key with AWS-generated key material. Automatic rotation is configured for every 365 days, and the key was last rotated 30 days ago. After a security review, the company requires fresh key material for new encryption operations before the end of today. This is a precautionary measure; there is no evidence of compromise. The existing annual rotation schedule must remain unchanged, and previously encrypted records must remain decryptable. The application's configured key ARN cannot change.

Which action should a CloudOps engineer take?

**Correct answer:** Invoke RotateKeyOnDemand for the existing KMS key without changing its automatic rotation configuration.

**Explanation:** On-demand rotation generates new key material for an eligible symmetric KMS key without changing its ARN, key policy, or existing automatic rotation schedule. KMS retains earlier material to decrypt previously encrypted records.

### Question 2 (SAP-C03)

**Question:**

A healthcare company is deploying a new fleet of Amazon EC2 instances through an infrastructure-as-code pipeline. All new Amazon EBS volumes must use native EBS encryption. The security team must control the encryption key's policy and be able to disable the key independently of the application teams. Key material must rotate automatically every year through AWS KMS without changing the key ARN or running a custom rotation workflow.

The company's existing customer managed KMS key is an RSA_3072 key with an ENCRYPT_DECRYPT key usage. A legacy application uses this key for application-level encryption and must continue using it unchanged. The deployment team proposes using the same key for the new EBS volumes to simplify key administration.

Which solution should a solutions architect recommend?

**Correct answer:** Create a customer managed SYMMETRIC_DEFAULT KMS key with AWS-generated key material in the standard KMS key store. Enable automatic rotation with a 365-day period, assign key administration to the security team, and configure the deployment pipeline to use its ARN for EBS encryption. Retain the RSA key for the legacy application.

**Explanation:** Native EBS encryption requires a symmetric encryption KMS key. A customer managed SYMMETRIC_DEFAULT key with AWS-generated material in the standard KMS key store supports automatic annual rotation while preserving its ARN and retaining older material for decryption. The security team can control its policy and disable it without changing the legacy application's RSA key.

### Question 3 (DEA-C01)

**Question:**

A company stores seven years of financial records in Amazon S3 using SSE-KMS with a symmetric customer managed KMS key whose key material was generated by AWS KMS. The bucket's encryption configuration and ingestion applications reference the key's full ARN. A new policy requires fresh KMS key material for new encryption operations at least every 180 days. Existing records must remain decryptable without rewriting the objects, and existing key ARN references must remain unchanged. Which solution meets these requirements with the LEAST operational overhead?

**Correct answer:** Enable automatic rotation on the existing KMS key with a rotation period of 180 days. Keep the key enabled and retain the existing key ARN references.

**Explanation:** This key supports automatic rotation with a configurable 180-day period. Rotation changes the material used for new encryption operations while preserving the key ARN and permissions. AWS KMS retains earlier key material and automatically selects the appropriate material for decryption, so existing S3 objects do not need to be rewritten.

### Question 4 (SCS-C03)

**Question:**

A company encrypts small confidential records directly with the AWS KMS Encrypt API by using a single-Region symmetric encryption KMS key with imported key material. The company has imported fresh material and completed on-demand rotation within the same KMS key. New encryption requests now use the fresh material.

Company policy requires the superseded material to be deleted from AWS KMS and all external backups in 30 days. Records encrypted before rotation must remain decryptable for seven years. The company must not expose record plaintext outside AWS KMS during the transition.

Which approach meets these requirements?

**Correct answer:** Before deleting the superseded material, call ReEncrypt for each older ciphertext with the existing KMS key as both the source and destination. Persist and validate the returned ciphertext, and delete the superseded material only after all dependencies on it have been removed.

**Explanation:** Rotation does not re-encrypt existing ciphertext. ReEncrypt can decrypt with the older material and encrypt with the current material within AWS KMS, without returning plaintext to the application. Using the same KMS key as the destination uses its current material. Persisting the replacement ciphertext and resolving every dependency allows the superseded imported material to be deleted safely.

### Question 5 (DVA-C02)

**Question:**

An application encrypts records by using the ARN of a customer managed symmetric AWS KMS key with AWS-generated key material. Automatic key rotation is enabled. During a compliance review, the security team requires all future scheduled rotations to stop until the team explicitly approves resuming them. The application must continue encrypting new records and decrypting records encrypted before previous rotations, without changing its configured key ARN. Which solution meets these requirements with the least operational effort?

**Correct answer:** Call DisableKeyRotation for the existing KMS key. Leave the key enabled and continue using its ARN.

**Explanation:** Disabling automatic rotation stops future scheduled rotations without disabling cryptographic operations or changing the key ARN. KMS continues using the current key material for encryption and retains previous key material to decrypt existing ciphertext. Automatic rotation can be enabled again after approval.

### Question 6 (SAA-C03)

**Question:**

A company stores several million documents in an unversioned Amazon S3 bucket. Each document is smaller than 100 MB and uses SSE-KMS with a symmetric customer managed AWS KMS key. S3 Bucket Keys are disabled. The security team has completed an on-demand rotation of the KMS key material.

A new compliance requirement states that the encrypted data key for every existing document must be protected by the current KMS key material. The company can rewrite the objects but must preserve their object keys and contents. Which solution meets this requirement with the LEAST operational effort?

**Correct answer:** Use S3 Batch Operations to copy every document onto itself, explicitly specifying SSE-KMS with the existing KMS key ARN.

**Explanation:** Copying each object onto itself with an explicit SSE-KMS configuration rewrites its encryption while preserving its object key and contents. With S3 Bucket Keys disabled, S3 obtains a new data key protected by the KMS key's current material. S3 Batch Operations performs the copies at scale without custom per-object processing.

## Practice Key Rotation in a full exam

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

- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 6 questions
- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 5 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 4 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 2 questions
- [DVA-C02](https://blowstack.com/practice-exams/aws-certified-developer-associate): 2 questions
- [DEA-C01](https://blowstack.com/practice-exams/aws-certified-data-engineer-associate): 1 question
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 1 question

## What is Key Rotation

Key rotation replaces the cryptographic material used for new operations according to a defined schedule or security event. The interval during which a key is authorized for a particular use is its cryptoperiod. Engineers choose cryptoperiods based on data sensitivity, usage volume, algorithm requirements, regulatory obligations, and the consequences of compromise. Rotation is one lifecycle control; it does not replace access restrictions, secure key generation, monitoring, or incident response.

Cloud key management systems commonly separate a logical key resource from its underlying key material. Rotation can create a new material version while preserving the resource identifier, permissions, and application configuration. New encryption operations use the current version, while the service retains earlier versions for decrypting existing ciphertext. Alternatively, engineers can create a separate key resource and update application references. This approach requires explicit handling of permissions, dependencies, and rollback.

The distinction between provider-generated and imported material affects who performs the rotation and who is responsible for recovery. With provider-generated material, the key management service generates and protects the material within its managed security boundary. Eligible keys can use service-managed scheduled rotation. With imported material, an organization generates the material externally and imports it through a protected import process. The organization must manage external copies, provenance, backup, and any configured expiration. Importing material does not automatically give it the same rotation capabilities as a provider-generated key.

For AWS KMS, eligible symmetric encryption keys with AWS-generated material support automatic and on-demand rotation. Eligible symmetric encryption keys with imported material support on-demand rotation after new material has been imported; imported material does not support automatic rotation. Therefore, the blanket statement that imported KMS keys can never rotate is incorrect. Rotation support depends on the key's origin, type, and configuration. Where native rotation is unavailable, create a new KMS key and migrate consumers deliberately.

Rotation is different from reimporting an existing key. If imported material expires or is deleted, restoring access to ciphertext requires the matching original material, subject to the service's reimport requirements. Unrelated replacement material cannot decrypt ciphertext produced with the missing material. An expiration date is therefore an availability control with potentially destructive consequences, not a rotation schedule.

Envelope encryption makes another distinction important. An application encrypts data with a data key and protects that data key with a key-encryption key. Rotating the key-encryption key does not automatically rewrite existing ciphertext or replace every data key. For example, rotating a KMS key used by object storage changes the material used for subsequent applicable operations, but does not by itself re-encrypt every existing object. Rewrapping encrypted data keys or rewriting stored data is a separate migration, with service-specific support and costs.

A practical rollout identifies every consumer, verifies that new writes use the intended key version, and tests reads of older data and backups. Old material must remain available until retention and recovery requirements permit retirement. Moving an alias to a new key changes future lookups through that alias; it does not redirect ciphertext dependencies or clients using a fixed key identifier.

Rotation adds operational complexity, retained-version costs, and possible service disruption. After suspected compromise, simply rotating is insufficient: revoke unauthorized access, assess exposed data, and determine whether re-encryption or credential replacement is necessary. Previously copied ciphertext remains vulnerable if an attacker also obtained its corresponding key material.

## Learn Key Rotation in lessons

5 short lessons on Key Rotation in 5 certification courses.

- SOA-C03: Key Rotation: changing key material safely (Premium), https://app.blowstack.com/lessons/key-rotation-changing-key-material-safely-soa-c03
- SAP-C03: Key Rotation: automatic rotation of customer managed KMS keys (Premium), https://app.blowstack.com/lessons/key-rotation-automatic-rotation-of-customer-managed-kms-keys-sap-c03
- DEA-C01: Key Rotation: encryption and decryption across KMS key versions (Premium), https://app.blowstack.com/lessons/key-rotation-encryption-and-decryption-across-kms-key-versions-dea-c01
- SCS-C03: Key Rotation: AWS-generated and imported material (Premium), https://app.blowstack.com/lessons/key-rotation-aws-generated-and-imported-material-scs-c03
- SAA-C03: Key Rotation: rotating AWS KMS key material (Premium), https://app.blowstack.com/lessons/key-rotation-rotating-aws-kms-key-material-saa-c03
