BuildNot yet confirmed elsewhere1 publisher2 min readPublished
AWS publishes a reference pipeline for signing software artifacts with ML-DSA
AWS says teams can sign binaries, container images and SBOMs with ML-DSA today, using KMS, Private CA and IAM Roles Anywhere. CNSA 2.0 mandates exclusive quantum-resistant software signatures by 2030, and AWS dates the EU CRA's full effect to December 2027.
The Engineer · Build desk
AWS's example firmware, deployed in 2026 with a 15-year life, runs to 2041. CNSA 2.0 mandates exclusive use of quantum-resistant signatures for software and firmware by 2030. AWS's scenario asks what happens if a quantum computer becomes operational in 2035.
| Figure | Value | Note | Claim |
|---|---|---|---|
| End of 15-year life, 2026 firmware deployment | 2,041 year | 11 | |
| Firmware deployed | 2,026 year | 7 | |
| CNSA 2.0 exclusive use by | 2,030 year | 3 | |
| Scenario: quantum computer | 2,035 if operational | 8 |
What happened
- The post is Part 1 of two. Part 2 covers enforcing ML-DSA algorithm policy with SCPs and IAM and is aimed at security and governance teams.
- CNSA 2.0, published by the NSA, has since 2025 required national security systems to "support and prefer" quantum-resistant signatures for software and firmware.
- AWS says the building blocks are production-ready and generally available, so teams do not wait on a preview service to start.
- AWS also says that as of October 2026 its series is "the first end-to-end guide from any cloud provider for post-quantum signing across the software supply chain."
Why it matters
- contradiction AWS says buyers in the US federal and European markets face converging deadlines, yet it ties quantum-resistant signatures only to CNSA 2.0 and describes the CRA as a lifecycle integrity duty.
- decision Part 2 turns the algorithm choices made in Part 1 into org-wide preventive and detective controls, so the key and certificate choices in the pipeline become a governance decision.
- exposure Exposure sits with devices that cannot be re-signed in the field. In our view, artifacts a pipeline rebuilds and re-signs routinely carry less of it.
AWS builds the pipeline from three services. ML-DSA keys sit in KMS, the certificate hierarchy lives in Private CA, and Roles Anywhere carries the ML-DSA trust anchors [1]. The post's introduction does not cover pricing, signature size or the client tooling for images and SBOMs. We'd test the verifier side first. Signing in AWS pays off only if the tools that check binaries, images and SBOMs downstream accept ML-DSA certificates.
The clocks run unevenly. Counted from the post's October 2026 date, the 2030 exclusive-use date in CNSA 2.0 is roughly three to four years away, depending on where in 2030 it falls [12]. The CRA's December 2027 date is 14 months away [13]. Whatever the CRA asks of signing arrives first.
Firmware is AWS's strongest case. It describes ECDSA P-256 firmware deployed in 2026 to embedded devices that check the signature on every boot for a 15-year life and cannot be recalled for re-signing [7]. AWS frames a working quantum computer in 2035 as a conditional. If one arrives, an attacker could produce a valid-looking signature over tampered firmware, and every device would accept it on the next restart [8]. A 2026 deployment with a 15-year life runs to 2041, so six years of fleet life fall after 2035 [11].
Behind the scenario is a claim about threat shape. Most post-quantum discussion centers on harvest now, decrypt later, which threatens confidentiality [9]. AWS argues that signatures face a parallel threat to integrity, because they rely on the same asymmetric math a quantum computer would break [9]. The algorithm it builds on, ML-DSA, is standardized in NIST FIPS 204 [16].
What to watch
- Part 2's SCP and IAM controls, and whether they can block classical RSA and ECDSA signing keys across an organization.
- Whether downstream verifiers for container images and SBOMs accept ML-DSA certificate chains from AWS Private CA.
- Any CRA guidance that names signature algorithms, which would settle whether December 2027 is a post-quantum deadline.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence35
- Adoption
- Insufficient
- Hype gap+20
- Incentives60
- Confidence45
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
The AWS post combines ML-DSA keys in AWS KMS, ML-DSA certificate hierarchies in AWS Private Certificate Authority, and ML-DSA trust anchors in IAM Roles Anywhere into an end-to-end signing architecture for binaries, container images and software bills of materials (SBOMs).
ReportedSupportedSource: AWS Security Blog, Quantum-resistant signing on AWS, Part 1View cited source - [2]
Since 2025, CNSA 2.0, published by the US National Security Agency, has required US National Security Systems to "support and prefer" quantum-resistant signatures for software and firmware.
- [3]
CNSA 2.0 mandates exclusive use of quantum-resistant signatures for software and firmware by 2030.
- [4]
The EU Cyber Resilience Act takes full effect in December 2027.
- [5]
AWS describes the Cyber Resilience Act as requiring manufacturers to maintain verifiable software integrity throughout a product's lifecycle.
- [6]
AWS says it provides the building blocks for a quantum-resistant software supply chain today using production-ready, generally available services.
- [7]
In AWS's example, firmware signed with ECDSA P-256 and deployed to a fleet of embedded devices in 2026 is verified on every boot over a 15-year operational lifetime, and the devices cannot be recalled to re-sign after deployment.
- [8]
AWS says that if a cryptographically relevant quantum computer becomes operational in 2035, an attacker could produce a valid-looking signature over tampered firmware, and every device in the fleet would accept it as authentic on next restart.
- [9]
AWS says most post-quantum discussion focuses on harvest now, decrypt later, a threat to confidentiality, while digital signatures rely on the same asymmetric mathematical problems a quantum computer would break, so software supply chains face a parallel threat to integrity.
- [10]
AWS says organizations that ship software to US federal agencies or sell products in the European market face converging deadlines that demand action now.
- [11]
A 2026 deployment with a 15-year life runs to 2041, which leaves six years of device life after the 2035 scenario date.
- [12]
From the post's October 2026 date, CNSA 2.0's exclusive-use date of 2030 is roughly three to four years away, depending on the month in 2030.
- [13]
From the post's October 2026 date, the CRA's December 2027 full-effect date is 14 months away.
- [14]
The post is Part 1 of a two-part series; Part 2, Enforce your ML-DSA algorithm policy with SCPs and IAM, is for security and governance teams and turns the algorithm choices made in Part 1 into preventive and detective controls across an organization.
- [15]
AWS states that as of Oct 2026 its series is the first end-to-end guide from any cloud provider for post-quantum signing across the software supply chain.
ReportedContestedSource: AWS Security Blog (self-description, not independently verified)View cited source - [16]
ML-DSA is standardized in NIST FIPS 204.
Sources
1 independent publisher whose own reporting we read for this story.
- aws.amazon.comQuantum-resistant signing on AWS, Part 1: Build a software supply chain with ML-DSA
1 article · October 12, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
Entities
- Amazon Web ServicesFollow
- AWS KMSFollow
- AWS Private CAFollow
- AWS IAM Roles AnywhereFollow
- ML-DSAFollow
- CNSA 2.0Follow
- EU Cyber Resilience ActFollow
- National Security AgencyFollow