Using Wasabi with ezS3 for Cost-Effective Storage
Wasabi offers no egress fees and flat-rate pricing. Connect Wasabi to ezS3 for secure team access, browser uploads, and predictable storage costs.
Wasabi takes a different approach to cloud storage pricing—no egress fees, no API request fees, just one flat rate per TB per month. ezS3 supports Wasabi as an S3-compatible provider with a dedicated connection form: you choose a region and your credentials, and ezS3 derives the correct endpoint so you don’t have to look it up.
Why Choose Wasabi?
- No egress fees: Download as much data as you need at no extra cost
- Predictable pricing: Flat rate per TB per month
- S3-compatible: Works with ezS3’s same access control, audit log, and browser upload/download flows
- Immutable storage: Optional object lock for compliance
Step 1: Create a Wasabi Bucket and Access Keys
- Sign up for a Wasabi account and create a bucket in the region you want (e.g. us-east-1, eu-central-1).
- In the Wasabi console, go to Settings → Access Keys and click Create New Access Key.
- Copy the Access Key ID and Secret Key and store them somewhere safe (you’ll paste them into ezS3 in the next step).
Step 2: Add a Wasabi Provider in ezS3
- In ezS3, go to Storage Providers and click Add Provider.
- Choose Wasabi Hot Cloud Storage.
- Fill in the form:
- Region — The Wasabi region where your bucket lives (e.g.
us-east-1,eu-central-1). You can type the region code or pick from the suggestions. ezS3 will show and use the correct endpoint for that region; you don’t enter an endpoint URL yourself. - Bucket scopes (optional) — Leave blank to let ezS3 list all buckets the key can access. If the key can’t list buckets, enter a comma-separated list of bucket names (e.g.
marketing-assets, backups). - Access key ID — Your Wasabi access key.
- Secret key — Your Wasabi secret key.
- Region — The Wasabi region where your bucket lives (e.g.
- Leave Allow ezS3 to update bucket CORS settings (recommended) on so ezS3 can add the ezs3.net origin for browser uploads.
- Save. ezS3 validates the connection and then you can assign buckets to roles and start using them.
How ezS3 Picks the Wasabi Endpoint
ezS3 derives the endpoint from the Region you choose:
- us-east-1 →
https://s3.wasabisys.com - Any other region →
https://s3.<region>.wasabisys.com(e.g.https://s3.eu-central-1.wasabisys.com)
So you only need to know your bucket’s region; the endpoint is set automatically. Supported regions include us-east-1, us-east-2, us-central-1, us-west-1, us-west-2, ca-central-1, eu-central-1, eu-west-1, ap-northeast-1, ap-northeast-2, ap-southeast-1, and ap-southeast-2.
Pricing Comparison
For teams with high egress, Wasabi’s pricing model shines:
Scenario: 5 TB storage, 10 TB egress per month
| Provider | Storage | Egress | Total |
|---|---|---|---|
| AWS S3 | ~$115 | ~$900 | ~$1,015 |
| Wasabi | ~$30 | $0 | ~$30 |
Prices as of 2025 and subject to change
Important Limitations
Wasabi has some limitations to be aware of:
- Minimum retention: Files must be stored for at least 90 days (paid even if deleted earlier)
- No object versioning: Unlike S3, Wasabi doesn’t support versioning
- Smaller ecosystem: Fewer third-party integrations than AWS
Best Use Cases for Wasabi
Wasabi is ideal for:
- Backup and archive: Long-term data storage with frequent access
- Media storage: Video files, images, and other large media
- Data distribution: High-volume downloads without egress fees
- Surveillance: Security camera footage and similar data
Ready to save on storage costs? Sign up for ezS3 and connect your Wasabi bucket today.
Read next
Configuring Cloudflare R2 with ezS3
Cloudflare R2 is S3-compatible object storage with simple pricing. Create an R2 token, connect it to ezS3, and use auto CORS so browser uploads work.
Configuring Backblaze B2 with ezS3
Connect Backblaze B2 to ezS3 for secure team access to S3-compatible storage. Set up buckets, CORS, and browser uploads in minutes.
Configuring DigitalOcean Spaces with ezS3
Connect DigitalOcean Spaces to ezS3 for secure team access. Create a Space, add an API key, and enable browser uploads with auto CORS.