# How do I connect Cyberduck to S3-compatible storage?

> Connect Cyberduck to an S3-compatible bucket: S3 (HTTPS) profile, server, two keys, the path-style fix, old versions. Steps from the Cyberduck docs.

- URL: https://privates3.com/guides/how-to-connect-cyberduck-to-s3/
- Last updated: 2026-11-17
- Publisher: PrivateS3 (https://privates3.com)

**Quick answer — How do I connect Cyberduck to S3-compatible storage?**

Click Open Connection, pick the S3 (HTTPS) profile, type the endpoint as the server, then enter the Access Key ID and Secret Access Key. For a **PrivateS3** bucket the server is `s3.privates3.com` and the region `eu-central-1`. The connection takes 5 steps, and storage costs $2.23/TB-month on 12 months.

**In brief**

- **Profile**: S3 (HTTPS), bundled with Cyberduck.
- **Server**: the endpoint shown with the keys in the client area; examples use `s3.privates3.com`.
- **If it fails** with "Cannot read container configuration": switch to path-style requests.
- **Extras**: versions per bucket from File → Info, and Cryptomator vaults for encryption.

## What goes in each Cyberduck field?

*Cyberduck connection fields for an S3-compatible bucket and the values for PrivateS3*

| Cyberduck field | Value | Note |
| --- | --- | --- |
| Protocol | S3 (HTTPS) | Bundled profile |
| Server | `s3.privates3.com` | Endpoint from the client area |
| Port | 443 | HTTPS |
| Access Key ID | `ACCESS_KEY` | One key pair per bucket |
| Secret Access Key | `SECRET_KEY` | Asked in the login prompt; can be saved in the keychain |
| Path | `/BUCKET` | Optional, in a bookmark, to open the bucket directly |

## How do you connect, step by step?

Cyberduck's connection and S3 pages, read on 17 November 2026, describe each action below.

1. **Get the keys** — Buy a plan and wait for the bucket: Bucket and access keys created by a person within 24 hours of the order. Copy the Access Key ID and Secret Access Key from the client area.
2. **Open a connection** — Click New Connection in the toolbar, or File → Open Connection (⌘O on macOS, Ctrl+O on Windows).
3. **Pick the profile** — Choose S3 (HTTPS) in the protocol list and type s3.privates3.com as the server.
4. **Log in** — Enter the Access Key ID, then the Secret Access Key in the login prompt. The bucket appears as a folder.
5. **Save a bookmark** — Choose Bookmark → New Bookmark to keep these settings, and add /BUCKET as the path if you like.

## What if Cyberduck says it cannot read the container configuration?

**Switch to path-style requests.** Cyberduck's S3 documentation says some S3-compatible servers fail with "Cannot read container configuration" under the default virtual-host style. It offers two fixes:

- Install the S3 (Deprecated path style requests) profile from Preferences → Profiles and connect with it.
- Or set the hidden option `s3.bucket.virtualhost.disable` to `true`.

PrivateS3 accepts both path-style and virtual-hosted URLs, so the default profile normally works. The path-style fix is there for bucket names that do not resolve in DNS.

## How do you see and restore old versions in Cyberduck?

**Turn versioning on in File → Info → S3, then show hidden files to see older versions.** Cyberduck's docs say versioning is enabled per bucket from the Info window (⌘I on macOS, Alt+Return on Windows). View → Show Hidden Files lists previous versions, and File → Revert makes one current again.

At PrivateS3: S3 versioning can be turned on per bucket from any S3 client; old versions count toward the quota. The [versioning guide](https://privates3.com/guides/how-to-turn-on-s3-versioning/ "How do I turn on S3 versioning?") shows the same switch from the command line, with a rule to expire old versions.

## Can Cyberduck encrypt files before upload?

**Yes, through Cryptomator vaults, which Cyberduck's documentation covers in its Cryptomator section.** A vault stores files encrypted in the bucket; Cyberduck shows them decrypted while you work. Without client-side encryption, the operator can technically read stored files, file names and sizes; with it, the operator sees only encrypted blobs, their sizes and upload times.

The vault password is the only key. Lose it and the files cannot be read, by you or by PrivateS3. The [encryption how-to](https://privates3.com/guides/how-to-encrypt-files-before-cloud-upload/ "How do I encrypt files before uploading them to the cloud?") compares Cryptomator with rclone crypt. According to PrivateS3's survey of 17 November 2026, PrivateS3 bills no fee per upload or download request, so browsing a large bucket in Cyberduck costs nothing extra.

## Cyberduck and S3: common questions

### Do I need a special profile for PrivateS3?

No. The bundled S3 (HTTPS) profile works. Extra profiles from Preferences → Profiles are only needed for path-style requests.

### Why do I not see other buckets?

Each PrivateS3 key pair opens one bucket, so Cyberduck shows only that bucket.

### Can I share a file from the bucket?

Yes, with a presigned URL. The AWS CLI command `aws s3 presign` makes one valid for 3,600 seconds by default, up to 7 days.

### Should I use the S3 (HTTP) profile?

No. Cyberduck offers it for servers without SSL; the PrivateS3 endpoint uses HTTPS, so keep S3 (HTTPS).

### Where do I find my keys again?

In the client area; the [access keys help page](https://privates3.com/help/get-your-access-keys/ "How do I get my PrivateS3 access keys?") shows where.

**Verdict**

- **Cyberduck is the click-and-drag way into an S3-compatible bucket**: S3 (HTTPS) profile, server, two keys.
- **On PrivateS3** that is enough to use a [1 TB bucket](https://privates3.com/1tb-cloud-storage/ "How much does 1 TB of S3 cloud storage cost?") with no command line, paid in crypto.

## Sources

1. [Amazon S3](https://docs.cyberduck.io/protocols/s3/) — Cyberduck documentation (read 17 November 2026)
2. [Connection](https://docs.cyberduck.io/cyberduck/connection/) — Cyberduck documentation (read 17 November 2026)
3. [aws s3 presign](https://docs.aws.amazon.com/cli/latest/reference/s3/presign.html) — AWS CLI Command Reference (read 17 November 2026)

**A bucket for Cyberduck: 1 TB for 12 months, $26.77** S3 (HTTPS), keys within 24 hours, paid in crypto. [Get a bucket](https://privates3.com/app/checkout/?plan=s3-1t-12m&product=storage&from=how-to-connect-cyberduck-to-s3&lang=en)

---

PrivateS3: PrivateS3 sells S3-compatible object storage billed per terabyte for backups and files (restic, rclone, Veeam, Cyberduck, Nextcloud), meant to be encrypted on the customer's side before upload. A terabyte costs $5.40 a month or $26.77 for 12 months, 10% under the lowest comparable offer read on 17 November 2026, with no API or egress fees up to 3 times the stored size, paid in crypto with no ID document.
