/// CONNECT A PROVIDER / DIGITALOCEAN SPACES
DigitalOcean Spaces
DigitalOcean Spaces is S3-compatible, so you connect it as an access-key Fleet with a custom endpoint. The Spaces region is part of the endpoint URL, so there is no separate region field to worry about getting wrong.
Don't have a DigitalOcean Spaces bucket yet? Create one first →
What you need
- A Spaces access key and secret, generated under API → Spaces Keys in the DigitalOcean control panel.
- The Space (bucket) name.
- The regional endpoint:
https://<REGION>.digitaloceanspaces.com— the region is in the endpoint, for examplehttps://nyc3.digitaloceanspaces.com.
Connect the Fleet
From the Fleet page, click Create Fleet and pick Access Keys. Then:
- Enter a display name and the Space name.
- Paste the Spaces access key and secret.
- Set the endpoint to
https://<REGION>.digitaloceanspaces.comusing your Space's region, such asnyc3orfra1. - Click Connect Fleet.
Use a full-access key
Generate a full-access Spaces key for storafleet. DigitalOcean's limited-access (scoped) keys cannot manage bucket policies, so features that depend on reading or writing the bucket policy will fail if you connect with a scoped key.
Free per-bucket CDN
Every Space comes with a free CDN you can enable per bucket. It supports a custom domain with managed TLS and a cache purge for invalidating content. See the CDN guide for how to wire it up with a storafleet Fleet.
Because the region lives in the endpoint, make sure the region in the URL matches the region your Space was created in.