Amazon Braket earns FedRAMP Class C, but the quantum hardware stays outside the boundary
On 16 October 2026, Amazon Braket, AWS’s quantum service, entered the FedRAMP Class C scope in the US regions where it is available. Federal agencies can now explore quantum within an authorized boundary, but the computations themselves run on third-party quantum hardware providers, outside the certified boundary.
16 October 2026. AWS announced that Amazon Braket, its quantum computing service, entered the FedRAMP Class C scope in the US regions where it is available. 3. The number of regions concerned: US East (N. Virginia), US West (N. California), and US West (Oregon). Two layers. The ones the announcement carefully separates: the AWS-operated components, now inside the certified boundary, and the third-party quantum computers on which the computations actually run, which remain outside the boundary. Why it matters: quantum computing becomes officially consumable by US federal agencies, but the compliance boundary stops where the quantum machine begins.
What “FedRAMP Class C” changes for agencies
FedRAMP is the US government-wide program that standardizes the security assessment, authorization, and continuous monitoring of cloud products and services. For a federal agency, an authorization of this kind is a gate opener: it lets you use a service within an authorized boundary, without repeating a full security assessment for each organization. With this announcement, government agencies — and the organizations that serve them — can explore quantum computing through Braket within an already-validated framework.
The technical scope of the announcement is precise. The AWS-operated components enter the certified boundary: the API and SDK, job orchestration and management, compilation, and result storage in Amazon S3. In other words, everything that belongs to the software chain AWS controls is covered.
The boundary stops at orchestration
The point the announcement formulates carefully is this: quantum workloads execute on third-party quantum hardware providers, the Quantum Hardware Providers (QHPs), outside the certified boundary. In plain terms, FedRAMP compliance covers the queue, the compilation, and the storage, but not the quantum computer that runs the circuit.
That is a structural nuance, not a communication detail. AWS does not build the quantum processors it resells: it aggregates a catalog of providers — ion traps, neutral atoms, superconducting — and orchestrates access to their machines. The certification therefore covers the control plane, where identities, accounts, and results flow. The core of the computation, however, stays with a third party, and the compliance boundary stops at its door. For a public-sector security officer, the reading is immediate: what is “authorized” is the pipe and the control room, not the machine at the end of the pipe.
What AWS guarantees about data sent to QHPs
To compensate for this split, the announcement lists the guarantees applied to data leaving for the QHPs: removal of all personally identifiable information, encryption in transit and at rest, and adherence to AWS’s standard retention and deletion policies. The message is clear: even outside the boundary, the flow to third-party hardware stays framed by AWS privacy rules.
That is reassuring, but it does not move the boundary. A contractual and technical guarantee on data transfer is not equivalent to a FedRAMP authorization of the hardware itself. An agency handling sensitive data must therefore reason in two steps: what stays at AWS is covered; what leaves for computation at a QHP is outside the certified boundary, even if it is protected in transit. The distinction is not an artifact: it is the reality of an aggregation service that resells machines it does not own.
The practical question that follows is one of sovereignty: the QHPs in the Braket catalog are third-party companies, some operating outside the United States. For a federal agency, “outside the boundary” does not only mean “outside the FedRAMP authorization” — it also means the computation data may transit infrastructure beyond its jurisdiction. AWS’s guarantee of personal-data removal and encryption reduces the risk but does not remove it: an agency submitting a sensitive circuit must still decide whether the result it expects justifies sending it to a third party. That decision is not hypothetical — a submitted quantum circuit carries structural information about the problem being solved, and the answers that come back can be more revealing than the question.
Why it is a milestone more than a revolution
The announcement is not a technological novelty — Braket has existed since 2020 and remains a niche service, with three regions and access to experimental machines. Its weight is regulatory: it inscribes quantum into the federal compliance perimeter, opening the door to public budgets and research use cases that were until now held back by paperwork.
Read the signal over time too. Quantum is still a research and preparation market: agencies buy less computational results than exploration time on fast-evolving machines. A FedRAMP authorization on the orchestration layer is the prerequisite for those explorations to happen within a compliant framework — and a hint that AWS is betting on federal demand that will rise with hardware maturity. Rival hyperscalers, Microsoft and Google first, are watching: whoever locks in quantum compliance first secures a position in a market still at the promise stage.
The public-quantum race is accelerating
The announcement sits within a broader race. The three American hyperscalers each have a quantum offering: AWS with Braket, Microsoft with Azure Quantum, and Google with its Quantum AI service and home-built processors. On paper, Braket has long been the most “catalog” of the three — an aggregator of third-party machines rather than a manufacturer. This announcement gives it an argument the others have yet to produce: explicit federal compliance.
The calculus is strategic. The US public sector is a customer that pays in contract years and values compliance continuity almost as much as raw performance. By earning FedRAMP Class C on the orchestration layer, AWS secures a position as the “compliant entry point” into quantum, even though the machines themselves remain third-party. It is a classic AWS bet: win the control plane of a market before the hardware matures, then let the suppliers fight underneath.
Read the announcement at its proper size, though. Braket remains a preparation service: the agencies that adopt it do research, algorithm benchmarking, and training, not production computation. Useful quantum — the kind that cracks a real problem classical machines cannot handle — is not here, and no one promises it will be this decade. Federal compliance is therefore an infrastructure milestone, not proof of quantum maturity. It says: the pipe is ready, the machine will come later.
Verdict
If you are a US federal agency or a public-sector contractor, this announcement removes a real obstacle: you can now consume Braket within an authorized boundary for the AWS layer. If you expect end-to-end “certified” quantum, keep the distinction in mind: the quantum computers themselves remain outside the boundary, and your computation data leaves for third parties — protected, but outside the FedRAMP boundary. Treat Braket for what it is: a compliant quantum control plane, not a compliant quantum computer.
For everyone outside the US public sector, the announcement is still a useful signal. It shows where the quantum market’s commercial gravity sits: not in selling computation, but in selling access, governance, and compliance around computation that runs on someone else’s machines. The first cloud provider to make quantum “boring” — auditable, authorized, insurable — will capture the budgets that arrive before the hardware is ready.