compute, cloud, machine, domain

Workloads use LazyCloud compute by default. Compute covers setup and host requirements.

lazycloud compute

uv run lazycloud compute status       # capacity, connection, and workload count
uv run lazycloud compute instances    # running instances
uv run lazycloud compute workloads    # each workload and the machine it is pinned to

lazycloud cloud

Connecting an AWS account needs the Business plan. The connection belongs to your account and backs every workspace you own.

uv run lazycloud cloud connect aws --account-id <id> [--role-arn <arn>]
uv run lazycloud cloud authorize           # reopen the pending stack in the AWS Console
uv run lazycloud cloud status [--watch] [--until <phase>] [--interval <s>] [--timeout <s>]
uv run lazycloud cloud validate            # recheck the current authorization
uv run lazycloud cloud reconnect           # start a replacement authorization
uv run lazycloud cloud cancel-reconnect
uv run lazycloud cloud retry               # retry the connection's pending action
uv run lazycloud cloud disconnect [--wait]
uv run lazycloud cloud forget [--yes]      # drop a connection whose disconnect cannot finish

cloud connect aws prints an AWS Console link and opens it in your browser. The link opens the connection stack ready to create. Once you’re signed in to that account, tick the IAM acknowledgement and choose Create stack. No AWS CLI or access keys are involved. LazyCloud checks the connection once the stack finishes, and cloud status --watch --until ready waits for that. cloud reconnect and cloud authorize print and open the same kind of link. cloud disconnect --wait ends in one of two ways. Either the account is removed, or the connection is in action_required and exits with status 1. The detail names what failed. Once it’s fixed, cloud retry picks the removal up again, and cloud forget gives up on it. forget removes the connection and lists each stack or instance LazyCloud could not delete, with a Console link to delete it yourself.

lazycloud machine

uv run lazycloud machine list
uv run lazycloud machine join --name <name> --workspaces <a,b> [options]   # run on the machine you are joining
uv run lazycloud machine update <name-or-id> --workspaces <a,b>
uv run lazycloud machine remove MACHINE_ID

A joined machine has an account-unique name and a list of workspaces whose workloads may run on it. A workload with machine="<name>" in its decorator runs there or fails. machine join options:

Option	What it does
`--name <name>`	Machine name workloads pin to. Lowercase letters, digits, and hyphens. Required.
`--workspaces <a,b>`	Workspace names whose workloads may run here, comma-separated or repeated. Required.
`--gpu <model>`	GPU model this machine contributes.
`--max-cpu`, `--max-memory`, `--max-gpus`	Capacity to advertise, for example `--max-cpu 4` (physical cores) or `--max-memory 32Gi`.
`--gpu-ids <ids>`	Comma-separated GPU device ids to expose, instead of `--max-gpus`.
`--background`, `--foreground`	Install the agent as a service, or run it in the terminal. Default is `--foreground`.
`--service-manager`, `--service-name`, `--state-dir`	Service installation details.

The host requirements list what the machine needs.

lazycloud domain

Custom domains need a Team or Business plan.

uv run lazycloud domain add HOSTNAME       # prints the DNS records to create
uv run lazycloud domain status HOSTNAME
uv run lazycloud domain list
uv run lazycloud domain remove HOSTNAME

See Custom domains.

To change your default workspace, run uv run lazycloud workspace use <name>. Commands with a --workspace option can override it for one call.

Getting started

Core concepts

CLI reference

Examples

Account

compute, cloud, machine, domain

lazycloud compute

lazycloud cloud

lazycloud machine

lazycloud domain