S3 Browser is certified for use with Wasabi. To use this product with Wasabi, configure S3 Browser as shown below.
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 Service URLs for Wasabi’s Storage Regions.
FAQ
#1 Why is Make public/Make private not working when trying to change permissions on an object in the S3 browser?
The S3 browser tool applies these changes by modifying the permissions on your account's ACLs. The ACLs are a deprecated form of Access Control and are recommended only for legacy applications. In order to best delegate access, it is recommended to utilize bucket and IAM policies. More information about Wasabi policies is available in the Wasabi Console User Guide.
#2 IAM Access Manager on S3 browser does not work with Wasabi.
Currently, the Access Manager feature of the S3 browser is unsupported with WasabiIAM. We recommend using the Wasabi console to manage users via a GUI.