DigitalOcean Spaces
Step-by-step guide to connect DigitalOcean Spaces to BucketMate for macOS with Spaces access keys, the right regional endpoint, and bucket settings.
BucketMate connects to DigitalOcean Spaces through the S3-compatible Spaces endpoint for your region.
Prerequisites
- DigitalOcean account
- Space
- Spaces access key
- Spaces secret key
- Space region
Endpoint and region
Use the endpoint for your Spaces region:
https://<region>.digitaloceanspaces.com
Examples:
| Region | Endpoint |
|---|---|
nyc3 | https://nyc3.digitaloceanspaces.com |
sfo3 | https://sfo3.digitaloceanspaces.com |
ams3 | https://ams3.digitaloceanspaces.com |
sgp1 | https://sgp1.digitaloceanspaces.com |
fra1 | https://fra1.digitaloceanspaces.com |
Connection steps
- Open the DigitalOcean dashboard.
- Go to API and create or copy Spaces access keys.
- Open BucketMate.
- Choose Add connection.
- Select DigitalOcean Spaces.
- Enter the endpoint for the Space region.
- Enter the access key and secret key.
- Select the matching region.
- Use Test Connection.
- Choose Connect.
Common issues and fixes
ACL support is limited
Only private and public-read ACLs are supported. Fix by using those ACLs only.
Cross-region copy is not supported
Cross-region and cross-cluster CopyObject or UploadPartCopy are not supported. Fix by keeping source and destination in the same region and cluster.
Management features require the API
Bucket policies, versioning, lifecycle rules, and access logging are not available in the Spaces control panel. BucketMate can turn on versioning and auto-delete old versions through the S3 API. See Bucket versioning. Use the Spaces API or an S3-compatible CLI for bucket policies and access logging.
Tag-based lifecycle rules are not supported
Tag-based lifecycle rules are not supported. Fix by using time-based rules only.
Bucket-level encryption is not supported
Bucket-level encryption is not supported. Fix by using SSE-C or client-side encryption.
Bucket list permission is restricted
If credentials can access only one Space, turn off Load all buckets and enter the Space name manually.
Public URLs do not work
Copied direct URLs work only when the object is public or available through a configured CDN/custom domain. For private files, create a presigned share link in BucketMate.
BucketMate tips
- Keep source and destination in the same region for copy and move workflows.
- Use presigned links for temporary access to private files.