<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws-Kms on CuraDevOps</title><link>https://curadevops.metacog.co.kr/tags/aws-kms/</link><description>Recent content in Aws-Kms on CuraDevOps</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 27 Oct 2026 16:07:53 +0000</lastBuildDate><atom:link href="https://curadevops.metacog.co.kr/tags/aws-kms/index.xml" rel="self" type="application/rss+xml"/><item><title>AWS KMS adds ML-KEM post-quantum key encapsulation (FIPS 203)</title><link>https://curadevops.metacog.co.kr/insights/2026-10-27-aws-key-management-service-now-supports-ml-kem-for-post-quan/</link><pubDate>Tue, 27 Oct 2026 16:07:53 +0000</pubDate><guid>https://curadevops.metacog.co.kr/insights/2026-10-27-aws-key-management-service-now-supports-ml-kem-for-post-quan/</guid><description>&lt;ul>
&lt;li>&lt;strong>Platform/SRE — Plan:&lt;/strong> AWS KMS now GA with all three ML-KEM key specs, backed by FIPS 140-3 HSMs — evaluate adopting ML-KEM for workloads handling long-lived sensitive data as part of a PQC migration plan this quarter; no forced deadline, but the NIST IR 8547 roadmap signals classical key-exchange schemes will be phased out.&lt;/li>
&lt;li>&lt;strong>CI/CD — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> AWS KMS adding ML-KEM signals cloud providers are operationalizing NIST&amp;rsquo;s PQC standards; useful context for shaping a post-quantum cryptography roadmap, but no licensing change, cost impact, or deadline requires a decision now.&lt;/li>
&lt;/ul></description></item></channel></rss>