Wasabi is now validated for use with Globus Connect Server to deliver advanced file transfer and sharing capabilities. We have tested Wasabi with Globus Connect Server version 4.0.57 with AWS S3 connector add-on.
Requirements
Creation of buckets in Wasabi Hot Cloud Storage
A Globus Connect Server with AWS S3 Connector (the connector is available as an add-on to organizations with a Globus subscription)
Admin access to the Globus Connect Server via ssh
Configuring the Globus Connect Server
To configure the Globus Connect Server to use your Wasabi Hot Cloud Storage:
Configure the AWS S3 connector.
Edit the file
/etc/globus/globus-gridftp-server-s3.confand set the host_name option to be the appropriate Wasabi S3 endpoint URL for the desired region. While buckets in all regions will be accessible, buckets created by the AWS S3 Connector will be created in this region. This would generally be the closest region geographically.For example, to configure the AWS S3 Connector to use the us-east-1 region:
host_name = s3.wasabisys.comNote - if you would prefer to create buckets in a region other than us-east-1 use the appropriate service URL. See Service URLs for Wasabi's Storage Regions.
Create a file for each user containing the S3 credentials.
Each user will need to have a special file created, which specifies the S3 credentials associated with their local user account. The default
s3_map_filenameconfiguration for the AWS S3 Connector looks in$HOME/.globus/s3for a file mapping the current user’s ID to S3 access keys. Each user who will use the AWS S3 Connector must create such a file containing their credentials. This file can be created and populated by the user with the following commands:# mkdir -m 0700 -p ~/.globus # (umask 077; echo "$(id -un);$S3_ACCESS_KEY_ID;$S3_SECRET_ACCESS_KEY" \ > ~/.globus/s3)For example, the s3 file mentioned above should look like this.
#userjoe@GlobusConnectServer:~/.globus$ cat s3
userjoe;S08WABCDC38C2M4PN0IX;tTNi4tgnskdldk890HSG2HYDMQ7n7jKrRwWXPJDYNote - Don’t use the access and secret key above, it is just an example
OPTIONAL - Since S3 users do not need user accounts on the local Globus Connect Server endpoint, S3 transfers can be configured to run under a local service user account. Create a user named
globus-s3, and add the following line to the /etc/gridftp.d/gridftp-s3 configuration file:process_user globus-s3The
s3_map_filenamecredential file ($HOME/.globus/s3)configuration, and Globus Connect Server configuration that refers to$HOME, will use the home directory of this account. Ensure that these files are accessible only to theglobus-s3account.All credentials must be stored in a single
s3_map_filenamein the format above, by default in the file~globus-s3/.globus/s3. The username must correspond to the username based on the Globus Connect ServerAuthorizationMethodFor more information about the steps above, visit the Globus documentation.
Use the Globus application web interface.
At this point, you should be able to load your Wasabi buckets after successfully logging in to your Globus Connect Server endpoint through the Globus web application (https://app.globus.org).
In order to perform a file transfer, click on File Manager, and enter the name of your Globus Connect Server endpoint (example, partnersteam#partners) in the Collections field to load the buckets.

Enter a different endpoint as a Collection and perform file transfers back and forth. In the example below, a Globus Connect Personal client is installed on a PC (example WasabiLaptop below) to act as an endpoint.

Select the file you want to transfer, then click Start at the bottom to initiate the transfer.

Select Transfer & Sync Options by clicking the down arrow key shown above.

Once the transfer is requested successfully, you will see the following notification on the screen.

Click Activity on the left bar to see if the transfer goes through successfully.

You should also expect an email notification from Globus about the transfer status once it is complete.
