Transmit 5.0 has been certified for use with Wasabi. To use Transmit with Wasabi, configure the Transmit app as shown below (screenshot for Transmit 5.0). The screen fields should be as follows.
Protocol: Amazon S3
Address: s3.wasabisys.com
Port: 443 (default)
Access Key ID: Your Wasabi access key
Secret: Your Wasabi secret key
Remote Path: accept default or specify what you want
Note that this example uses Wasabi’s us-east-1 storage region. To use other Wasabi storage regions, use the appropriate Wasabi service URL as described in this article.
Known issue of Transmit’s Multipart Upload feature with S3
If customers try to upload an object larger than 5GB, they will get an error message like this.
According to the Transmit support team, the only signature method supported for S3 object storage services is V2 on Multipart Uploads. From Wasabi, tests have demonstrated that this signature method generates malformed requests, which are answered with a SignatureDoesNotMatch error message, as the error message shown above.
Wasabi does support V2 and V4 signatures on requests (more information here). Customers can use V2 signature with features such as Multipart Uploads, too. This has been tested with applications such as S3 Browser, which uses the V2 signature by default.
