[Enhancement]: Post-Quantum Cryptography (PQC) Readiness Observations & Documentation Suggestions

Open
#7,718 2 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 2 days

@brmur is already working on this.

Since Jan 30, 2026.

Assessment

This issue has not been assessed yet.

Description

New example request
Background story

As organizations begin planning for NIST post-quantum cryptography (PQC) migration,
there is growing demand for practical guidance on how to design crypto-agile systems
using AWS services and SDKs.

While AWS provides strong cryptographic primitives, there is currently no example-level
guidance that helps developers understand how to prepare for hybrid (classical + PQC)
transitions, crypto inventory, and long-term data protection planning.

This example is important to help developers start planning early, before migration
becomes urgent and disruptive.

What does this example accomplish?

This request proposes adding documentation and example guidance for
Post-Quantum Cryptography (PQC) readiness in AWS services.

The example would help customers understand how to:
• Track cryptographic usage (crypto inventory)
• Design crypto-agile systems
• Prepare for hybrid classical + PQC transitions
• Align with NIST post-quantum standards
• Plan long-term data protection (store-now-decrypt-later risk)

This is NOT a vulnerability report.
It is a documentation and readiness feature request based on public AWS behavior and docs.

The goal is to help developers and security teams begin PQC planning early,
before migration becomes urgent.

Happy to help refine or contribute examples if useful.

Which AWS service(s)?

AWS Key Management Service (KMS), AWS CloudHSM, AWS Certificate Manager (ACM), AWS Secrets Manager, AWS IAM, AWS Nitro Enclaves

Which AWS SDKs or tools?
  • All languages
  • .NET
  • C++
  • Go (v2)
  • Java
  • Java (v2)
  • JavaScript
  • JavaScript (v3)
  • Kotlin
  • PHP
  • Python
  • Ruby
  • Rust
  • Swift
  • Not applicable
Are there existing code examples to leverage?

No response

Do you have any reference code?

Dominant language
Java
Stars
10.5k
Forks
5.8k
Avg merge
2d 21h
Merged PRs (30d)
30

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from awsdocs/aws-doc-sdk-examples

All issues in awsdocs/aws-doc-sdk-examples

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.