Check against your doze

doze AWS

OfficialSigned

The whole local AWS as ONE service — with its web console.

doze/aws

$ doze add aws

Newest: 0.2.0 · [date]
Needs: doze 0.2.0 or newer
Runs: runs itself
Platforms: macOS arm64 · Linux arm64 · Linux x86_64
Licence: Apache-2.0
Source: on GitHub

The doze add aws in the header is doze 0.2. On , write the block by hand (below).

The newest release, 0.2.0, needs doze 0.2.0. 0.1.1 runs on your .

Both run runs itself. 0.2.0 is the newest; 0.1.1 is the newest your doze can run. Pick a path below. Neither touches your data.

0.2.0 carries doze: "0.2.0" in its signed index entry; every release before it sets no minimum.

Update doze

Recommended

1Update

doze is the CLI: update it with Homebrew

$ brew upgrade doze

Update doze first, then move the pin: can't check a release's minimum, so its doze modules upgrade would take 0.2.0 anyway. Want the Mac app too? brew install --cask doze-dev/tap/doze; it updates itself from Settings › About.

2Update doze.hcl

doze 0.2 names every line to change. Each block gains module; idle_timeout becomes sleep, and the default sleep is 2 minutes (was 5).

doze.hcl

- aws "aws" {}
+ module aws "aws" {}

What you get

aws 0.2.0. What changed in 0.2.0
doze add, doze migrate, and the desktop app.
From then on, doze picks a release your doze can run, by itself.
Every example on the overview works as written.

then, in your project

$ doze modules upgrade aws
  moves doze/aws 0.1.1 → 0.2.0 in doze.lock; commit it

Stay on

Use aws 0.1.1

From doze 0.2 this happens on its own: doze skips releases that need a newer doze and pins the newest one that runs. doze came before releases carried a minimum, so it would fetch 0.2.0. Hold aws at 0.1.1 yourself, in 's own syntax:

If you don't: doze fetches 0.2.0 anyway

[what happens then: to test]

1Hold the release in doze.hcl

doze.hcl, as doze reads it

modules {
  module "aws" { version = "0.1.1" }
}

aws "aws" {}

2doze writes this to doze.lock

doze.lock

modules:
    doze/aws:
        version: 0.1.1
        protocol: 1
        hashes:
            aarch64-apple-darwin: sha256:10edd7…b9e3
            aarch64-unknown-linux-gnu: sha256:9a986d…f1b7
            x86_64-unknown-linux-gnu: sha256:dd0fd2…d02d

pinned doze/aws 0.1.1 in doze.lock — commit the lockfile
so your team and CI get this exact build

When you do update: delete the modules block. doze 0.2 refuses it ("the modules block is gone") and pins releases itself.

What doze 0.2 and later print

From 0.2 on, doze checks each release's minimum. When the next minimum arrives, say a future release that needs doze 0.3.0 while you are on 0.2.0, it says so in one of two ways, word for word:

Nothing in the registry runs on this doze

$ doze up
error: aws needs doze 0.3.0 or newer; this doze is 0.2.0. Update doze (in the app: Settings › About), then run the command again

Why: doze looked for a aws release that fits and runs on your doze, and none does. It names the oldest doze that would work.
Fix: Update doze: brew upgrade doze, or Settings › About in the app. Run the same command again; nothing else to undo.

doze.lock was written by a newer doze

$ doze up
error: module doze/aws [0.x.y] (pinned in doze.lock) needs doze 0.3.0 or newer; this doze is 0.2.0. Update doze (in the app: Settings › About); the lock was written by a newer doze

Why: A teammate on a newer doze committed doze.lock with a release that needs it. The pin is the team's agreement, so doze will not quietly run something older.
Fix: Update doze to match your team. Don't edit the pin down: the next commit would move everyone else back too.

Every release against doze

All versions and release notes

Release	Released	Needs doze	Engines	On your
0.2.0newest	[date]	0.2.0	runs itself	Needs newer doze
0.1.1	18 Jul 2026	any	runs itself	Runs · hold it yourself on
0.1.0	18 Jul 2026	any	runs itself	Runs

"any": no minimum set, runs on doze 0.1.0 and up. Checking against because you chose it above. Stop checking

Start

A few lines in doze.hcl give you doze AWS. Nothing starts until something connects.

1 · In doze.hcl

doze.hcl

module aws "aws" {}

It listens on port 4566. doze env prints its address for tools outside doze.hcl.

A fuller setup

Paste it over the block above and keep what you need.

The doze AWS example, complete

The example the module ships in its own description (meta.yaml), in doze 0.2's module syntax.

doze.hcl

module aws "local" {
  port = 4566

  bucket "uploads" { versioning = true }
  queue  "emails"  { dlq = "auto"  max_receives = 5 }
  queue  "orders"  { fifo = true  content_dedup = true }

  topic "signups" {
    subscribe { queue = "emails"  raw = true }
  }

  table "sessions" {
    key = "session_id:S"
    ttl = "expires_at"
  }

  function "resize" {
    code    = "./functions/resize"   # dir with a provided.al2 bootstrap
    timeout = 10
  }

  rule "order_placed" {
    pattern = "{\"source\":[\"shop.checkout\"]}"
    targets = ["lambda:resize", "queue:emails"]
  }

  key "app_key" {}
  secret "db_password" { value = "s3cr3t" }
  parameter "/app/feature/banner" { value = "hello" }

  state_machine "order_flow" {
    definition = <<-ASL
      {
        "StartAt": "Resize",
        "States": {
          "Resize": {
            "Type": "Task",
            "Resource": "arn:aws:lambda:us-east-1:000000000000:function:resize",
            "Retry": [{"ErrorEquals": ["States.TaskFailed"], "MaxAttempts": 2}],
            "Next": "Notify"
          },
          "Notify": {
            "Type": "Task",
            "Resource": "arn:aws:states:::sqs:sendMessage",
            "Parameters": {"QueueUrl": "http://localhost:4566/000000000000/emails", "MessageBody.$": "$"},
            "End": true
          }
        }
      }
    ASL
  }
}

Quality

Each line says where it comes from, so you can check it.

Signed by doze-dev
ed25519 key Nu5y8mbj…GWjw=, compiled into doze, over every file and over the whole index. How signing works
signed index
Three platforms
macOS arm64, Linux x86_64, Linux arm64, each with its own sha256, in every release.
signed index
Every example on this page parsed by doze
By doze 0.2 with doze lint --offline, on every change to the registry.
registry CI · new
Source linked
doze-aws/module, Apache-2.0.
GitHub

Install

Module release

Needs doze 0.2.0[date] · runs itself

Run

$ doze add aws

It writes to doze.hcl [doze add will name it aws: to build]

module aws "aws" {
  port = 4566
}

And to doze.lock, on first use

modules:
    doze/aws:
        version: 0.2.0
        protocol: 1
        hashes:
            aarch64-apple-darwin: sha256:3cad…
            aarch64-unknown-linux-gnu: sha256:161e…
            x86_64-unknown-linux-gnu: sha256:2dbb…
        doze: 0.2.0

modules:
    doze/aws:
        version: 0.1.1
        protocol: 1
        hashes:
            aarch64-apple-darwin: sha256:10ed…
            aarch64-unknown-linux-gnu: sha256:9a98…
            x86_64-unknown-linux-gnu: sha256:dd0f…

modules:
    doze/aws:
        version: 0.1.0
        protocol: 1
        hashes:
            aarch64-apple-darwin: sha256:10ed…
            aarch64-unknown-linux-gnu: sha256:9a98…
            x86_64-unknown-linux-gnu: sha256:dd0f…

Pinned forever. Only doze modules upgrade moves it.

Compatibility

Versions

Release	Needs doze	Engines
0.2.0	0.2.0	—
0.1.1	any	—
0.1.0	any	—

"any": the release sets no minimum and runs on doze 0.1.0 and up. On doze 0.1.1?

No download counts

We don't count downloads: doze sends nothing home.