Support Post-Quantum Cryptography (PQC) in ACCP

[msteindorfer]

Context: AWS is progressively migrating to post-quantum cryptography [1] as part of its shared cloud security compliance model [2]. While AWS is explicit about supporting PQC in its foundational native libraries (i.e., aws-lc and s2n), it, to my knowledge, did not communicate a commitment or roadmap related to ACCP.

Question: Specifically for ACCP, I'd like to inquire if, or respectively when, ACCP will add support for exposing PQC algorithms that are already standardized and shipping as part of aws-lc, namely ML-KEM (FIPS 203 [3]) for key encapsulation, and ML-DSA (FIPS 204 [4]) for digital signatures.

Those two algorithms are already available in OpenJDK 24 and onwards (cf. JEP 496 [5] and JEP 497 [6]). Exposing the corresponding aws-lc implementations via ACCP would directory support ACCP's mission:

"The Amazon Corretto Crypto Provider (ACCP) is a collection of high-performance cryptographic implementations exposed via the standard JCA/JCE interfaces. This means that it can be used as a drop in replacement for many different Java applications. [...] As of 2.0.0, algorithms exposed by ACCP are primarily backed by AWS-LC's implementations."

Thank you in advance for clarifying your plans for supporting post-quantum cryptography in ACCP.

---

1. "AWS Post-Quantum Cryptography Migration Plan" (https://aws.amazon.com/blogs/security/aws-post-quantum-cryptography-migration-plan)
2. "AWS Cloud Security Shared Responsibility Model" (https://aws.amazon.com/compliance/shared-responsibility-model)
3. "FIPS 203: Module-Lattice-Based Key-Encapsulation Mechanism Standard" (https://csrc.nist.gov/pubs/fips/203/final)
4. "FIPS 204: Module-Lattice-Based Digital Signature Standard" (https://csrc.nist.gov/pubs/fips/204/final)
5. "JEP 496: Quantum-Resistant Module-Lattice-Based Key Encapsulation Mechanism" (https://openjdk.org/jeps/496)
6. "JEP 497: Quantum-Resistant Module-Lattice-Based Digital Signature Algorithm" (https://openjdk.org/jeps/497)

[brian-jarvis-aws]

Greetings, and thank you for reaching out. ML-DSA (both "pure" and "External Mu") was added in the ACCP 2.5.0 release. However I realize that we missed updating the README to add it to the list of supported signatures so thank you for bringing that to my attention.

We do intend to add support for ML-KEM as well, though I can't offer a timeline for when that will be delivered. Your interest in it is helpful for our internal prioritization, though.