Why Your Cloud Encryption Is Moving in 2026
AWS is transitioning Cloud-TLS to ML-KEM in 2026. This forces DACH teams using the harvest-now, decrypt-later approach to plan for crypto inventory and…
The quantum computer capable of cracking today’s encryption doesn’t exist yet. Yet AWS began overhauling its entire transport encryption in 2026. The reason sounds paradoxical: attackers are already harvesting encrypted data today to decrypt it years later with a quantum computer. Those who wait until the machine arrives have already lost the race.
Key Takeaways
- AWS shifts transport encryption to ML-KEM. KMS, Certificate Manager, and Secrets Manager will run in hybrid mode under NIST FIPS 203 in 2026; legacy experimental Kyber support is being dropped.
- “Harvest now, decrypt later” is the real driver. Data intercepted today that must remain confidential for years is already at risk – not just when the quantum computer arrives.
- Inventory before panic. Managed cloud TLS often gets the upgrade for free; custom clients, VPNs, and long-lived signatures remain a team effort.
Related:Manual TLS certificates? That ends in 2026 / BSI C3A: Cloud sovereignty becomes verifiable
What AWS is phasing out now
AWS Key Management Service, Certificate Manager, and Secrets Manager have supported ML-KEM for TLS key agreement since 2026. ML-KEM is the new NIST standard FIPS 203, derived from the CRYSTALS-Kyber algorithm. It operates in hybrid mode, combining classical cryptography with quantum-resistant methods to ensure connections stay secure even if one layer falters.
Key for planning: the previous experimental Kyber support is being removed across all AWS endpoints in 2026 and replaced with the standardized ML-KEM. Anyone who built custom clients against the old Kyber variants must adapt. This is a mandatory migration to the final standard.
Harvest now, decrypt later
The real urgency lies in a simple attack pattern. An attacker intercepts encrypted data traffic today and stores it – without being able to read it. Once a sufficiently powerful quantum computer becomes available, they decrypt the archive retroactively. Anything transmitted today that must remain confidential in five or ten years is already at risk.
This affects patient records, contracts, design data, and long-term trade secrets. The critical factor is your data’s protection lifespan. If it extends beyond the timeline to a cryptographically relevant quantum computer, you need to act now.
An Overview of the Three NIST Standards
Since 2024, the final standards have been published. AWS is implementing them step by step. FIPS 203 defines ML-KEM for key agreement. FIPS 204 establishes ML-DSA for digital signatures, while FIPS 205 introduces SLH-DSA as a hash-based signature alternative. For most cloud connections, ML-KEM is initially the most relevant, as key exchange represents the weakest link against quantum attacks.
Germany’s Federal Office for Information Security (BSI) recommends adopting quantum-resistant methods in hybrid mode while keeping classical cryptography running in parallel. AWS is taking precisely this approach. The hybrid model is the conservative, auditable option – and the right one for regulated industries.
# Inventory: Find TLS and crypto libraries in the cluster
kubectl get pods -A -o json | jq -r '.items[].spec.containers[].image' | sort -u
# Search for clients with experimental Kyber code
rg -n "kyber|ML-KEM|X25519Kyber" --type-add 'code:*.{go,rs,py,java,ts}' -t codeWhat Your Team Should Do Now
The first step is an inventory – before any technical project kicks off. Where is encryption used in your environment, which algorithms are deployed, and for which data classes? Without this cryptography inventory, you won’t know what needs migrating. Many companies uncover legacy libraries and hardcoded algorithms that had slipped off everyone’s radar.
The second step is crypto agility. Your systems should be able to swap encryption methods without rebuilding the application. Those relying on managed cloud services like AWS KMS will get the shift to ML-KEM largely for free. If you’re running your own cryptography, the migration burden falls on you – and you should start now.
No Need for Panic, But Time to Act
The good news: For most cloud communications, the transition happens behind the scenes as soon as the provider enables ML-KEM. The bad news: Your legacy systems, VPN tunnels, and long-term signatures remain your responsibility. A realistic 2026 plan includes inventory, prioritization by protection duration, and a shift to crypto-agile building blocks.
Post-quantum cryptography isn’t a weekend project. It’s a multi-year overhaul. The best time to start was yesterday – the second-best is today.
Frequently Asked Questions
What is post-quantum cryptography?
Post-quantum cryptography includes encryption methods that can withstand attacks from quantum computers. Traditional algorithms like RSA can be broken by a powerful quantum computer, but the new standards – such as ML-KEM (FIPS 203) – cannot. They rely on mathematical problems for which even quantum machines have no efficient solution.
What does “harvest now, decrypt later” mean?
Attackers intercept and store encrypted data today to decrypt it later using a quantum computer. That’s why data requiring long-term confidentiality is already at risk – even though quantum computers don’t yet exist.
Do I need to do anything as an AWS customer?
AWS handles the transition to ML-KEM for TLS connections to KMS, ACM, and Secrets Manager. However, your own applications, VPN tunnels, and long-term signatures remain your responsibility. A cryptography inventory will reveal where action is needed.
When will a quantum computer break encryption?
No one can predict an exact date. Estimates range from a decade to much longer. What matters is comparing the expected breakthrough timeline with how long your data needs to stay secure. If confidentiality must outlast that window, migration is overdue.
What is crypto agility?
Crypto agility means a system can switch encryption methods without being rebuilt. It’s the foundation of any post-quantum migration, as standards and recommendations will continue to evolve. Building with crypto agility today saves you from another painful overhaul down the road.
Editor’s Picks
cloudmagazinManual TLS certificates? That ends in 2026cloudmagazinGerman hyperscalers: Who really deliverscloudmagazinQuantum computing: IonQ Forte traps DACH IT in a cost spiralMore from the MBF Media Network
MyBusinessFutureThe blind spot of digital leaders: Why banks fail despite heavy IT investments – due to data chaosDigital ChiefsData rights already apply to existing fleetsSecurityToday622 CVEs: Prioritize, don’t panic-patchImage source: AI-generated (July 2026)
