Connect
Run the dispatcher withprovider set to digitalocean and these variables:
DIGITALOCEAN_TOKEN
Key and permissions
DIGITALOCEAN_TOKEN is a DigitalOcean personal access token, created in the control panel under API > Tokens (Generate New Token), optionally with custom scopes. MicroVMs (custom-scoped token): microvm:create (create), microvm:read (list/get), microvm:update (run commands, also pause/resume/console), microvm:delete (delete). microvm:access is only for the MicroVM HTTPS endpoint and is not needed. Harness Runtime: only agent_harness_session:create is named in the API reference (on one endpoint); the scopes for configs, sessions, exec and delete that CostGraph uses are not documented, so a full-access token may be required. Sources: docs.digitalocean.com: networking access, docs.digitalocean.com: limits, docs.digitalocean.com: api, docs.digitalocean.com: harness runtime, docs.digitalocean.com: limits.Limits
- MicroVMs are public preview, MKC1 region only, linux/amd64 images only. (source)
- MicroVM auto-pause cannot be disabled; max idle timeout 4 hours. Max 32 GiB memory and 400 GiB disk; sizes 1/2/8/16 vCPU. (source)
- MicroVM exec: a command has 60 s to finish; 32 concurrent and 60 commands per minute per team; output capped at 4 MiB. (source)
- Harness Runtime exec timeout_seconds is clamped server-side to max 240 (default 60). (source)
- Harness Runtime: idle suspend default 15 minutes; up to 100 concurrent sessions per team; monthly active compute cap 744 hours per session; sizes up to mars-16vcpu-32gb. (source)