Documented steps

Create a Spaces access key pair (access key + secret) in the DigitalOcean control panel under Spaces access keys. These are separate credentials from DigitalOcean API tokens — per current docs, Spaces keys can only be created/managed in the control panel, not via the public API or CLI.
Spaces speaks the S3 protocol at regional endpoints: https://<region>.digitaloceanspaces.com (bucket-style: https://<bucket>.<region>.digitaloceanspaces.com). Example region: nyc3. Check the Spaces availability page for current regions.
Configure any S3 client with the Spaces endpoint and keys, e.g. aws CLI: `aws s3 cp file.txt s3://my-bucket/file.txt --endpoint-url https://nyc3.digitaloceanspaces.com --acl public-read` with AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY set to the Spaces keys.
Objects default to private; set ACL public-read (x-amz-acl header or --acl flag) to serve an object publicly at https://<bucket>.<region>.digitaloceanspaces.com/<key>.
For CDN delivery, enable the Spaces CDN on the bucket; public objects are then served from https://<bucket>.<region>.cdn.digitaloceanspaces.com/<key>.
Docs: https://docs.digitalocean.com/products/spaces/ and S3-compatibility notes: https://docs.digitalocean.com/products/spaces/reference/s3-compatibility/

Known gotchas

A DigitalOcean API token does NOT work for S3 operations — only Spaces access keys do, signed with AWS Signature v4.
Bucket (Space) names are globally unique across DigitalOcean; name collisions fail creation.
Per-bucket scoped access keys are incompatible with S3-compatible bucket policies — use broad keys if you rely on bucket policies.
The secret key is shown once at creation — store it immediately.
Not every S3 feature is supported; check the S3-compatibility reference before relying on advanced operations (e.g. some multipart/copy variants).

aws-s3 · 4 steps · unrated

Create a DigitalOcean Droplet via API with SSH keys attached, poll until active, and retrieve its public IPv4

digitalocean.com · 6 steps · unrated

Create a DigitalOcean Container Registry via API, authenticate docker, push an image, and reclaim space

digitalocean.com · 5 steps · unrated

Give your agent this knowledge — and 15,600+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Upload files to DigitalOcean Spaces with the S3-compatible API (aws CLI/SDK) and serve them publicly

Documented steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,600+ more routes

Need this verified for your stack — or a route we don't have yet?