DigitalOcean

Overview
How to connect
Automated checks
Useful links

DSALTA connects to DigitalOcean using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules.

Read-only access. DSALTA never modifies, creates, or deletes resources in your DigitalOcean environment.

DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.

What DSALTA reads

DSALTA reads only the DigitalOcean account that authorized the connection — its name, email and a role always shown as Account Owner — as a single row on your Access page; and your DigitalOcean resources, which appear on your Inventory page.It calls these DigitalOcean endpoints:

/v2/account
/v2/droplets
/v2/databases
/v2/kubernetes/clusters

Permissions the checks require: readEvery request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your DigitalOcean environment.

Troubleshooting

Integration shows Disconnected

There is no Reconnect button. Open Integrations → Connected, click Manage on the DigitalOcean card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from DigitalOcean. This usually happens when API tokens expire.

Data is not syncing

Verify the connected account still holds the permissions this integration requires. Then open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Sync from integrations at the top right. That button refreshes every connected integration at once — there is no per-integration sync control.

DSALTA requests these scopes: read.

Open the integration

In the DSALTA sidebar, go to Integrations, find DigitalOcean, and click Connect.

Authorize access

A secure DigitalOcean window opens. Sign in if prompted and approve the request. DSALTA does not ask you to choose which resources to monitor — the connection covers everything the credential you authorize can read.

DigitalOcean authorization is per-team. Before you click Connect, switch to the team you want DSALTA to cover — the grant carries that team’s identity, and only that team’s droplets, databases and Kubernetes clusters will reach your Inventory page. To cover a second team you have to authorize again from that team.

Whoever signs in here becomes the only row on your Access page — DSALTA reads GET /v2/account and labels that row “Account Owner”. Sign in with an account whose email exists on your People page. If it matches no person, User access to Critical System should be valid reports that row as invalid with the reason “No matching person on the People page”; Offboarded users should not have active access flags only rows that do match a person who is terminated or offboarding, so it keeps passing.

The “DigitalOcean infrastructure should be properly configured” check is a droplet-backup check. It passes only when every droplet in the connected team has automatic backups enabled; a single droplet without backups turns it non-compliant.

DSALTA's Link DigitalOcean Account panel warning that a pop-up will open, with a Connect button

Once connected, DigitalOcean appears on the Connected tab and the checks below begin reporting after the first sync.

Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.

Check	Severity	What it verifies
DigitalOcean infrastructure should be properly configured	Medium	Checks that DigitalOcean infrastructure is properly configured and secure.
User access to Critical System should be valid	Info	Checks that everyone with DigitalOcean access is an active employee on the People page.
Offboarded users should not have active access	High	Checks that offboarded employees no longer have active DigitalOcean access.

Topic	Link
Setup	DigitalOcean OAuth reference
General	DigitalOcean website
DSALTA	Connection error messages

Getting Connected

Identity Providers

Cloud Infrastructure

Code Repositories

Security & Monitoring

Databases

SaaS & Productivity

What DSALTA reads

Troubleshooting

​What DSALTA reads

​Troubleshooting

What DSALTA reads

Troubleshooting