Get your keys
- In the DigitalOcean control panel, go to Spaces Object Storage in the left sidebar.
- Open the Access Keys tab and click Create Access Key. You can give the key full access or limit it to specific buckets.
- Copy the Access Key and Secret. Note these are separate from DigitalOcean API tokens; a personal access token will not work for Spaces.
Connect
- Add a new connection and choose the DigitalOcean Spaces preset.
- Paste the keys and pick the region of your Spaces.
- Connect.
Regions
| Region | Endpoint |
|---|---|
| NYC3 | https://nyc3.digitaloceanspaces.com |
| SFO2 | https://sfo2.digitaloceanspaces.com |
| SFO3 | https://sfo3.digitaloceanspaces.com |
| AMS3 | https://ams3.digitaloceanspaces.com |
| LON1 | https://lon1.digitaloceanspaces.com |
| FRA1 | https://fra1.digitaloceanspaces.com |
| TOR1 | https://tor1.digitaloceanspaces.com |
| BLR1 | https://blr1.digitaloceanspaces.com |
| SGP1 | https://sgp1.digitaloceanspaces.com |
| SYD1 | https://syd1.digitaloceanspaces.com |
| ATL1 | https://atl1.digitaloceanspaces.com |
| RIC1 | https://ric1.digitaloceanspaces.com |
Good to know
- A full access key reaches every Space in the account, across regions, but each region needs its own connection because the endpoint differs. Keys limited to specific buckets only see those buckets.
- A Space’s CDN URL is separate from the S3 endpoint. The app talks to the origin endpoint; CDN caching does not interfere with uploads or listings.
- Spaces caps each bucket’s request rate before large buckets slow down; the app’s queued, resumable transfers behave well within those limits.