Wasabi S3 Back end

I am new to Rocket Chat, and I am looking to make maintenance as simple as possible. We use Wasabi extensively as our S3-compatible back end as it is fast, reliable and affordable, without the complexity that often comes with working with Amazon S3. I would prefer not to have multiple S3 services going, so I am looking for some hints on getting the service working with Wasabi.

Has anyone done it? Wasabi is supposed to be 100% S3 compatible, but I am getting nothing but errors.

Server Setup Information

  • Version of Rocket.Chat Server: 3.8.2
  • Operating System: Linux - ubuntu 20.04.1
  • Deployment Method: Snap
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: 12.18.4
  • MongoDB Version:
  • Proxy: None
  • Firewalls involved: None

Any additional Information

I have tried running both v4 and v3 API calls.

For anyone who follows in my footsteps, it was actually really simple.

I followed this example:
https://blogs.oracle.com/developers/team-chat-for-free-with-rocketchat-on-the-oracle-cloud#os

Bucket Name: Actually creartes a SUB bucket if you use this
ACL: Empty
Access Key: You should know it
Secret Key: Again, you should know.
Region: Actually but the Wasabi region in.
Bucket URL: https://name-of-bucket.s3.wasabisys.com (or whatever your region)
API: v4
Force Path Style: yes

Works like a dream, couldn’t be happier.

3 Likes

Thanks for taking the time to come back and post your solution. I plan on giving this a try tonight.

1 Like

We keep it simple. We use both Veeam and Acronis to wasabi has a replication point for the onsite backup. 30 dollars per TB I think. That’s just the wasabi charge. Not what we charge for the actual backup process Kodi nox