Key Lifecycle States
You'll learn: How encryption keys move through distinct operational states and what each state means for your security and systems.
Why Keys Have States
Just like a physical key can be cut, used daily, temporarily disabled, or destroyed, cryptographic keys in a KMS follow a defined lifecycle. These states control what operations are allowed and provide guard rails against accidental data loss or unauthorized access.
The Five Core States
Pending
Keys awaiting activation, often during initial creation or import. You cannot encrypt or decrypt data yet—think of this as a key still being manufactured.
Enabled
The active, operational state. Keys can perform all cryptographic operations: encrypt, decrypt, sign, verify. This is where keys spend most of their productive life.
Disabled
Temporarily suspended. No cryptographic operations allowed, but the key material still exists. Use this for incident response, suspected compromise, or planned system maintenance. You can re-enable the key later without data loss.
Scheduled for Deletion
The "waiting period" before permanent destruction—typically 7-30 days depending on the provider. This grace period prevents catastrophic mistakes. During this time, you cannot use the key, but you can cancel the deletion if you realize you still need it.
Deleted (Destroyed)
The key material is permanently destroyed and unrecoverable. Any data encrypted with this key cannot be decrypted. There's no going back.
Operational Implications
State transitions matter immensely. Disabling a key blocks all decryption—your application will fail to read encrypted data. Scheduling deletion starts an irreversible countdown. Always verify which resources depend on a key before changing its state.
Key Takeaway: Encryption keys progress through controlled lifecycle states (pending → enabled → disabled → scheduled for deletion → deleted) that govern what operations are possible and provide safety mechanisms against accidental data loss.