Enabling IBM Cloud Object Storage Using the Command Line

These instructions explain how to configure your Aspera product for transfers with IBM Cloud Object Storage (IBM COS), which uses the fully S3 API compatible Cleversafe software platform. You will need root privileges to modify the configuration files and restart the trapd service.
Note: If IBM COS is on-premises, the Aspera transfer server (Enterprise Server, Connect Server, Point-to-Point, or Desktop Client) must also be on-premises. If IBM COS is in the Cloud, the Aspera transfer server must be in the same region.

These instructions assume the following:

  1. If IBM COS 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 S3 docroot using the asconfigurator tool.
    # asconfigurator -x "set_user_data;user_name,username;absolute,docroot"
    Where docroot has the following syntax:
    s3://access_key:secret_key@accessor_ip/vault_name"
  3. Open and modify /opt/aspera/etc/trapd/s3.properties.
    # vi /opt/aspera/etc/trapd/s3.properties

    IBM COS does not support getting the vault location. To disable this feature, 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 astrap-config.
     # /opt/aspera/bin/astrap-config.sh enable
  5. Restart Trapd to activate your changes by running the following command:
    # service asperatrapd restart