The technology enables secure data exchange by establishing a 32-byte shared secret, designed to protect against future decryption by quantum computers. NIST designed ML-KEM to replace older schemes like DH/ECDH and RSA-based key transport as part of its strategic cryptographic roadmap. However, the service is not yet available in the Middle East (UAE), Middle East (Bahrain), and China Regions.
ML-KEM Implementation Safeguards Against Future Quantum Attacks
AWS KMS now uses Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM) adhering to the NIST FIPS 203 standard, a proactive measure against future decryption of currently recorded data. This implementation directly addresses the “harvest now, decrypt later” threat, where adversaries store encrypted data anticipating the arrival of sufficiently powerful quantum computers capable of breaking existing encryption. The KMS Encapsulate API generates a 32-byte shared secret and its ciphertext using the public key, while the Decapsulate API recovers the secret with the corresponding private key.
AWS KMS safeguards the private key of each ML-KEM key pair within FIPS 140-3 Level 3 validated hardware security modules, providing a robust layer of protection. Customers can use the GetPublicKey API to export public keys for local encapsulation using libraries such as AWS-LC, OpenSSL, or Bouncy Castle, facilitating secure data exchange with external partners. According to the AWS announcement, NIST designed ML-KEM to replace classical key-establishment schemes, highlighting the importance of adopting post-quantum cryptography standards. The availability of ML-KEM-512, ML-KEM-768, and ML-KEM-1024 key specifications provides customers with options tailored to their specific security requirements.




See today’s quantum computing news on Quantum Zeitgeist for the latest breakthroughs in qubits, hardware, algorithms, and industry deals.
