Connect a DigitalOcean account

PruneOps needs a read-only DigitalOcean API token to inventory Droplets, volumes and Load Balancers in your account. Spaces uses separate S3-compatible credentials.

How it works

Two independent credential sets, both read-only.

01
API token

A single bearer token, generated from the API section of the DigitalOcean control panel, covers Droplets, volumes and Load Balancers.

02
Spaces

A separate S3-compatible access key / secret key pair, generated per Spaces endpoint from the control panel, covers bucket inventory.

03
Read-only scope

Scope the token to read-only when generating it — nothing PruneOps does ever needs write access.

API token

Covers Droplets, volumes and Load Balancers.

  1. In the DigitalOcean Control Panel, go to API → Tokens and generate a new Personal Access Token. Scope it to read-only — nothing this app does ever needs write access.
  2. Go to Organization → Integrations → Cloud Accounts → Add Account, pick DigitalOcean, and paste the token.

Spaces credentials (optional)

S3-compatible, generated independently of the API token above.

  1. In the DigitalOcean Control Panel, go to API → Spaces Keys and generate a new key pair.
  2. Add them to the same cloud account under Spaces Access Key / Spaces Secret Key, along with the endpoint region (e.g. nyc3, ams3, sgp1).

First sync

Once the account is saved, inventory runs on the next hourly cycle — or trigger it immediately from the account's detail page. Discovered Droplets, volumes, Spaces and Load Balancers appear under Audit → DigitalOcean.