What is Wasabi?
Wasabi is the S3-compatible object-storage company that built its entire business on one number: $6.99 per TB per month, with no egress fees and no API request fees. That pricing — about 80 % cheaper than AWS S3 Standard at typical access volumes — has made Wasabi a default destination for backup vendors (Veeam, MSP360, Synology Active Backup), media archives, and any team escaping AWS egress costs. Wasabi Hot Cloud Storage is fully S3-API-compatible, runs in 13+ regions across North America, Europe and Asia-Pacific, offers Object Lock for ransomware-immutable backups, and replicates objects across multiple AZs for 11-nines durability. The 'Hot' in the name signals that there are no cold-tier retrieval delays — every byte is online and accessible at request time.
Wasabi's catch is its 90-day minimum storage duration: any object deleted before it has been stored for 90 days is still billed for the remaining days at the standard rate, plus a Timed Deleted Storage charge. There's also a 1 TB minimum monthly charge on the Pay-as-You-Go plan — even if you store less. CloudsLinker is purpose-built to play well with Wasabi's pricing model: incremental sync minimizes deletes, lifecycle-aware copies route cold data to S3 Glacier Deep Archive while keeping warm working sets on Wasabi, and migrations into Wasabi use multipart uploads with parallel parts for the fastest possible initial seeding.
Key features of Wasabi
Why connect Wasabi to CloudsLinker
CloudsLinker connects to Wasabi using standard S3 Access Key + Secret Key + Endpoint (region-specific, e.g. s3.us-east-2.wasabisys.com). Once connected, transfers run server-to-server using the S3 multipart upload API — objects above 100 MB are split into 5 MB–5 GB parts and uploaded in parallel for maximum throughput. The same connector handles Wasabi as source, destination, or both sides of a Wasabi-to-Wasabi cross-region replication job. CloudsLinker preserves user metadata headers, object tags (where supported), and modification times across providers.
What you can do with Wasabi on CloudsLinker
S3 multipart copies in and out of Wasabi
Migrate from AWS S3, B2, R2 or GCS into Wasabi at full multipart-parallel speed. Or copy <em>out</em> of Wasabi to any cloud — no egress fees apply if your monthly egress ≤ stored volume.
No bandwidth from your side
Wasabi transfers run on CloudsLinker's servers, not yours. Your home or office connection is irrelevant to job throughput.
Scheduled & incremental sync
Hourly / daily / weekly sync jobs with delta mode — only changed objects are copied each run, minimizing the 90-day-retention penalty for short-lived data.
Filter by prefix, size, modified date
Migrate only <code>s3://bucket/2026/</code>, skip files > 100 GB, or sync only objects modified in the last 7 days.
Common Wasabi transfer scenarios
Cut AWS egress fees: S3 → Wasabi for high-traffic origin
If your S3 bucket serves more than ~$200/month in egress to the public internet, copying it to Wasabi via CloudsLinker often pays for itself in the first month. CloudsLinker scripts the initial seed (multipart parallel), then nightly delta sync keeps Wasabi current. Front Wasabi with Cloudflare or your own CDN and your egress bill effectively drops to zero.
Cross-provider DR: Wasabi as off-site backup of S3 / Azure / GCS
S3 Replication keeps you inside AWS; a full-account compromise hits both copies. Schedule a CloudsLinker incremental from your primary S3 bucket to a Wasabi bucket in a different region — for ~$7/TB/month you get true provider-independent DR with Object Lock immutability.
Large-file media archive: video / 3D / scientific datasets
Wasabi's 5 TB max object size and multipart support are ideal for video masters, 3D renders, and scientific datasets that don't fit cleanly on consumer clouds. CloudsLinker handles the multipart upload from your source (S3, R2, NAS via SFTP) to Wasabi at high throughput.
Backup Veeam / MSP360 / Synology repositories to a second Wasabi region
Many backup vendors target Wasabi as primary; CloudsLinker can mirror those backup buckets to a second Wasabi region for added redundancy without paying egress (since destination is also Wasabi). Ideal for backup admins who want geo-redundancy without paying double for storage.
Migrate from Wasabi → Cloudflare R2 if access patterns shifted
Wasabi's free-egress rule applies only when egress ≤ stored. If your bucket grew into a high-egress workload (10×+ stored volume per month), Cloudflare R2's true zero-egress model becomes cheaper. CloudsLinker copies between Wasabi and R2 with multipart speed — typically 1–3 TB/day per connection.
How to connect Wasabi to CloudsLinker
Wasabi authenticates with S3-style Access Key + Secret Key, plus a region-specific endpoint URL.
Before you start
Create a dedicated Wasabi sub-user for CloudsLinker — never use the root account credentials:
- Sign in to the Wasabi console at https://console.wasabisys.com.
- Go to Access Keys → Create New Access Key.
- Select Sub-user rather than Root, and attach a policy scoped to the buckets you want CloudsLinker to read / write. For migration jobs, the minimum permissions are:
s3:ListBucket,s3:GetObject(source)s3:PutObject,s3:DeleteObject,s3:AbortMultipartUpload(destination)
- Copy the Access Key ID and Secret Access Key — Wasabi shows the secret only once.
Connection steps
- In CloudsLinker, click Add Cloud → choose Wasabi.
- Enter a display name (e.g. “Wasabi us-east-2”).
- Paste the Access Key ID and Secret Access Key from the Wasabi console.
- Enter the Endpoint URL matching your bucket’s region:
s3.us-east-1.wasabisys.com(Virginia)s3.us-east-2.wasabisys.com(N. Virginia)s3.us-west-1.wasabisys.com(Oregon)s3.eu-central-1.wasabisys.com(Amsterdam)s3.eu-west-1.wasabisys.com(London)s3.ap-northeast-1.wasabisys.com(Tokyo)- …or the region your bucket lives in (Wasabi has 13+ regions).
- Click Confirm. CloudsLinker validates the credentials with a
ListBucketscall and shows the connection as ready.
Revoke access
To revoke CloudsLinker’s keys later: https://console.wasabisys.com → Access Keys → find the key → Delete. Or rotate by creating a new key and deleting the old one.
Wasabi upload & download limits you should know
Wasabi’s storage and API limits mirror AWS S3 closely; the unique constraints are around pricing policies (90-day retention, 1 TB minimum, free-egress rule):
- Maximum object size: 5 TB (achieved via multipart upload).
- Single PUT max: 5 GB — beyond that, multipart is required. CloudsLinker switches automatically above 100 MB.
- Multipart parts: 5 MB minimum, 5 GB maximum, 10,000 parts max per object.
- Incomplete multipart cleanup: Wasabi auto-aborts incomplete multipart uploads after 31 days, preventing dangling-storage charges.
- API rate limits: Wasabi does not publish strict per-second rate limits but applies throttling on aggressive patterns. CloudsLinker handles back-off automatically.
- Storage pricing: $6.99 per TB per month, single rate across all 13+ regions.
- Free egress rule: if monthly egress ≤ active stored volume, egress is free. Sustained excess may trigger throttling or service suspension.
- 90-day minimum retention: delete before 90 days → still billed for the remaining days. Critical for high-churn workloads.
- 1 TB monthly minimum: Pay-as-You-Go customers billed for 1 TB even if they store less.
- Bucket / object count: no published cap (effectively unlimited).
- Object Lock retention: supported, with WORM compliance for ransomware-resistant backups.
Sources: Wasabi Pricing, Wasabi: Min and max object sizes, Wasabi: Multipart upload behavior, Wasabi: Minimum Storage Duration Policy.
Wasabi + CloudsLinker — Frequently Asked Questions
Does Wasabi really charge zero egress?
What's the 90-day minimum retention penalty?
What's the maximum object size?
Are my Wasabi keys stored securely on CloudsLinker?
Does CloudsLinker support all Wasabi regions?
s3.us-east-2.wasabisys.com for us-east-2, s3.eu-central-1.wasabisys.com for eu-central-1). For cross-region copies, connect each region as a separate cloud.
Will multipart uploads from CloudsLinker incur extra cost?
UploadPart nor CompleteMultipartUpload costs anything. The only billing event is storage. Note: incomplete multipart uploads are auto-deleted after 31 days to prevent dangling charges.
How fast can CloudsLinker push data into Wasabi?
Does CloudsLinker preserve S3 metadata, tags, and Object Lock?
x-amz-meta-*) and content-type are preserved. Object tags are preserved when both sides support them. Object Lock retention dates are preserved when copying between Object-Lock-aware providers (Wasabi, S3, R2 with Object Lock, B2).
Can I migrate from AWS S3 to Wasabi without leaving AWS?
Is Wasabi suitable for high-churn data?
Wasabi transfer guides
Step-by-step walkthroughs for moving data to and from Wasabi.
Conclusion
Wasabi's flat $6.99/TB pricing and no-egress model rewrites the economics of cloud storage for backup, archive, and high-traffic media — but only if you respect the 90-day minimum retention and stay within the egress-≤-storage rule. CloudsLinker is built around those constraints: incremental sync to minimize deletes, multipart parallel uploads for fast initial seeding, and filters to keep cold-but-churn data off Wasabi entirely. Connect with Access Key + Endpoint and run your first migration in minutes.
Online storage services supported by CloudsLinker
Transfer data between over 49 cloud services with CloudsLinker
Didn't find your cloud service? Contact: [email protected]