AWS KMS now supports post-quantum ML-KEM! Get ready for "harvest now, decrypt later"
Hi everyone, it's Shii-chan!
AWS What's New
aws.amazon.com
KMS now has post-quantum key encapsulation! It feels like the future, but it's worth preparing for today.
What was announced?
According to AWS What's New, AWS Key Management Service (KMS) now supports ML-KEM (Module-Lattice-Based Key-Encapsulation Mechanism). It's a post-quantum cryptography standard under NIST FIPS 203 that lets two parties establish a shared secret.
Why it matters
NIST's strategic roadmap (NIST IR 8547) positions ML-KEM to replace DH/ECDH key agreement and RSA-based key transport. ML-KEM addresses the "harvest now, decrypt later" threat, where an adversary records a key exchange today and recovers the shared secret once sufficiently powerful quantum computers exist.
What changes
- You can manage ML-KEM key pairs in KMS
- The private key is protected in FIPS 140-3 Level 3 validated HSMs
- You can export the public key so partners and clients can encapsulate locally
Dive Deep
All three key specs defined in FIPS 203 are supported:
- ML-KEM-512
- ML-KEM-768
- ML-KEM-1024
The APIs work like this:
- Encapsulate: uses the public key to produce a random 32-byte shared secret and its ciphertext
- Decapsulate: recovers the shared secret from the ciphertext with the private key
- GetPublicKey: exports the public key so external systems can encapsulate locally with libraries such as AWS-LC, OpenSSL or Bouncy Castle
It's available in all AWS Regions where KMS is available, except:
- Middle East (UAE)
- Middle East (Bahrain)
- China Regions
Wrap-up
- KMS supports ML-KEM-512 / 768 / 1024 from NIST FIPS 203
- Encapsulate / Decapsulate / GetPublicKey cover the key establishment flow
- Private keys stay in FIPS 140-3 Level 3 HSMs
- The two Middle East Regions and China Regions are excluded
If you protect long-lived data and are starting to think about post-quantum migration, this is for you!
