Cloud Cryptography
Cloud KMS and PQC: AWS, Azure, and GCP Quantum-Safe Roadmaps Compared
Compare AWS KMS, Azure Key Vault, and GCP Cloud KMS PQC roadmaps. Learn which providers support ML-KEM, ML-DSA, and hybrid key exchange — and what it means for your cloud crypto posture.
Cloud KMS and PQC: AWS, Azure, and GCP Quantum-Safe Roadmaps Compared
If your organization uses AWS KMS, Azure Key Vault, or Google Cloud KMS, your cryptographic posture includes cloud-managed keys you do not directly control. Each provider has a different PQC roadmap. Understanding where they stand determines when your cloud workloads can become quantum-safe. For related context, see crypto agility planning.
This article compares the PQC roadmaps of the three major cloud providers, explains what hybrid key exchange means for cloud services, and identifies what you should do now regardless of your provider's timeline.
Why Cloud KMS Matters for PQC
Cloud Key Management Services generate, store, and manage the cryptographic keys that protect your cloud data at rest and in transit. When your application calls aws kms encrypt or az keyvault key encrypt, the algorithm and key used are determined by the cloud provider's service configuration — not by your application code.
For most organizations, migrating cloud KMS keys to post-quantum algorithms is the single biggest cryptographic dependency. You cannot migrate what you do not directly control. You are on the provider's timeline. For related context, see healthcare PQC readiness planning.
AWS KMS PQC Roadmap
Current state: AWS KMS supports RSA, ECC (P-256, P-384, P-521), and AES-GCM for symmetric encryption. AWS KMS does not yet support ML-KEM or ML-DSA.
Published roadmap: AWS has announced PQC support as part of its cryptographic modernization program. Key developments:
- AWS LibCrypto (the cryptographic library underlying KMS) added ML-KEM support in 2024
- AWS Certificate Manager (ACM) is testing hybrid certificate issuance
- AWS has committed to supporting CNSA 2.0 algorithms for government workloads
What to expect: AWS typically rolls out cryptographic features to US East first, then globally. ML-KEM support in KMS is expected in the 2025-2026 timeframe, with ML-DSA following. Hybrid key exchange in AWS services (ALB, CloudFront, API Gateway) is expected in the same window.
What you can do now: Inventory all KMS keys. Document which keys protect regulated data. Test with AWS LibCrypto's ML-KEM implementation in non-production. When KMS adds PQC support, migrate high-priority keys first.
Azure Key Vault PQC Roadmap
Current state: Azure Key Vault supports RSA and ECC keys. Managed HSM supports FIPS 140-2 Level 3. No PQC algorithm support yet.
Published roadmap: Microsoft has been more explicit about PQC timelines:
- SymCrypt (Microsoft's cryptographic library) added ML-KEM and ML-DSA in 2024
- Azure has committed to CNSA 2.0 algorithm support
- Azure has the most detailed public documentation on PQC integration with existing services
What to expect: Azure's PQC rollout is expected to align with its government cloud requirements, which are driven by CNSA 2.0 timelines. ML-KEM support in Key Vault is expected in the 2026-2027 window.
What you can do now: Inventory Azure Key Vault and Managed HSM keys. Enable logging for key usage to understand which services depend on which keys. Monitor Azure's PQC announcements through the Azure updates feed.
Google Cloud KMS PQC Roadmap
Current state: GCP Cloud KMS supports RSA, ECC, and AES-GCM. Google has been the most active in PQC research and deployment among the three providers.
Published roadmap:
- Google has been running internal PQC experiments since 2016
- Chrome has experimental ML-KEM support for TLS
- Google's internal ALTS (Application Layer Transport Security) protocol has been upgraded with PQC
- GCP has committed to CNSA 2.0 compliance for government workloads
What to expect: Google is likely to be first to market with production PQC key support in Cloud KMS, given its advanced internal deployment. ML-KEM support in Cloud KMS is expected in the 2025-2026 window.
What you can do now: Inventory GCP Cloud KMS keys. Enable key rotation if not already configured. Google's KMS key rotation architecture makes algorithm migration simpler than providers that issue static key material.
Comparison Table
| Capability | AWS KMS | Azure Key Vault | GCP Cloud KMS | |-----------|---------|-----------------|---------------| | RSA/ECC support | Yes | Yes | Yes | | ML-KEM (FIPS 203) | Testing (LibCrypto) | Testing (SymCrypt) | Internal deployment | | ML-DSA (FIPS 204) | Not yet | Testing (SymCrypt) | Internal deployment | | CNSA 2.0 commitment | Yes | Yes | Yes | | Hybrid key exchange | In development | In development | Advanced | | Est. production PQC | 2025-2026 | 2026-2027 | 2025-2026 | | PQC documentation quality | Moderate | Excellent | Good |
What You Should Do Regardless of Provider Timelines
The cloud providers are moving. Your job is to be ready when they arrive:
- Inventory every cloud KMS key. Know which keys exist, what they protect, and their rotation status.
- Classify by data sensitivity. Which keys protect regulated data? Those migrate first.
- Monitor provider announcements. Subscribe to AWS, Azure, and GCP security bulletins.
- Plan for external posture assessment. Cloud services that terminate TLS (ALB, CloudFront, Front Door, Cloud CDN) have certificates you can assess externally with CipherReady today. For related context, see PQC readiness roadmap for security teams.
FAQ
Q: Can I use CipherReady to assess my cloud provider's TLS endpoints? A: Yes — for domains you own that point to cloud services (e.g., your application domain behind CloudFront). CipherReady assesses the TLS certificate presented at the public endpoint, regardless of which provider terminates the connection.
Q: Do I need to wait for my cloud provider before starting PQC readiness? A: No. External cryptographic posture assessment, certificate inventory, vendor questionnaire campaigns, and internal PKI planning can all begin now. Cloud KMS migration is one part of a broader PQC readiness program.
Q: Will cloud providers charge more for PQC key support? A: Possibly. PQC keys are larger and operations are more computationally intensive. Expect pricing changes when PQC key types become available. Budget accordingly.
Start Free Readiness Scan →