Amazon QLDB (Quantum Ledger Database) is a fully managed ledger database that maintains a complete, cryptographically verifiable history of every data change — immutable, append-only, and independently verifiable using SHA-256 hash chaining. Despite the "Quantum" in its name, it has nothing to do with quantum computing; it's named for providing a complete and verifiable (quantum, as in "indivisible/complete") record of change history.

> Note: AWS announced QLDB will no longer be available to new customers as of July 2025, with existing customers supported per AWS's standard end-of-life timelines. This guide covers its architecture and concepts, which remain directly relevant to anyone operating existing QLDB workloads or evaluating ledger-database patterns on alternatives like Amazon Aurora PostgreSQL with cryptographic extensions.

Key Takeaways

  • QLDB maintains an immutable journal — every change is appended, never overwritten or deleted.
  • Data integrity is provable via SHA-256 hash chaining and a digest you can verify independently, without trusting AWS.
  • It uses PartiQL (SQL-compatible query language) over a document-oriented data model — not a blockchain network, no consensus mechanism, single-owner trust model.
  • Common use cases: financial transaction records, supply chain provenance, HR/compliance audit trails, insurance claims history.
  • AWS has deprecated QLDB for new customers (July 2025) — new projects should evaluate alternatives (Aurora PostgreSQL + cryptographic verification patterns, or Amazon Managed Blockchain for multi-party trust).

How QLDB's Journal Works

Unlike a conventional database where an UPDATE overwrites a row, QLDB never deletes history. Every write appends a new revision to the document's history while preserving all prior revisions in the journal.

-- PartiQL: insert a document into a QLDB table
INSERT INTO VehicleRegistration
VALUE {
  'VIN': '1HGCM82633A123456',
  'Owner': 'Jane Doe',
  'RegisteredDate': `2024-01-15T00:00:00Z`
}
-- Update appends a new revision; prior revision is retained in the journal
UPDATE VehicleRegistration
SET Owner = 'John Smith'
WHERE VIN = '1HGCM82633A123456'
-- Query full revision history for a document
SELECT * FROM history(VehicleRegistration)
AS h WHERE h.data.VIN = '1HGCM82633A123456'

This history query is QLDB's signature feature — you can reconstruct exactly who changed what and when, with cryptographic proof that the record hasn't been tampered with after the fact.

Verifying Data Integrity with Digests

QLDB periodically computes a digest — a cryptographic hash summarizing the entire journal state at a point in time. You can request a digest and independently verify that a specific document revision is part of that provably unaltered history.

# Request a digest for a ledger at the current tip
aws qldb get-digest --name vehicle-registry-ledger
{
  "Digest": "U0hBMjU2IGhhc2ggb2YgdGhlIGxlZGdlciB0aXA=",
  "DigestTipAddress": {
    "IonText": "{strandId:\"BQ5qB1Oy...\",sequenceNo:482}"
  }
}
# boto3: fetch a revision + its proof, then verify against the digest
import boto3

client = boto3.client("qldb-session")

response = client.get_revision(
    Name="vehicle-registry-ledger",
    BlockAddress={"IonText": '{strandId:"BQ5qB1Oy",sequenceNo:481}'},
    DocumentId="2eTR8Qnc5nAHlzb8WaVR2K",
    DigestTipAddress={"IonText": '{strandId:"BQ5qB1Oy",sequenceNo:482}'}
)
# response["Proof"] gives the hash chain to recompute and compare against the digest

Because verification is purely cryptographic math against a hash chain you can compute yourself, you don't need to trust AWS's word that the record is unaltered — you can prove it.

QLDB vs. Blockchain: What's the Actual Difference?

<svg viewBox="0 0 740 260" xmlns="http://www.w3.org/2000/svg" style="width:100%;max-width:740px;font-family:sans-serif;color:currentColor">
  <style>
    .box { fill: none; stroke: currentColor; stroke-width: 1.5; }
    .lbl { fill: currentColor; font-size: 12px; }
    .sub { fill: currentColor; font-size: 11px; opacity: 0.75; }
    .accent { fill: currentColor; opacity: 0.1; }
  </style>
  <rect x="30" y="30" width="320" height="180" class="box accent"/>
  <text x="45" y="55" class="lbl">QLDB (centralized ledger)</text>
  <text x="45" y="80" class="sub">Single trusted owner (you/AWS)</text>
  <text x="45" y="100" class="sub">No consensus mechanism needed</text>
  <text x="45" y="120" class="sub">SHA-256 hash chain journal</text>
  <text x="45" y="140" class="sub">SQL-like queries (PartiQL)</text>
  <text x="45" y="160" class="sub">Fast, low-latency writes</text>

  <rect x="390" y="30" width="320" height="180" class="box"/>
  <text x="405" y="55" class="lbl">Blockchain (distributed ledger)</text>
  <text x="405" y="80" class="sub">Multiple independent parties</text>
  <text x="405" y="100" class="sub">Consensus protocol required</text>
  <text x="405" y="120" class="sub">Block-based chain</text>
  <text x="405" y="140" class="sub">Smart contract execution</text>
  <text x="405" y="160" class="sub">Higher latency, multi-party trust</text>
</svg>

QLDB solves "prove this record wasn't tampered with" for a single trusted operator. If you need trust across multiple independent organizations with no central authority, that's what Amazon Managed Blockchain (Hyperledger Fabric/Ethereum) is for — a fundamentally different trust model, not just a feature difference.

Common Use Cases

  1. Financial transaction ledgers — banks and fintechs needing provable transaction history for audits.
  2. Supply chain provenance — tracking custody and state changes of goods through a chain, verifiable end-to-end.
  3. Insurance claims audit trail — complete immutable record of claim status changes for regulatory compliance.
  4. HR/compliance records — employment history changes that must be provably unaltered for legal defensibility.

FAQ

What does "Quantum" mean in Amazon QLDB? It refers to providing a complete, immutable, verifiable record of data history — not quantum computing or quantum cryptography. The name predates and is unrelated to post-quantum cryptography.

Is Amazon QLDB a blockchain? No. QLDB is a centralized, single-owner ledger database using cryptographic hash chaining for tamper-evidence. Blockchain is a distributed, multi-party system requiring consensus among independent participants. QLDB solves a narrower, simpler problem.

Is QLDB still available on AWS? AWS stopped onboarding new QLDB customers as of July 2025. Existing customers continue to be supported under AWS's standard timelines, but new projects should evaluate alternatives.

What should I use instead of QLDB for new projects? For single-owner tamper-evidence, Aurora PostgreSQL combined with cryptographic verification patterns (signed audit logs, hash-chained triggers) is a common path. For genuine multi-party trust without a central authority, Amazon Managed Blockchain is the better fit.

Need Help Migrating Off or Architecting Around QLDB?

With QLDB closed to new customers, many teams need a migration plan for existing ledger workloads or a ledger-pattern design on a supported database. F9 Infotech's AWS data architecture team can help you evaluate Aurora-based ledger patterns or Managed Blockchain and plan a safe migration. Talk to our AWS data architects about your ledger database requirements.