Run on
AWS
--backend cloud runs a sweep’s rollouts on a cluster in your own AWS account. Prove starts the
nodes, runs the sweep on them, and stops them when the sweep ends, however it ends: done, failed,
stopped early, or interrupted. Backends is Prove’s own
page on it, with what Prove starts and stops and what leaves your machine. Prove offers AWS;
Google Cloud and Azure are not yet supported. It is not available on Windows.
Install
Section titled “Install”The cloud extra brings the cluster software Prove uses, pinned to one version. The AWS CLI is
not a Python package:
install it
yourself, and Prove names it when it is missing.
pip install "poisson-prove[cloud]"Credentials
Section titled “Credentials”An AWS account, signed in on this machine through the AWS CLI. aws login signs you in; for an
SSO profile, aws sso login.
aws loginProve stores no cloud secret and asks for none. It reaches your account only through the AWS CLI’s own sign-in on this machine.
Config
Section titled “Config”poisson-prove where cloud --yes writes the [cloud] table into the spec: where the nodes start,
their machine type and how many, the ledger of what has been spent, the spend at which Prove stops
the sweep itself (stop_cost) and the estimate above which it refuses one (max_cost). This is
the table it writes, the same as Prove’s docs give. Each key is on
The sweep spec.
[cloud]provider = "aws"region = "us-east-2"machine_type = "m7i.2xlarge"nodes = 4max_vcpus = 32ledger = "cloud-ledger.jsonl"stop_cost = 2.0max_cost = 3.0est_seconds_per_episode = 1.0Before anything starts, Prove checks the extra, the AWS CLI, that this machine is signed in, the
region and machine type against its price table, the image’s Python against this machine’s, and
the account’s vCPU quota. Each refusal is one error: line with the command that fixes it.
On the keyless example’s spec, where cloud --yes writes the table and says whether this machine
is signed in, and sweep --dry-run prints the plan and stops. The Account line names the
account, masked. The Cluster line says what Prove starts and how soon the nodes stop themselves
if this machine stops first. The Traffic line says who carries your code, and the Cost line
gives the estimate, the ledger, the stop and the cap.
poisson-prove init --exampleOutput2 lines · exit 0
ok wrote prove.toml: a sweep of the keyless mock agent, 9 conditions x 194 replicates next: poisson-prove sweeppoisson-prove where cloud --yesOutput4 lines · exit 0
where your AWS account, us-east-2, 4 × m7i.2xlarge; signed in, ready signed in AWS 6030…4933 wrote [cloud] into prove.toml next: poisson-prove sweep --dry-runpoisson-prove sweep --dry-runOutput13 lines · exit 0
plan 1,746 rollouts of mock-agent: 9 cells x 194 replicates on your AWS account, ~$0.45 this run (4 × m7i.2xlarge at $0.4687/node-hour, Prove's AWS prices for us-east-2 of 2026-11-06, each node's disk priced at 52 GB) · ledger cloud-ledger.jsonl $0 so far · stop $2.00 · cap $3.00 target poisson_prove.examples.mock_agent:rollout (imports, takes cfg and seed) outcomes failures: timeout, violated Sweep: 2 axes · 9 cells · N=194 → 1,746 rollouts Backend: cloud · AWS · target: mock-agent · t_unit: tool_calls Account: AWS 6030…4933, signed in with the AWS CLI Cluster: Prove starts 4 × m7i.2xlarge in us-east-2 (8 vCPU each, 32 in all, ceiling 32) running python:3.11, and stops them when the sweep ends · 8 slots each · 32 at once · if this machine stops first, the nodes stop themselves within 5 min · this machine is kept from idle sleep while they run Bundle: poisson_prove 0.4.0 · 0.5 MB · sha256 9c4f61466c60… Worker view: job 0 matches this machine Traffic: your code, its inputs and its results go between this machine and the nodes through Burla's relay (the cluster software Prove uses); the store stays on this machine Cost: ~$0.45 this run (4 × m7i.2xlarge at $0.4687/node-hour, Prove's AWS prices for us-east-2 of 2026-11-06, each node's disk priced at 52 GB) · ledger cloud-ledger.jsonl $0 so far · stop $2.00 · cap $3.00 Chaos: none smallest rise one condition alone would be flagged for 0.199 at its worst base rate, 0.400 (Fisher, q 0.05 over 18 tests, 4 times in 5; you accept up to 0.200)Unlike Modal’s, this check reads your sign-in: Prove asks the AWS CLI who is signed in, a read-only call, and starts nothing. The first sweep is what starts nodes. Run Prove in your AWS account runs two, with their output stored.