DigitalOceanVFS mounts one bucket: every object becomes a file and every / in a key
a folder. It is the S3 VFS pointed at DigitalOcean Spaces’s
endpoint, so commands behave as they do on S3. Set up credentials as in DigitalOcean Spaces setup.
Install
Configure
region also picks the endpoint, https://<region>.digitaloceanspaces.com;
endpoint replaces it.
A mount takes MountMode.READ, WRITE or EXEC.
Fields
Named profile in the shared AWS config and credentials files that supplies credentials when no access key pair is given.
Address the bucket in the URL path (
<endpoint>/<bucket>/<key>) instead of as a subdomain of the endpoint.Key prefix inside the bucket that the mount treats as its root; keys outside it are not visible. Leading slashes are dropped and a trailing
/ is added.Seconds a request may wait to connect, or between two reads of its answer, before it fails; a download that keeps flowing is never cut off.
Provider region every request is signed for. Most providers also build their endpoint URL from it unless
endpoint is set.Authentication
Credentials come from the first of:accessKeyIdandsecretAccessKey, withsessionTokenfor temporary credentials.profile, a profile in~/.aws/credentials.- The AWS SDK credential chain: environment variables, then the instance or container role.
Permission denied.
Layout
/spaces/reports/2026-q3.csv is the key reports/2026-q3.csv. Folders come
from the / in keys.
Behavior
- Key prefix:
keyPrefix: 'users/42/'mounts only that part of the bucket, so/spaces/notes.mdis the keyusers/42/notes.md.
Browser
The browserDigitalOceanVFS from @struktoai/mirage-browser keeps the keys off the
page: a server signs a URL for each S3 call with the DigitalOcean Spaces keys, and the
browser fetches it.
- Requests go to the host each signed URL names;
regionandendpointonly name the mount’s storage location. - The bucket’s CORS rules must allow the page’s origin, exactly as served.
- A browser mount cannot declare
write: conditional, and any HTTP 403 from a signed URL, an expired one included, answersPermission denied. keyPrefixset in the browser is no security boundary: enforce the prefix in the signing server and the key’s permissions.
Signing server
Signing server
An Express route that signs URLs:Sign only the operations the app needs: a viewer needs
GET, HEAD and LIST.Bucket CORS rules
Bucket CORS rules
Spaces takes the S3
PutBucketCors call, so the AWS CLI works against
its endpoint. The control panel sets the same rules under the Space’s
Settings > CORS Configurations.Browser fields
Browser fields
Function
(path, operation, options) that returns a signed URL for each S3 operation; your server signs it, so the browser holds no keys.Region of the bucket. Most providers derive the endpoint from it; requests go to the host each presigned URL names.
Endpoint URL that replaces the one the provider derives. Requests go to the host each presigned URL names; the mount uses it to name its storage location.
Key prefix the mount treats as its root. The browser can change it before a URL is signed, so enforce the prefix on the signing server.
Seconds a request may wait to connect, or between two reads of its answer, before it fails; a download that keeps flowing is never cut off.
Integration
DigitalOcean Spaces answers these commands through its own API, so fewer objects are read. See Integration.md5sum: the object’s ETag, when it is the MD5 (a single-part upload, unencrypted or under SSE-S3).find: one recursive listing.du: one recursive listing.ls -Randtree: one recursive listing.
VFS.md
The VFS.md an agent reads with DigitalOcean Spaces mounted at/<path>.
<mode> is the mount’s mode: read, write or exec. The commands shown are
those of a write mount.
- Rendered
- Raw
Virtual Filesystem
Supported Unix Commands for VFSUnix commands work on each path as on a local filesystem, as far as the path supports them:
Limitations of Unix Commands for VFSWhere a path differs from a local filesystem:
Run
man <cmd> or <cmd> --help for one command’s usage.