Connect Cyberduck in three steps.
Cyberduck and Mountain Duck ship a dosya.dev connection profile. Pick it from the list, paste your S3 keys, and your workspaces appear as buckets. No endpoint, no port, nothing to type.
Generate S3 credentials
Profile > API keys > S3 credentials Enable the profile
Preferences > Profiles > dosya.dev Open a connection
Open Connection > dosya.dev Generate S3 credentials
Cyberduck signs in with an access key and a secret, the same pair every S3 tool uses. They are attached to an API key in Profile > API keys.
- 1
Open Profile > API keys in the dosya.dev app.
Create a key, or open one you already have.
- 2
Choose S3 credentials on that key.
You get an Access Key ID that starts with
DOSYAand a Secret Key. - 3
Copy the secret now.
It is shown once. If you lose it, generate a new pair; the old one stops working.
Use a key that can list and read. An upload-only key can save files but cannot show a listing, so Cyberduck's browser stays empty. The key carries your role in each workspace: if your role cannot use the S3 gateway there, that workspace refuses the connection.
Enable the dosya.dev profile
Cyberduck keeps the long tail of providers in a list you switch on. dosya.dev is in that list in every current version of Cyberduck and Mountain Duck, so there is nothing to install.
- 1
Open Preferences.
Cyberduck > Settings on macOS (⌘,), Edit > Preferences on Windows.
- 2
Go to the Profiles tab and search for dosya.
The list is fetched from Cyberduck's profile repository, so it is current without an app update.
- 3
Tick dosya.dev.
It now appears as a protocol in the connection and bookmark dialogs. Close Preferences.
Not in your list yet?
Download the same profile file and double-click it. Cyberduck registers it on the spot. It is the file merged into Cyberduck's own profile repository, byte for byte.
Open a connection
Pick dosya.dev as the protocol and paste the two keys. The server and port are already filled in by the profile and cannot be changed, which is the point.
# Open Connection (⌘N on macOS, Ctrl+N on Windows)
1. Protocol: dosya.dev
2. Server: api.dosya.dev (set by the profile, not editable)
3. Port: 443 (set by the profile, not editable)
4. Access Key ID: DOSYAXXXXXXXXXXXXXXXX
5. Secret Key: your_s3_secret_key
6. Path: ws_your_workspace_id (optional: open one workspace directly)
Press Connect. The browser lists one bucket per workspace, named ws_….
To come back without retyping anything, use Bookmark > New Bookmark with the same values;
Cyberduck keeps the secret in your keychain.
What to expect once connected
Cyberduck talks to the S3 gateway, so it sees exactly what any S3 client sees.
Workspaces are buckets
Every workspace your key can reach is listed at the top level as ws_<id>. You cannot create or delete buckets from Cyberduck; workspaces are made in the app.
Folders, upload, download
Drag files in or out, create folders, download whole trees. Intermediate folders are created on upload.
Large files just work
Uploads above 32 MB go as multipart in 32 MB parts. The profile sets that size to what the gateway accepts; there is nothing to tune.
Delete is soft
A delete in Cyberduck moves the file to the workspace's trash, the same as deleting in the app. Restore it from there.
Same files, same permissions
What you see and what you may change follow your role in each workspace. The web app, the desktop app and Cyberduck agree.
Synchronize and mount
Cyberduck's File > Synchronize works against a workspace folder. For a drive letter or Finder volume, use Mountain Duck below.
Mountain Duck: a workspace as a drive
Mountain Duck, from the same makers, mounts a connection as a volume in Finder or File Explorer. It uses the same profile list, so the steps are the same.
- 1
Enable dosya.dev under Preferences > Profiles.
Same tab, same checkbox, same fallback download if it is not listed yet.
- 2
Add a new bookmark with the dosya.dev protocol.
Paste the Access Key ID and Secret Key. Put a workspace id in Path to mount one workspace rather than all of them.
- 3
Connect.
The workspace appears as a drive. Any application can open and save files there.
Why not the generic Amazon S3 profile?
The gateway lives at https://api.dosya.dev/s3: every request carries that path.
Cyberduck's generic Amazon S3 profile has a server and a port but no way to prefix a path onto
every request, so it reaches api.dosya.dev and gets an error. The dosya.dev profile
carries the prefix, turns on path-style addressing, which is the only style the gateway answers,
and sets the multipart part size to what the gateway accepts. Those three settings are the whole
difference, and they are why the profile exists.
If you are scripting rather than clicking, the S3 gateway page has the same connection details for the AWS CLI, SDKs and rclone.
If something is off
Login failed, or 403 Forbidden
The secret is wrong, or the key's role cannot use the S3 gateway in that workspace. Generate a fresh pair under Profile > API keys and paste both values again. If one workspace works and another refuses, ask that workspace's owner or admin for access.
A workspace is missing from the list
Only the workspaces the key can reach are listed. An API key can be limited to a single workspace; a key made that way shows that one workspace and nothing else. Check the key in Profile > API keys.
dosya.dev is not in the protocol dropdown
The profile is enabled per machine. Go to Preferences > Profiles and tick dosya.dev, or download the profile above and double-click it.
Uploads of big files fail with 413
The gateway accepts parts up to 50 MB and the profile sends 32 MB parts. If the profile was edited to a larger part size, put it back or re-download it from this page.
It connected with the Amazon S3 profile once, then errors
Switch the bookmark to the dosya.dev profile. The generic profile cannot send the /s3 prefix, so listing and transfers fail in ways that look like permission errors.