Wasabi
Wasabi is S3 with a different endpoint and no egress charges, which is why it is the usual choice for backups. Everything on the S3 page applies; this page is the differences.
What you need #
- A Wasabi access key and secret key with access to the bucket.
- The endpoint for the bucket's region —
s3.eu-west-1.wasabisys.com(London),s3.eu-west-3.wasabisys.com(Paris),s3.eu-central-1.wasabisys.com(Amsterdam),s3.us-east-1.wasabisys.com— and the matching region code.
Add it as a storage target #
- Storage → Add → Wasabi.
- Enter key, secret, endpoint and region. The endpoint must match where the bucket lives; a bucket in London addressed through the Paris endpoint fails Test with a region error.
- Test.
Test on the target's row proves the credentials; a target that fails shows the provider's own message until it is fixed. From then on it can be a job's destination, a cloud-to-cloud source, a cloud drive, or an archive.
What it supports #
| Capability | Wasabi |
|---|---|
| Streams uploads | Yes |
| Version history | Native bucket versioning (Wasabi supports it); otherwise sidecar |
| Realtime cloud-copy source | Yes — Wasabi publishes to an AWS SNS topic |
| Cloud-drive mount | Yes |
| Reachable from the Cloud Agent | Yes |
| Browse in the console | Yes |
Things to know #
Realtime via SNS. Wasabi has no notification service of its own; it publishes bucket events to an AWS SNS topic. The topic and Caryvane's subscription are set up on the AWS side exactly as for S3. The Wasabi-specific gotcha: the AWS IAM key you enter in Wasabi's Configure Region → notifications is what Wasabi publishes with, and it needs sns:Publish on the topic — a stale or under-privileged key there produces no events and no error.
Minimum storage duration. Wasabi bills deleted objects for 90 days from upload. Version pruning and archive removals are therefore not free within that window; size retention accordingly.