DigitalOcean

Authentication

DigitalOcean uses a single personal access token. Generate one from the DigitalOcean dashboard with read and write scopes.

Field	Required	Description
api_token	Yes	Personal access token

Configuration

providers:
  digitalocean:
    api_token: "${DIGITALOCEAN_TOKEN}"
    region: nyc3
    image: ubuntu-24-04-x64
    size: s-2vcpu-4gb

defaults:
  provider: digitalocean

Regions

Common regions:

Slug	Location
nyc1, nyc3	New York
sfo3	San Francisco
ams3	Amsterdam
sgp1	Singapore
lon1	London
fra1	Frankfurt
blr1	Bangalore
tor1	Toronto
syd1	Sydney

Run managed providers regions digitalocean to list all available regions.

Sizes

Sizes follow the pattern s-{vcpu}vcpu-{ram}gb for shared CPU plans:

Slug	Specs
s-1vcpu-1gb	1 vCPU, 1 GB RAM, 25 GB disk
s-2vcpu-4gb	2 vCPU, 4 GB RAM, 80 GB disk
s-4vcpu-8gb	4 vCPU, 8 GB RAM, 160 GB disk

Run managed providers sizes digitalocean --region nyc3 to list all available sizes in a region.

Images

Use the image slug for the OS you want:

Slug	OS
ubuntu-22-04-x64	Ubuntu 22.04 LTS
ubuntu-24-04-x64	Ubuntu 24.04 LTS
debian-12-x64	Debian 12

Auto storage

DigitalOcean supports auto-provisioned storage via Spaces. When a service needs backup storage, managed automatically:

1. Creates a Spaces access key
2. Creates an S3-compatible bucket in the configured region
3. Stores credentials in state for service scripts to use

No additional configuration is needed.

Networking

DigitalOcean servers are created with VPC private networking enabled. Servers in the same region automatically get private IPs for inter-server communication, which managed uses for service-to-service traffic.