Enabling IBM Cloud Object Storage (COS) - S3 Using the Command Line

You can configure your Aspera server to enable transfers with IBM Cloud Object Storage (COS) - S3.
Note: If IBM COS - S3 is on-premises, the Aspera transfer server must also be on-premises. If IBM COS - S3 is in the Cloud, the Aspera transfer server must be in the same region.

Prerequisites:

  1. If IBM COS - S3 is in the Cloud, connect to your server through SSH and elevate to the root user.
    # ssh -i identity_file -p 33001 user@host_ip_address
    # sudo su -
  2. Set the transfer user's docroot.
    # asconfigurator -x "set_user_data;user_name,username;absolute,docroot"
    Where docroot has the following syntax:
    s3://access_id:secret_key@accessor_endpoint/vault_name
  3. Open and modify /opt/aspera/etc/trapd/s3.properties.
    # vi /opt/aspera/etc/trapd/s3.properties

    IBM COS - S3 does not support retrieving the vault location, so this feature must be disabled. Find the line #aspera.session.check-bucket.transfer=true, uncomment it, and change the value to false. For example:

    #Whether to check against cross-region transfers
    #Default is true
    aspera.session.check-bucket.transfer=false

    Using vault names in requests does not work if DNS is not configured. To disable the use of vault names in the request hostname, find the line #s3service.disable-dns-buckets=false, uncomment the line, and change the value to true. For example:

    #Disable use of bucket name in request hostname.
    #Default (and recommended) is false
    s3service.disable-dns-buckets=true
  4. Enable the Trapd service.
    # /opt/aspera/bin/astrap-config.sh enable
  5. Restart Trapd to activate your changes.
    # /etc/init.d/asperatrapd restart