How do I use IBM Aspera with Wasabi?

IBM's Aspera High-Speed Transfer Server (HST Server) is validated for use with Wasabi. IBM's Aspera is a data transfer solution to move data quickly across a hybrid cloud environment regardless of network conditions. To use this product with Wasabi, please follow the instructions in this article.

In order for this solution to work, the following components are needed

  • IBM Aspera High Speed Transfer Server
  • IBM Aspera Desktop Client
  • An account on Wasabi cloud storage.

As part of Wasabi's validation testing of this solution, we installed the IBM Aspera HST Server on a Linux distribution instance located close to one of our storage data centers. For more information on the steps to perform the installation refer to the link here.

There are several sections to configuring this solution, as noted below:

1. HST Server Configuration

2. Aspera Desktop Client Configuration

3. Alternate Configuration

The following steps need to be followed to configure the IBM Aspera HST Server to work with your Wasabi storage.

HST Server Configuration

Aspera clients connect to HST Server by authenticating as a system user who is configured in the application. The user can also belong to a group that is configured in the application. Users and groups can be set up in the HST Server GUI. The HST Server uses system accounts to authenticate connections from Aspera clients. The system users must be added and configured as Aspera transfer users before clients can browse the server file system or run FASP transfers to and from the server. When creating transfer users, you can also specify user-specific settings, such as transfer bandwidth, docroot, and file handling. 

1-1. Launch the HST Server as root. Run the following command: 

# asperascp

mceclip0.png

1-2. Click on Configuration.

mceclip1.png

1-3. Select Users tab, and then add a system user by clicking on the + sign. Enter the appropriate name as shown below, and then hit OK.

mceclip2.png

1-4. The Absolute Path, or docroot, is the area of the file system that is accessible to an Aspera transfer user. The default empty value allows access to the entire file system. You can set one global docroot and then further restrict access to the file system by group or individual user. Docroot paths require specific formatting depending on where the transfer server's storage is located. 

Docroot paths may be set to cloud or on-premises object storage in the HST Server GUI or by editing aspera.conf using asconfigurator. To set the docroot for a user with asconfigurator, run the following command:

# asconfigurator -x "set_user_data;user_name,username;absolute,docroot"

where username would be 'testuser' and docroot should be  s3://<access_id>:<secret_key>@s3.wasabisys.com/<bucket_name>

[root@asperaCentOS ~]# asconfigurator -x "set_user_data;user_name,testuser;absolute,s3://S08WOGC5C38C2M4PN0IX:tTNJDYU42Iihzt7Mroubep@s3.wasabisys.com/asperabucket/"
success
user_name: testuser

The docroot can also be configured manually by adding the following text to /opt/aspera/etc/ aspera.conf:

mceclip4.png

1-5. After editing aspera.conf, you must restart asperanoded:

# systemctl restart asperanoded

 

IBM Aspera Desktop Client configuration

2-1. Now, launch the Desktop Client and click on Connections option on the right.

mceclip5.png

2-2. On the Connection Manager screen, click on the '+' sign to add a new connection. Then, configure the host field with your HST Server IP address or hostname, and then add the user credentials. Click on Test Connection to confirm connectivity. Hit OK when done.

mceclip2.png

2-3. Now, select the connection and click on Connect. The client will now try to connect to the HST Server and retrieve the files and folders from the respective Wasabi bucket, as shown below.

mceclip1.png

 2-4. Click on Preferences and set the Default Target Rate for Download and Upload speed limits to appropriate speeds (Options available in Kbps, Mbps and Gbps). Typically, this should be set to the line rate connection speed to get the fastest throughput. Hit OK when done.

mceclip4.png

 

2-5. At this point you can begin transferring files between your local storage and Wasabi via the Aspera HST Server.

mceclip3.png

 2-6. Click on Details to view the transfer status information once the transfer completes.

mceclip6.png

 

Alternate Configuration

3-1. In the above configuration example we configure the user's S3 credentials on the HST Server itself. However, you could set just the S3 permissions for the user on HST Server, and let the user's S3 credentials be stored on the Aspera Desktop Client.

3-2. HST Server configuration

For a user 'svora' the aspera.conf configuration below will allow S3 permissions (read, write, etc). You can still limit the user's control through IAM policies configured on your Wasabi account. See here.

mceclip8.png

3-3. IBM Aspera Desktop Client Configuration

Now, on the Desktop Client configure the Connection with Storage set to Amazon S3, access key and secret access key as shown below. Click on the Browse button to get the client to populate the buckets and select the appropriate bucket.

mceclip10.png

3-4. Click on 'Advanced' (at the bottom) to enter the appropriate Wasabi region service URL. Click here to view the different Wasabi region URLs information. Hit OK when done. 

mceclip11.png

3-5. Hit OK on the Connection Manager to save the settings.

3-6. At this point, you can use the Connection to transfer files via HST Server and keep the S3 credentials stored on the client instead of HST Server.

Have more questions? Submit a request