Asperalm - A Ruby library for Aspera transfers and "Amelia", the Multi Layer IBM Aspera Command Line Tool

Version : 0.11.1


This gem provides a ruby API to Aspera transfers and a command line interface to Aspera Applications. Location:


  • Aspera, FASP are owned by IBM
  • This GEM is not endorsed/supported by IBM/Aspera
  • Use at your risk (not in production environments)
  • This gem is provided as-is, and is not intended to be a complete CLI, or industry-grade product.
  • some features may not be fully validated
  • IBM provides an officially supported Aspera CLI: .

That being said, mlia is very powerful and gets things done, it's also a great tool to learn Aspera APIs.

This manual addresses three parts:

  • mlia : ("Amelia") The Multi Layer IBM Aspera tool
  • asession : starting a FASP Session with JSON parameters
  • Asperalm : includes a Ruby "FASPManager"

In examples, command line operations (starting with $) are shown using a standard shell: bash.

Command line parameters in example beginning with my_, like my_param_value are user proviuded value and not fixed value commands.

Quick Start

This section guides you from installation, first use and advanced use.

First, follow the section: Installation (Ruby, Gem, FASP) to start using mlia.

Once the gem is installed, mlia shall be accessible:

$ mlia --version

First use

Once installation is completed, you can proceed to the first use with a demo server:

If you want to test with Aspera on Cloud, jump to section: Wizard

If you want to test with Aspera demo transfer server:

$ mlia server browse / --url=ssh:// --username=asperaweb --password=demoaspera
:   zmode    :   zuid    : zgid :  size  :           mtime           :         name          :
: dr-xr-xr-x : asperaweb : fasp : 4096   : 2014-04-10 19:44:05 +0200 : aspera-test-dir-tiny  :
: drwxr-xr-x : asperaweb : fasp : 176128 : 2018-03-15 12:20:10 +0100 : Upload                :
: dr-xr-xr-x : asperaweb : fasp : 4096   : 2015-04-01 00:37:22 +0200 : aspera-test-dir-small :
: dr-xr-xr-x : asperaweb : fasp : 4096   : 2018-05-04 14:26:55 +0200 : aspera-test-dir-large :

In order to make further calls more convenient, it is advised to define a option preset for the servers identification options. The following example will:

  • create a option preset
  • define it as default for "server" plugin
  • list files in a folder
  • download a file
$ mlia config id demoserver update --url=ssh:// --username=asperaweb --password=demoaspera
updated: demoserver
$ mlia config id default set server demoserver
updated: default→server to demoserver
$ mlia server browse /aspera-test-dir-large
:   zmode    :   zuid    : zgid :     size     :           mtime           :            name            :
: -rw-rw-rw- : asperaweb : fasp : 10133504     : 2018-05-04 14:16:24 +0200 : ctl_female_2.fastq.partial :
: -rw-r--r-- : asperaweb : fasp : 209715200    : 2014-04-10 19:49:27 +0200 : 200MB                      :
: -rw-r--r-- : asperaweb : fasp : 524288000    : 2014-04-10 19:44:15 +0200 : 500MB                      :
: -rw-r--r-- : asperaweb : fasp : 5368709120   : 2014-04-10 19:45:52 +0200 : 5GB                        :
: -rw-r--r-- : asperaweb : fasp : 500000000000 : 2017-06-14 20:09:57 +0200 : 500GB                      :
: -rw-rw-rw- : asperaweb : fasp : 13606912     : 2018-05-04 14:20:21 +0200 : ctl_male_2.fastq.partial   :
: -rw-rw-rw- : asperaweb : fasp : 76           : 2018-05-04 14:13:18 +0200 : ctl_female_2.fastq.haspx   :
: -rw-rw-rw- : asperaweb : fasp : 647348       : 2018-05-04 14:26:39 +0200 : ctl_female_2.gz            :
: -rw-rw-rw- : asperaweb : fasp : 74           : 2018-05-04 14:16:00 +0200 : ctl_male_2.fastq.haspx     :
: -rw-r--r-- : asperaweb : fasp : 1048576000   : 2014-04-10 19:49:23 +0200 : 1GB                        :
: -rw-r--r-- : asperaweb : fasp : 104857600    : 2014-04-10 19:49:29 +0200 : 100MB                      :
: -rw-r--r-- : asperaweb : fasp : 10737418240  : 2014-04-10 19:49:04 +0200 : 10GB                       :
$ mlia server download /aspera-test-dir-large/200MB
Time: 00:00:02 ========================================================================================================== 100% 100 Mbps Time: 00:00:00

Going further

Get familiar with configuration, options, commands : Command Line Interface.

Then, follow the section relative to the product you want to interact with ( Aspera on Cloud, Faspex, ...) : Application Plugins


In order to use the tool or the gem, it is necessary to install those components:

The following sections provide information on the installation.


A ruby interpreter is required to run the tool or to use the gem and tool. It is required to have privilege to install gems. Ruby 2.5+ is prefered, but it should also work with 2.1+. Any type of Ruby installation can be used.

Refer to the following sections for a proposed method for specific operating systems.


Install Ruby using "homebrew" from here:

Then install latest Ruby:

$ brew install ruby

Alternatively, Ruby came pre-installed on macOS (but maybe not on more modern versions). Starting with Macos Sierra, the version of Ruby is high enough. In that case, installation of the gem requires: sudo gem install asperalm.


Install Latest stable Ruby using

Go to "Downloads".

Select the version "without devkit", x64 corresponding to the one recommended "with devkit".

During installation, skip the installation of "MSys2".


Install Latest Ruby using "rvm" . It installs by default in /usr/local/rvm , but you can install in another location:

curl -sSL | bash -s -- --path /my/special/path

Once installed, you can install latest ruby:

# rvm install ruby

If you dont want all users to have ruby by default, rename the file: /etc/profile.d/ with another extension, and source it to get rvm.

Alternatively, only if you know what you do, on RPM based systems (CentOs, Redhat), install the ruby provided by yum which may be 2.0. Pre-install jwt for older Ruby < 2.1.

# yum install -y ruby
# gem install jwt -v 1.5.6

You can cleanup your whole yum-installed ruby environment like this to uninstall:

gem uninstall $(ls $(gem env gemdir)/gems/|sed -e 's/-[^-]*$//')
yum remove -y ruby ruby-libs

asperalm gem

Once you have Ruby and rights to install gems: Install the gem and its dependencies:

# gem install asperalm

To upgrade to the latest version:

# gem update asperalm

FASP Protocol

Most file transfers will be done using the FASP protocol. Only two additional files are required to perform an Aspera Transfer:

  • ascp
  • aspera-license (in same folder, or ../etc)

Those can be found in one of IBM Asprea transfer server or client with its license file (some are free):

  • IBM Aspera Connect Client (Free)
  • IBM Aspera Desktop Client (Free)
  • IBM Aspera CLI (Free)
  • IBM Aspera High Speed Transfer Server (Licensed)
  • IBM Aspera High Speed Transfer EndPoint (Licensed)

For instance, Aspera Connect Client can be installed by visiting the page:

mlia will detect most of Aspera transfer products in standard locations and use the first one found. Refer to section FASP for details on how to select a client or set path to the FASP protocol.

Several methods are provided on how to start a transfer. Use of a local client is one of them, but other methods are available. Refer to section: Transfer Agents

Command Line Interface: mlia

The asperalm Gem provides a command line interface (CLI) which interacts with Aspera Products (mostly using REST APIs):

  • IBM Aspera High Speed Transfer Server (FASP and Node)
  • IBM Aspera on Cloud (including ATS)
  • IBM Aspera Faspex
  • IBM Aspera Shares
  • IBM Aspera Console
  • IBM Aspera Orchestrator
  • and more...

mlia provides the following features:

  • Supports most Aspera server products (on-premise and SaaS)
  • Any command line options (products URL, credentials or any option) can be provided on command line, in configuration file, in env var, in files
  • Supports Commands, Option values and Parameters shortcuts
  • FASP Transfer Agents can be: FaspManager (local ascp), or Connect Client, or any transfer node
  • Transfer parameters can be altered by modification of transfer-spec, this includes requiring multi-session
  • Allows transfers from products to products, essentially at node level (using the node transfer agent)
  • Supports FaspStream creation (using Node API)
  • Supports Watchfolder creation (using Node API)
  • Additional command plugins can be written by the user
  • Supports download of faspex and Aspera on Cloud "external" links
  • Supports "legacy" ssh based FASP transfers and remote commands (ascmd)

Basic usage is displayed by executing:

$ mlia -h

Refer to sections: Usage and Sample Commands.

Not all mlia features are fully documented here, the user may explore commands on the command line.

Arguments : Commands and options

Arguments are the units of command line, as parsed by the shell, typically separated by spaces (and called "argv").

There are two types of arguments: Commands and Options. Example :

$ mlia command --option-name=VAL1 VAL2
  • executes command: command
  • with one option: option_name
  • this option has a value of: VAL1
  • the command has one additional argument: VAL2

When the value of a command, option or argument is constrained by a fixed list of values, it is possible to use the first letters of the value only, provided that it uniquely identifies a value. For example mlia conf ov is the same as mlia config overview.

The value of options and arguments is evaluated with the Extended Value Syntax.


All options, e.g. --log-level=debug, are command line arguments that:

  • start with --
  • have a name, in lowercase, using - as word separator in name (e.g. --log-level=debug)
  • have a value, separated from name with a =
  • can be used by prefix, provided that it is unique. E.g. --log-l=debug is the same as --log-level=debug


  • some options accept a short form, e.g. -Ptoto is equivalent to --preset=toto, refer to the manual or -h.
  • some options (flags) don't take a value, e.g. -r
  • the special option -- stops option processing and is ignored, following command line arguments are taken as arguments, including the ones starting with a -. Example:
$ mlia config echo -- --sample

Note that --sample is taken as an argument, and not option.

Options can be optional or mandatory, with or without (hardcoded) default value. Options can be placed anywhere on comand line and evaluated in order.

The value for any options can come from the following locations (in this order, last value evaluated overrides previous value):

Environment variable starting with prefix: MLIA_ are taken as option values, e.g. MLIA_OPTION_NAME is for --option-name.

Options values can be displayed for a given command by providing the --show-config option: mlia node --show-config

Commands and Arguments

Command line arguments that are not options are either commands or arguments. If an argument must begin with -, then either use the @val: syntax (see Extended Values), or use the -- separator (see above).

Interactive Input

Some options and parameters are mandatory and other optional. By default, the tool will ask for missing mandatory options or parameters for interactive execution.

The behaviour can be controlled with:

  • --interactive=<yes|no> (default=yes if STDIN is a terminal, else no)
    • yes : missing mandatory parameters/options are asked to the user
    • no : missing mandatory parameters/options raise an error message
  • --ask-options=<yes|no> (default=no)
    • optional parameters/options are asked to user

Output Format

Command execution will result in output (terminal, stdout/stderr). The information displayed depends on the action. Types of result include:

  • single_object : displayed as a 2 dimensional table: one line per attribute, first column is attribute name, and second is atteribute value. Nested hashes are collapsed.
  • object_list : displayed as a 2 dimensional table: one line per item, one colum per attribute.
  • value_list : a table with one column.
  • empty : nothing
  • status : a message
  • other_struct : a complex structure that cannot be displayed as an array

The table style is :.: by default and can be customized with parameter: table_style (horizontal, vertical and intersection characters).

The style of output can be set using the format parameter, supporting:

  • table : Text table
  • ruby : Ruby code
  • json : JSON code
  • jsonpp : JSON pretty printed
  • yaml : YAML
  • csv : Comma Separated Values

Table output can be filtered using the select parameter. Example:

$ mlia aspera admin res user list --fields=name,email,ats_admin [email protected]:'{"per_page":1000,"page":1,"sort":"name"}' [email protected]:'{"ats_admin":true}'
:             name              :              email               : ats_admin :
: John Custis                   : [email protected]                 : true      :
: Laurent Martin                : [email protected]              : true      :

Note that select filters selected elements from the result of API calls, while the query parameters gives filtering parameters to the API when listing elements.

In a table format, when displaying "objects" (single, or list), by default, sub object are flatten (option flat_hash). So, object "user":{"id":1,"name":"toto"} will have attributes: and Setting flat_hash to "false" will only display one field: "user" and value is the sub hash table. When in flatten mode, it is possible to filter fields by "dotted" field name.

Another option is display, which accepts values: info, data, error. Level info displays all messages (in table mode only). data do not display info messages, error display only error messages.

By default, a table output will display one line per entry, and columns. Depending on the command, columns may include by default all properties, or only some selected properties. It is possible to define specific colums to be displayed, by setting the fields option to one of the following value:

  • DEF : default display of columns (that's the default, when not set)
  • ALL : all columns available
  • a,b,c : the list of attributes specified by the comma separated list
  • Array extended value: for instance, @json:'["a","b","c"]' same as above
  • +a,b,c : add selected properties to the default selection.

Extended Value Syntax

Usually, values of options and arguments are specified by a simple string. But sometime it is convenient to read a value from a file, or decode it, or have a value more complex than a string (e.g. Hash table).

The extended value syntax is:

<0 or more decoders><0 or 1 reader><nothing or some text value>

The difference between reader and decoder is order and ordinality. Both act like a function of value on right hand side. Decoders are at the beginning of the value, followed by a single optional reader, followed by the optional value.

The following "readers" are supported:

  • @val:VALUE , prevent further special prefix processing, e.g. [email protected]:laurent sets the option username to value laurent.
  • @file:PATH , read value from a file (prefix "~/" is replaced with the users home folder), e.g. [email protected]:~/.ssh/mykey
  • @path:PATH , performs path expansion (prefix "~/" is replaced with the users home folder), e.g. [email protected]:~/sample_config.yml
  • @env:ENVVAR , read from a named env var, [email protected]:MYPASSVAR
  • @stdin: , read from stdin (no value on right)
  • @preset:NAME , get whole option preset value by name

In addition it is possible to decode a value, using one or multiple decoders :

  • @base64: decode a base64 encoded string
  • @json: decode JSON values (convenient to provide complex structures)
  • @zlib: uncompress data
  • @ruby: execute ruby code
  • @csvt: decode a titled CSV value
  • @lines: split a string in multiple lines and return an array
  • @list: split a string in multiple items taking first character as separator and return an array
  • @incps: include values of presets specified by key include_presets in hash

To display the result of an extended value, use the config echo command.

Example: read the content of the specified file, then, base64 decode, then unzip:

$ mlia config echo @zlib:@base64:@file:myfile.dat

Example: create a value as a hash, with one key and the value is read from a file:

$ mlia config echo @ruby:'{"token_verification_key"=>"pubkey.txt")}' 

Example: read a csv file and create a list of hash for bulk provisioning:

$ cat test.csv 
lolo,[email protected]
toto,[email protected]
$ mlia config echo @csvt:@file:test.csv
: name :        email        :
: lolo : [email protected] :
: toto : [email protected]      :

Example: create a hash and include values from preset named "config" of config file

$ mlia config echo @incps:@json:'{"hello":true,"incps":["config"]}'
{"version"=>"0.9", "hello"=>true}

Note that @incps:@json:'{"incps":["config"]}' or @incps:@ruby:'{"incps"=>["config"]}' is equivalent to: @preset:config

Structured Value

Some options and parameters expect a Structured Value, i.e. a value more complex than a simple string. This is usually a Hash table or an Array, which could also contain sub structures.

For instance, a transfer-spec is expected to be a Structured Value.

Structured values shall be described using the Extended Value Syntax. A convenient way to specify a Structured Value is to use the @json: decoder, and describe the value in JSON format. The @ruby: decoder can also be used. For an array of hash tables, the @csvt: decoder can be used.

It is also possible to provide a Structured Value in a file using @json:@file:<path>

Configuration and Persistency Folder

mlia configuration and other runtime files (token cache, file lists, persistency files) are stored in folder $HOME/.aspera/mlia. The folder can be displayed using :

$ mlia config folder

Configuration file

On the first execution of mlia, an empty configuration file is created in the configuration folder. Nevertheless, there is no mandatory information required in this file, the use of it is optional as any option can be provided on the command line.

Although the file is a standard YAML file, mlia provides commands to read and modify it using the config command.

All options for mlia commands can be set on command line, or by env vars, or using option presets in the configuratin file.

A configuration file provides a way to define default values, especially for authentication parameters, thus avoiding to always having to specify those parameters on the command line.

The default configuration file is: $HOME/.aspera/mlia/config.yaml (this can be overriden with option --config-file=path or equivalent env var).

So, finally, the configuration file is simply a catalog of pre-defined lists of options, called: option presets. Then, instead of specifying some common options on the command line (e.g. address, credentials), it is possible to invoke the ones of a option preset (e.g. mypreset) using the option: -Pmypreset or --preset=mypreset.

Option preset

A option preset is simply a collection of parameters and their associated values in a named section in the configuration file.

A named option preset can be modified directly using mlia, which will update the configuration file :

$ mlia config id <option preset> set|delete|show|initialize|update

The command update allows the easy creation of option preset by simply providing the options in their command line format, e.g. :

$ mlia config id demo_server update --url=ssh:// --username=asperaweb --password=demoaspera [email protected]:'{"precalculate_job_size":true}'
  • This creates a option preset demo_server with all provided options.

The command set allows setting individual options in a option preset.

$ mlia config id demo_server set password demoaspera

The command initialize, like update allows to set several parameters at once, but it deletes an existing configuration instead of updating it, and expects a Structured Value.

$ mlia config id demo_server initialize @json:'{"url":"ssh://","username":"asperaweb","password":"demoaspera","ts":{"precalculate_job_size":true}}'

A good practice is to not manually edit the configuration file and use modification commands instead. If necessary, the configuration file can be edited (or simply consulted) with:

$ mlia config open

A full terminal based overview of the configuration can be displayed using:

$ mlia config over

A list of option preset can be displayed using:

$ mlia config list

Special Option preset: config

This preset name is reserved and contains a single key: version. This is the version of Amelia which created the file.

Special Option preset: default

This preset name is reserved and contains an array of key-value , where the key is the name of a plugin, and the value is the name of another preset.

When a plugin is invoked, the preset associated with the name of the plugin is loaded, unless the option --no-default (or -N) is used.

Note that special plugin name: config can be associated with a preset that is loaded initially, typically used for default values.

Operations on this preset are done using regular config operations:

$ mlia config id default set _plugin_name_ _defauklt_preset_for_plugin_
$ mlia config id default get _plugin_name_

Format of file

The configuration file is a hash in a YAML file. Example:

  version: 0.3.7
  config: cli_default
  server: demo_server
  interactive: no
  url: ssh://
  username: asperaweb
  password: demoaspera

We can see here:

  • The configuration was created with CLI version 0.3.7
  • the default option preset to load for plugin "server" is : demo_server
  • the option preset demo_server defines some parameters: the URL and credentials
  • the default option preset to load in any case is : cli_default

Two option presets are reserved:

  • config contains a single value: version showing the CLI version used to create the configuration file. It is used to check compatibility.
  • default is reserved to define the default option preset name used for known plugins.

The user may create as many option presets as needed. For instance, a particular option preset can be created for a particular application instance and contain URL and credentials.

Values in the configuration also follow the Extended Value Syntax.

Note: if the user wants to use the Extended Value Syntax inside the configuration file, using the config id update command, the user shall use the @val: prefix. Example:

$ mlia config id my_aoc_org set private_key @val:@file:"$HOME/.aspera/mlia/aocapikey"

This creates the option preset:

  private_key: @file:"/Users/laurent/.aspera/mlia/aocapikey"

So, the key file will be read only at execution time, but not be embedded in the configuration file.

Options are loaded using this algorithm:

  • if option '--preset=xxxx' is specified (or -Pxxxx), this reads the option preset specified from the configuration file.
    • else if option --no-default (or -N) is specified, then dont load default
    • else it looks for the name of the default option preset in section "default" and loads it
  • environment variables are evaluated
  • command line options are evaluated

Parameters are evaluated in the order of command line.

To avoid loading the default option preset for a plugin, just specify a non existing configuration: -Pnone

On command line, words in parameter names are separated by a dash, in configuration file, separator is an underscore. E.g. --xxx-yyy on command line gives xxx_yyy in configuration file.

Note: before version 0.4.5, some keys could be ruby symbols, from 0.4.5 all keys are strings. To convert olver versions, remove the leading ":" in front of keys.

The main plugin name is config, so it is possible to define a default option preset for the main plugin with:

$ mlia config id cli_default set interactive no
$ mlia config id default set config cli_default

A option preset value can be removed with unset:

$ mlia config id cli_default unset interactive


For Faspex, Shares, Node (including ATS, Aspera Transfer Service), Console, only username/password and url are required (either on command line, or from config file). Those can usually be provided on the command line:

$ mlia shares repo browse / --url= --username=john --password=4sp3ra 

This can also be provisioned in a config file:

1$ mlia config id shares06 set url
2$ mlia config id shares06 set username john
3$ mlia config id shares06 set password 4sp3ra
4$ mlia config id default set shares shares06 
5$ mlia config overview
6$ mlia shares repo browse /

The three first commands build a option preset. Note that this can also be done with one single command:

$ mlia config id shares06 init @json:'{"url":"","username":"john","password":"4sp3ra"}'

The fourth command defines this option preset as the default option preset for the specified application ("shares"). The 5th command displays the content of configuration file in table format. Alternative option presets can be used with option "-P<option preset>" (or --preset=<option preset>)

Eventually, the last command shows a call to the shares application using default parameters.


The CLI tool uses a plugin mechanism. The first level command (just after mlia on the command line) is the name of the concerned plugin which will execute the command. Each plugin usually represent commands sent to a specific application. For instance, the plugin "faspex" allows operations on the application "Aspera Faspex".

Create your own plugin

$ mkdir -p ~/.aspera/mlia/plugins
$ cat<<EOF>~/.aspera/mlia/plugins/test.rb
require 'asperalm/cli/plugin'
module Asperalm
  module Cli
    module Plugins
      class Test < Plugin
        def execute_action; puts "Hello World!"; end
      end # Test
    end # Plugins
  end # Cli
end # Asperalm


The gem is equipped with traces. By default logging level is "warn". To increase debug level, use parameter log_level, so either command line --log-level=xx or env var MLIA_LOG_LEVEL.

Learning Aspera Product APIs (REST)

This CLI uses REST APIs. To display HTTP calls, use argument -r or --rest-debug, this is useful to display exact content or HTTP requests and responses.

In order to get traces of execution, use argument : --log-level=debug

Graphical Interactions: Browser and Text Editor

Some actions may require the use of a graphical tool:

  • a browser for Aspera on Cloud authentication (web auth method)
  • a text editor for configuration file edition

By default the CLI will assume that a graphical environment is available on windows, and on other systems, rely on the presence of the "DISPLAY" environment variable. It is also possible to force the graphical mode with option --ui :

  • --ui=graphical forces a graphical environment, a browser will be opened for URLs or a text editor for file edition.
  • --ui=text forces a text environment, the URL or file path to open is displayed on terminal.

HTTP proxy for REST

To specify a HTTP proxy, set the HTTP_PROXY environment variable (or HTTPS_PROXY), those are honoured by Ruby when calling REST APIs.

Proxy auto config (BETA)

BETA: The fpac option allows specification of a Proxy Auto Configuration (PAC) file, by its URL for local FASP agent. Supported schemes are : http:, https: and file:.

The PAC file can be tested with command: config proxy_check , example:

$ mlia config proxy_check --fpac=file:///./proxy.pac

This is not yet implemented to specify proxy, so use env vars.

FASP configuration

The config plugin also allows specification for the use of a local FASP client. It provides the following commands for ascp subcommand:

  • show : shows the path of ascp used
  • use : list,download connect client versions available on internet
  • products : list Aspera transfer products available locally
  • connect : list,download connect client versions available on internet

Show path of currently used ascp

$ mlia config ascp show

Selection of local ascp

To temporarily use an alternate ascp path use option ascp_path (--ascp-path=)

To permanently use another ascp:

$ mlia config ascp use '/Users/laurent/Applications/Aspera CLI/bin/ascp'
saved to default global preset /Users/laurent/Applications/Aspera CLI/bin/ascp

This sets up a global default.

List locally installed Aspera Transfer products

Locally installed Aspera products can be listed with:

$ mlia config ascp products list
:                  name                   :                    app_root                    :
: Aspera Connect                          : /Users/laurent/Applications/Aspera :
: IBM Aspera CLI                          : /Users/laurent/Applications/Aspera CLI         :
: IBM Aspera High-Speed Transfer Endpoint : /Library/Aspera                                :
: Aspera Drive                            : /Applications/Aspera                 :

Selection of local client

If no ascp is selected, this is equivalent to using option: --use-product=FIRST.

Using the option use_product finds the ascp binary of the selected product.

To permanently use the ascp of a product:

$ mlia config ascp products use 'Aspera Connect'
saved to default global preset /Users/laurent/Applications/Aspera

Installation of Connect Client on command line

$ mlia config ascp connect list
:                      id                       :                title                 :   version    :
: urn:uuid:589F9EE5-0489-4F73-9982-A612FAC70C4E : Aspera Connect for Windows           : :
: urn:uuid:A3820D20-083E-11E2-892E-0800200C9A66 : Aspera Connect for Windows 64-bit    : :
: urn:uuid:589F9EE5-0489-4F73-9982-A612FAC70C4E : Aspera Connect for Windows XP        : :
: urn:uuid:55425020-083E-11E2-892E-0800200C9A66 : Aspera Connect for Windows XP 64-bit : :
: urn:uuid:D8629AD2-6898-4811-A46F-2AF386531BFF : Aspera Connect for Mac Intel 10.6    : :
: urn:uuid:D8629AD2-6898-4811-A46F-2AF386531BFF : Aspera Connect for Mac Intel         : :
: urn:uuid:213C9370-22B1-11E2-81C1-0800200C9A66 : Aspera Connect for Linux 32          : :
: urn:uuid:97F94DF0-22B1-11E2-81C1-0800200C9A66 : Aspera Connect for Linux 64          : :
$ mlia config ascp connect id 'Aspera Connect for Mac Intel 10.6' links list
:                    title                    :           type           :                                 href                                  : hreflang :      rel      :
: Mac Intel Installer                         : application/octet-stream : bin/AsperaConnect-                     : en       : enclosure     :
: Aspera Connect for Mac HTML Documentation   : text/html                :                                                                       : en       : documentation :
: Aspera Connect PDF Documentation for Mac OS : application/pdf          : docs/user/osx/ja-jp/pdf/Connect_User_3.7.0_OSX_ja-jp.pdf              : ja-jp    : documentation :
: Aspera Connect PDF Documentation for Mac OS : application/pdf          : docs/user/osx/en/pdf/Connect_User_3.7.0_OSX.pdf                       : en       : documentation :
: Aspera Connect PDF Documentation for Mac OS : application/pdf          : docs/user/osx/es-es/pdf/Connect_User_3.7.0_OSX_es-es.pdf              : es-es    : documentation :
: Aspera Connect PDF Documentation for Mac OS : application/pdf          : docs/user/osx/fr-fr/pdf/Connect_User_3.7.0_OSX_fr-fr.pdf              : fr-fr    : documentation :
: Aspera Connect PDF Documentation for Mac OS : application/pdf          : docs/user/osx/zh-cn/pdf/Connect_User_3.7.0_OSX_zh-cn.pdf              : zh-cn    : documentation :
: Aspera Connect for Mac Release Notes        : text/html                : : en       : release-notes :
$ mlia config ascp connect id 'Aspera Connect for Mac Intel 10.6' links id 'Mac Intel Installer' download --to-folder=.
downloaded: AsperaConnect-

Transfer Agents

Some of the actions on Aspera Applications lead to file transfers (upload and download) using the FASP protocol (ascp).

When a transfer needs to be started, a transfer-spec has been internally prepared. This transfer-spec will be executed by a transfer client, here called "Transfer Agent".

There are currently 3 agents:

  • direct : a local execution of ascp
  • connect : use of a local Connect Client
  • node : use of an Aspera Transfer Node (potentially remote).
  • httpgw : use of an Aspera HTTP Gateway

Note that all transfer operation are seen from the point of view of the agent. For instance, a node agent making an "upload", or "package send" operation, will effectively push files to the related server from the agent node.

mlia standadizes on the use of a transfer-spec instead of raw ascp options to provide parameters for a transfer session, as a common method for those three Transfer Agents.

Direct (local ascp using FASPManager API)

By default the CLI will use a local FASP protocol, equivalent to specifying --transfer=direct. mlia will detect locally installed Aspera products. Refer to section FASP.

To specify a FASP proxy (only supported with the direct agent), set the appropriate transfer-spec parameter:

  • EX_fasp_proxy_url
  • EX_http_proxy_url (proxy for legacy http fallback)
  • EX_ascp_args

The transfer-info optionally provides the following auto resume parameters:

  • iter_max (7)
  • sleep_initial (2)
  • sleep_factor (2)
  • sleep_max (60)

This defines the resume algorithm.

IBM Aspera Connect Client GUI

By specifying option: --transfer=connect, mlia will start transfers using the locally installed Aspera Connect Client.

Aspera Node API : Node to node transfers

By specifying option: --transfer=node, the CLI will start transfers in an Aspera Transfer Server using the Node API, either on a local or remote node.

If a default node has been configured in the configuration file, then this node is used by default else the parameter --transfer-info is required. The node specification shall be a hash table with three keys: url, username and password, corresponding to the URL of the node API and associated credentials (node user or access key).

The --transfer-info parameter can directly specify a pre-configured option preset : [email protected]:<psetname> or specified using the option syntax : [email protected]:'{"url":"https://...","username":"theuser","password":"thepass"}'

Aspera on cloud

By specifying option: --transfer=aoc, WORK IN PROGRESS

HTTP Gateway

If it possible to send using a HTTP gateway, in case FASP is not allowed.


mlia faspex package recv --id=323 --transfer=httpgw [email protected]:'{"url":""}'

Transfer Specification

Some commands lead to file transfer (upload/download), all parameters necessary for this transfer is described in a transfer-spec (Transfer Specification), such as:

  • server address
  • transfer user name
  • credentials
  • file list
  • etc...

mlia builds a default transfer-spec internally, so it is not necessary to provide additional parameters on the command line for this transfer.

If needed, it is possible to modify or add any of the supported transfer-spec parameter using the ts option. The ts option accepts a Structured Value containing one or several transfer-spec parameters.

It is possible to specify ascp options when the transfer option is set to direct using the special transfer-spec parameter: EX_ascp_args. Example: [email protected]:'{"EX_ascp_args":["-l","100m"]}'. This is espacially useful for ascp command line parameters not supported yet in the transfer spec.

The use of a transfer-spec instead of ascp parameters has the advantage of:

  • common to all Transfer Agent
  • not dependent on command line limitations (special characters...)

A transfer-spec is a Hash table, so it is described on the command line with the Extended Value Syntax.

Transfer Parameters

All standard transfer-spec parameters can be overloaded. To display parameters, run in debug mode (--log-level=debug). transfer-spec can also be saved/overridden in the config file.


  • F=Fasp Manager(local FASP execution)
  • N=remote node(node API)
  • C=Connect Client(web plugin)

Req/Def : Required or default value (- means emty)

Fields with EX_ prefix are specific extensions to local mode.

arg: related ascp argument or env var suffix (PASS for ASPERA_SCP_PASS)

Documentation→Node API→/opt/transfers

directionRequiredstringYYY--modeDirection: "send" or "receive"
remote_hostRequiredstringYYY--hostIP or fully qualified domain name of the remote server
remote_userRequiredstringYYY--userRemote user. Default value is "xfer" on node or connect.
destination_rootRequiredstringYYYlast argDestination root directory.
title-stringNYY-Title of the transfer
Metadata for transfer
Authorization token: Bearer, Basic or ATM
cookie-stringYYYCOOKIEMetadata for transfer (older,string)
remote_access_keyTODOstring?Node only?
Source root directory.(TODO: verify option)
fasp_port33001integerYYY-OSpecifies fasp (UDP) port.
ssh_port22 or 33001integerYYY-PSpecifies ssh (TCP) port.
rate_policyserver configstringYYY--policyValid literals include "low","fair","high" and "fixed".
symlink_policyfollowstringYYY--symbolic-linkscopy, follow, copy+force, skip. Default is follow. Handle source side symbolic links by following the link (follow), copying the link itself (copy), skipping (skip), or forcibly copying the link itself (copy+force).
target_rate_kbps-integerYYY-lSpecifies desired speed for the transfer.
min_rate_kbps0integerYYY-mSet the minimum transfer rate in kilobits per second.
ciphernonestringYYY-cin transit encryption type.
none, aes-128, aes-256
string--file-crypt=encryption at rest
content_protection_password-stringPASSSpecifies a string password.
overwritediffstringYYY--overwriteOverwrite destination files with the source files of the same name.
never, always, diff, older, or diff+older
retry_durationstringTODOSpecifies how long to wait before retrying transfer. (e.g. "5min")
http_fallbackbool (node), integer-y
When true(1), attempts to perform an HTTP transfer if a fasp transfer cannot be performed.
create_dirbooleanYYY-dSpecifies whether to create new directories.
precalculate_job_sizesrv. def.booleanYYY--precalculate-job-sizeSpecifies whether to precalculate the job size.
remove_after_transferbooleanY?Specifies whether to remove file after transfer.
remove_empty_directoriesbooleanY?Specifies whether to remove empty directories.
multi_session1integerNYN-CSpecifies how many parts the transfer is in.
multi_session_thresholdnullintegerNYN-in bytes
dgram_sizeintegerY-Zin bytes
compressionintegerascp4 only, 0 / 1?
read_threadsinteger-ascp4 only
write_threadsinteger-ascp4 only
use_ascp4falsebooleanY-specify version of protocol
pathssource files (dest)arraypositional
Contains a path to the source (required) and a path to the destination.
http_fallback_portintegerY-tSpecifies http port.
https_fallback_portintegertodoSpecifies https port.
cipher_allowedstring-returned by node API. Valid literals include "aes-128" and "none".
target_rate_cap_kbpsN??-Returned by upload/download_setup node api.
rate_policy_allowed-returned by node API. Specifies most aggressive rate policy that is allowed. Valid literals include "low", "fair","high" and "fixed".
ssh_private_key-stringYNNKEYPrivate key used for SSH authentication, Shall look like: `-----BEGIN RSA PRIVATE KEY-----\nMII`
Note the JSON encoding `\` + `n` for newlines.
remote_password-stringYYYPASSSSH session password
authentication-NNY-token: Aspera web keys are provided to allow transparent web based session initiation. on connect: password is not asked. Else, password is asked, and keys are not provided.
EX_ssh_key_paths-arrayYNN-iUse public key authentication and specify the private key file
EX_at_rest_password-stringYNNFILEPASSPassphrase used for at rest encryption or decryption
EX_fasp_proxy_url-stringYNN--proxySpecify the address of the Aspera high-speed proxy server
EX_http_proxy_url-stringYNN-xSpecify the proxy server address used by HTTP Fallback
EX_ascp_args-arrayYNNsameAdd command line arguments to ascp
EX_http_transfer_jpeg0integerYNN-jHTTP transfers as JPEG file
EX_license_text-stringYNNLICENSElicense file text
EX_file_list-stringYNN--file-listsource file list
EX_file_pair_list-stringYNN--file-pair-listsource file pair list
EX_multi_session_part-stringYNN-Cpart for multisession
EX_no_read--YNN--no-readno read source
EX_no_write--YNN--no-writeno write estination

Destination folder for transfers

The destination folder is set by mlia by default to:

  • . for downloads
  • / for uploads

It is specified by the transfer-spec parameter destination_root. As such, it can be modified with option: [email protected]:'{"destination_root":"<path>"}'. The option to_folder provides an equivalent and convenient way to change this parameter: --to-folder=<path> .

List of files for transfers

When uploading, downloading or sending files, the user must specify the list of files to transfer. Most of the time, the list of files to transfer will be simply specified on the command line:

$ mlia -Pdemoserver server upload ~/mysample.file secondfile

This is the same as:

$ mlia -Pdemoserver server upload [email protected] ~/mysample.file secondfile

More advanced options are provided to adapt to various cases. In fact, list of files to transfer are conveyed using the transfer-spec using the field: "paths" which is a list (array) of pairs of "source" (mandatory) and "destination" (optional).

Note that this is different from the "ascp" command line. The paradigm used by mlia is: all transfer parameters are kept in transfer-spec so that execution of a transfer is independent of the transfer agent. It is envisioned that, one day, ascp will accept a transfer-spec directly.

For ease of use and flexibility, the list of files to transfer is specified by the option sources. The accepted values are:

  • the literal @args (default value), in that case the list of files is directly provided at the end of the command line (see at the beginning of this section).

  • an Extended Value holding an Array of String. Examples:

[email protected]:'["file1","file2"]'
[email protected]:@stdin:
[email protected]:'"myfilelist").split("\n")'
  • the literal value @ts which specifies that the user provided the list of files directly in the ts option, in its paths field. Example:
[email protected] [email protected]:'{"paths":[{"source":"file1"},{"source":"file2"}]}'
  • Although not recommended, because it applies only to the local transfer agent (i.e. bare ascp), it is possible to specify bare ascp arguments using the pseudo transfer-spec parameter EX_ascp_args. In that case, one must specify a dummy list in the transfer-spec, which will be overriden by the bare ascp command line provided.
[email protected] [email protected]:'{"paths":[{"source":"dummy"}],"EX_ascp_args":["--file-list","myfilelist"]}'

In case the file list is provided on the command line (i.e. using [email protected] or --sources=<Array>, but not [email protected]), the list of files will be used either as a simple file list or a file pair list depending on the value of the option: src_type:

  • list : (default) the path of destination is the same as source
  • pair : in that case, the first element is the first source, the second element is the first destination, and so on.


mlia server upload --src-type=pair ~/Documents/Samples/200KB.1 /Upload/sample1

Note the special case when the source files are located on "Aspera on Cloud", i.e. using access keys and the file id API:

  • All files must be in the same source folder.
  • If there is a single file : specify the full path
  • For multiple files, specify the source folder as first item in the list followed by the list of file names.

Source files are located on "Aspera on cloud", when :

  • the server is Aspera on Cloud, and making a download / recv
  • the agent is Aspera on Cloud, and making an upload / send

Support of multi-session

Multi session, i.e. starting a transfer of a file set using multiple sessions is supported on "direct" and "node" agents, not yet on connect.

  • when agent=node :
[email protected]:'{"multi_session":10,"multi_session_threshold":1}'

Multi-session is directly supported by the node daemon.

  • when agent=direct :
[email protected]:'{"multi_session":5,"multi_session_threshold":1,"resume_policy":"none"}'

Note: resume policy of "attr" may cause problems. "none" or "sparse_csum" shall be preferred.

Multi-session spawn is done by mlia.


  • Change target rate
[email protected]:'{"target_rate_kbps":500000}'
  • Override the FASP SSH port to a specific TCP port:
[email protected]:'{"ssh_port":33002}'
  • Force http fallback mode:
[email protected]:'{"http_fallback":"force"}'
  • Activate progress when not activated by default on server
[email protected]:'{"precalculate_job_size":true}'

Scheduling an exclusive execution

It is possible to ensure that a given command is only run once at a time with parameter: --lock-port=nnnn. This is especially usefull when scheduling a command on a regular basis, for instance involving transfers, and a transfer may last longer than the execution period.

This opens a local TCP server port, and fails if this port is already used, providing a local lock.

This option is used when the tools is executed automatically, for instance with "preview" generation.

Usually the OS native scheduler shall already provide some sort of such protection (windows scheduler has it natively, linux cron can leverage flock).

Sample Commands

A non complete list of commands used in unit tests:

mlia --no-default node --url=my_url_here --username=my_username_here --password=my_password_here --insecure=yes delete /500M.dat
mlia --no-default node --url=my_url_here --username=my_username_here --password=my_password_here --insecure=yes upload --to-folder=CF_HSTS_FOLDER_UPLOAD [email protected] [email protected]:'{"paths":[{"source":"/aspera-test-dir-small/10MB.1"}],"remote_password":"CF_HSTS_SSH_PASS","precalculate_job_size":true}' --transfer=node [email protected]:'{"url":"my_url_here","username":"my_username_here","password":"my_password_here"}' 
mlia --version)
mlia --version` TOOLNAME=EXENAME erb >
mlia --warnings --config-file=MLIA_CONFIG_FILE
mlia -N --url=my_url_here --username=my_username_here --password=my_password_here node acc create [email protected]:'{"id":"aoc_1","secret":"'CF_COMMON_PASS'","storage":{"type":"local","path":"/"}}'
mlia -N --url=my_url_here --username=my_username_here --password=my_password_here node acc delete --id=aoc_1
mlia -N aspera files browse / --link=CF_AOC_PUBLINK_FOLDER
mlia -N aspera files upload --to-folder=/ CF_SAMPLE_FILEPATH --link=CF_AOC_PUBLINK_FOLDER
mlia -N aspera org --link=CF_AOC_PUBLINK_RECV_PACKAGE
mlia -N aspera packages send [email protected]:'{"name":"'"CURRENT_DATE"'"}' CF_SAMPLE_FILEPATH --link=CF_AOC_PUBLINK_SEND_DROPBOX
mlia -N aspera packages send [email protected]:'{"name":"'"CURRENT_DATE"'"}' CF_SAMPLE_FILEPATH --link=CF_AOC_PUBLINK_SEND_USER
mlia -N server --url=my_url_here --username=my_username_here --password=my_password_here --format=nagios nagios transfer --to-folder=CF_HSTS_FOLDER_UPLOAD
mlia -N server --url=my_url_here --username=my_username_here --ssh-keys=~/.ssh/id_rsa --format=nagios nagios app_services
mlia -N server --url=my_url_here --username=my_username_here --ssh-keys=~/.ssh/id_rsa ctl all:status
mlia -N server --url=my_url_here --username=my_username_here --ssh-keys=~/.ssh/id_rsa nodeadmin -- -l
mlia -Pserver_eudemo_key server br /
mlia -h
mlia aspera admin analytics transfers [email protected]:'{"status":"completed","direction":"receive"}'
mlia aspera admin ats access_key --id=akibmcloud --secret=my_secret_here node browse /
mlia aspera admin ats access_key --id=akibmcloud delete
mlia aspera admin ats access_key create --cloud=aws --region=CF_AWS_REGION [email protected]:'{"id":"ak_aws","name":"laurent key AWS","storage":{"type":"aws_s3","bucket":"'CF_AWS_BUCKET'","credentials":{"access_key_id":"my_access_key_id_here","secret_access_key":"my_secret_access_key_here"},"path":"/"}}'
mlia aspera admin ats access_key create --cloud=softlayer --region=CF_ICOS_REGION [email protected]:'{"id":"akibmcloud","secret":"somesecret","name":"laurent key","storage":{"type":"ibm-s3","bucket":"CF_ICOS_BUCKET","credentials":{"access_key_id":"my_access_key_id_here","secret_access_key":"my_secret_access_key_here"},"path":"/"}}'
mlia aspera admin ats access_key list --fields=name,id
mlia aspera admin ats cluster clouds
mlia aspera admin ats cluster list
mlia aspera admin ats cluster show --cloud=aws --region=CF_AWS_REGION 
mlia aspera admin ats cluster show --id=1f412ae7-869a-445c-9c05-02ad16813be2
mlia aspera admin res client --id=CF_AOC1_CLIENT_ID set_pub_key @file:CF_PRIVATE_KEY_FILE
mlia aspera admin res node v3 events --secret=my_secret_here
mlia aspera admin resource node --name=eudemo-sedemo --secret=my_secret_here v3 access_key create [email protected]:'{"id":"testsub1","storage":{"path":"/folder1"}}'
mlia aspera admin resource node --name=eudemo-sedemo --secret=my_secret_here v3 access_key delete --id=testsub1
mlia aspera admin resource node --name=eudemo-sedemo --secret=my_secret_here v3 events
mlia aspera admin resource node --name=eudemo-sedemo --secret=my_secret_here v4 browse /
mlia aspera admin resource node --name=eudemo-sedemo --secret=my_secret_here v4 delete /folder1
mlia aspera admin resource node --name=eudemo-sedemo --secret=my_secret_here v4 mkdir /folder1
mlia aspera admin resource workspace list
mlia aspera admin resource workspace_membership list --fields=ALL [email protected]:'{"page":1,"per_page":50,"embed":"member","inherited":false,"workspace_id":11363,"sort":"name"}'
mlia aspera apiinfo
mlia aspera automation workflow --id=$$WF_ID action create [email protected]:'{"name":"toto"}' | tee
mlia aspera automation workflow create [email protected]:'{"name":"laurent_test"}'
mlia aspera automation workflow delete --id=$$WF_ID
mlia aspera automation workflow list
mlia aspera automation workflow list [email protected]:'{"name":"laurent_test"}' --fields=id --format=csv > [email protected]
mlia aspera automation workflow list [email protected]:'{"show_org_workflows":"true"}' --scope=admin:all
mlia aspera bearer_token --display=data --scope=user:all
mlia aspera faspex
mlia aspera files bearer /
mlia aspera files browse /
mlia aspera files delete /newname
mlia aspera files download --transfer=connect /200KB.1
mlia aspera files file 18891
mlia aspera files find / --value='\.partial$$'
mlia aspera files http_node_download --to-folder=LOCAL_FOLDER /200KB.1
mlia aspera files mkdir /testfolder
mlia aspera files rename /testfolder newname
mlia aspera files short_link create --to-folder='my folder' --value=private
mlia aspera files short_link create --to-folder='my folder' --value=public
mlia aspera files short_link list [email protected]:'{"purpose":"shared_folder_auth_link"}'
mlia aspera files transfer --workspace=eudemo --from-folder='/Demo Files/aspera-test-dir-tiny' --to-folder=unit_test 200KB.1
mlia aspera files upload --to-folder=/ CF_SAMPLE_FILEPATH
mlia aspera files v3 info
mlia aspera organization
mlia aspera packages list
mlia aspera packages list --format=csv --fields=id|head -n 1)
mlia aspera packages recv --id=ALL --once-only=yes --lock-port=12345
mlia aspera packages send [email protected]:'{"name":"'"CURRENT_DATE"'","recipients":["[email protected]"],"note":"my note"}' CF_SAMPLE_FILEPATH
mlia aspera packages send [email protected]:'{"name":"'"CURRENT_DATE"'","recipients":["[email protected]"]}' [email protected]:'{"package_contact":true}' CF_SAMPLE_FILEPATH
mlia aspera user info modify @json:'{"name":"dummy change"}'
mlia aspera user info show
mlia aspera workspace
mlia ats access_key --id=ak_aws delete
mlia ats access_key --id=akibmcloud --secret=my_secret_here cluster
mlia ats access_key --id=akibmcloud --secret=my_secret_here node browse /
mlia ats access_key --id=akibmcloud delete
mlia ats access_key create --cloud=aws --region=CF_AWS_REGION [email protected]:'{"id":"ak_aws","name":"laurent key AWS","storage":{"type":"aws_s3","bucket":"'CF_AWS_BUCKET'","credentials":{"access_key_id":"my_access_key_id_here","secret_access_key":"my_secret_access_key_here"},"path":"/"}}'
mlia ats access_key create --cloud=softlayer --region=CF_ICOS_REGION [email protected]:'{"id":"akibmcloud","secret":"somesecret","name":"laurent key","storage":{"type":"ibm-s3","bucket":"CF_ICOS_BUCKET","credentials":{"access_key_id":"my_access_key_id_here","secret_access_key":"my_secret_access_key_here"},"path":"/"}}'
mlia ats access_key list --fields=name,id
mlia ats api_key create
mlia ats api_key instances
mlia ats api_key list
mlia ats cluster clouds
mlia ats cluster list
mlia ats cluster show --cloud=aws --region=CF_AWS_REGION 
mlia ats cluster show --id=1f412ae7-869a-445c-9c05-02ad16813be2
mlia conf flush
mlia conf wiz --url=my_url_here --config-file=SAMPLE_CONFIG_FILE --client-id=HIDE_CLIENT_ID --client-secret=HIDE_CLIENT_SECRET --pkeypath='' --use-generic-client=no --username=my_username_here
mlia conf wiz --url=my_url_here --config-file=SAMPLE_CONFIG_FILE --pkeypath='' --username=my_username_here --test-mode=yes
mlia config ascp connect id 'Aspera Connect for Windows' info
mlia config ascp connect id 'Aspera Connect for Windows' links id 'Windows Installer' download --to-folder=.
mlia config ascp connect id 'Aspera Connect for Windows' links list
mlia config ascp connect list
mlia config ascp products list
mlia config ascp show
mlia config email_test [email protected]
mlia config export
mlia config genkey LOCAL_FOLDER/mykey
mlia config id conf_name delete
mlia config id conf_name initialize @json:'{"p1":"v1","p2":"v2"}'
mlia config id conf_name set param value
mlia config id conf_name show
mlia config id conf_name update --p1=v1 --p2=v2
mlia config id default set shares conf_name
mlia config list
mlia config open
mlia config overview
mlia config plugins
mlia config proxy_check --fpac=file:///./examples/proxy.pac
mlia console transfer current list 
mlia console transfer smart list 
mlia console transfer smart sub 112 @json:'{"source":{"paths":["10MB.1"]},"source_type":"user_selected"}'
mlia cos node [email protected]:@file:CF_ICOS_CREDS_FILE --region=CF_ICOS_REGION --bucket=CF_ICOS_BUCKET access_key --id=self show
mlia cos node [email protected]:@file:CF_ICOS_CREDS_FILE --region=CF_ICOS_REGION --bucket=CF_ICOS_BUCKET download CF_SAMPLE_FILENAME
mlia cos node [email protected]:@file:CF_ICOS_CREDS_FILE --region=CF_ICOS_REGION --bucket=CF_ICOS_BUCKET info
mlia cos node [email protected]:@file:CF_ICOS_CREDS_FILE --region=CF_ICOS_REGION --bucket=CF_ICOS_BUCKET upload CF_SAMPLE_FILEPATH
mlia faspex nagios_check
mlia faspex package list
mlia faspex package list --fields=package_id --format=csv --box=sent|tail -n 1)
mlia faspex package list --fields=package_id --format=csv|tail -n 1)
mlia faspex package recv --link='CF_FASPEX_PUBLINK_RECV_PACKAGE'
mlia faspex package recv --to-folder=LOCAL_FOLDER --id=ALL --once-only=yes
mlia faspex package send [email protected]:'{"title":"'"CURRENT_DATE"'","recipients":["[email protected]"]}' CF_SAMPLE_FILEPATH
mlia faspex package send --link='CF_FASPEX_PUBLINK_SEND_DROPBOX' [email protected]:'{"title":"'"CURRENT_DATE"'"}' CF_SAMPLE_FILEPATH
mlia faspex package send --link='CF_FASPEX_PUBLINK_SEND_TO_USER' [email protected]:'{"title":"'"CURRENT_DATE"'"}' CF_SAMPLE_FILEPATH
mlia faspex source name "Server Files" node br /
mlia faspex5 node list [email protected]:'{"type":"received","subtype":"mypackages"}'
mlia faspex5 package list [email protected]:'{"state":["released"]}'
mlia faspex5 package receive --id=$$LAST_PACK
mlia faspex5 package send [email protected]:'{"title":"test title","recipients":["admin"]}' CF_SAMPLE_FILEPATH
mlia node async --id=1 bandwidth 
mlia node async --id=1 counters 
mlia node async --id=1 files 
mlia node async list
mlia node async show --id=1
mlia node async show --id=ALL
mlia node basic_token
mlia node browse / -r
mlia node info
mlia node nagios_check
mlia node search / [email protected]:'{"sort":"mtime"}'
mlia node service --id=service1 delete
mlia node service create @json:'{"id":"service1","type":"WATCHD","run_as":{"user":"user1"}}'
mlia node service list
mlia node transfer list [email protected]:'{"active_only":true}'
mlia node upload --to-folder=CF_HSTS_FOLDER_UPLOAD [email protected]:'{"target_rate_cap_kbps":10000}' CF_SAMPLE_FILEPATH
mlia orchestrator info
mlia orchestrator plugins
mlia orchestrator processes
mlia orchestrator workflow --id=CF_WORKFLOW_ID inputs
mlia orchestrator workflow --id=CF_WORKFLOW_ID start [email protected]:'{"Param":"laurent"}'
mlia orchestrator workflow --id=CF_WORKFLOW_ID start [email protected]:'{"Param":"laurent"}' --result=ResultStep:Complete_status_message
mlia orchestrator workflow --id=CF_WORKFLOW_ID status
mlia orchestrator workflow list
mlia orchestrator workflow status
mlia preview events --once-only=yes --skip-types=office
mlia preview scan --skip-types=office --log-level=info
mlia preview test ~/'Documents/Samples/YıçşöğüİÇŞÖĞÜ.pdf' --log-level=debug png
mlia preview test ~/'Documents/Samples/mxf_video.mxf' --log-level=debug mp4 --video-conversion=clips
mlia preview test ~/'Documents/Samples/mxf_video.mxf' --log-level=debug mp4 --video-conversion=preview
mlia preview test ~/'Documents/Samples/mxf_video.mxf' --log-level=debug mp4 --video-conversion=reencode
mlia preview test ~/Documents/Samples/anatomic-2k/TG18-CH/TG18-CH-2k-01.dcm --log-level=debug png
mlia server browse /
mlia server browse CF_HSTS_FOLDER_UPLOAD/target_hot
mlia server delete CF_HSTS_FOLDER_UPLOAD/target_hot
mlia server delete CF_HSTS_FOLDER_UPLOAD/to.delete
mlia server delete NEW_SERVER_FOLDER
mlia server df
mlia server download NEW_SERVER_FOLDER/CF_SAMPLE_FILENAME --to-folder=CF_HSTS_FOLDER_UPLOAD --transfer=node
mlia server du /
mlia server info
mlia server mkdir CF_HSTS_FOLDER_UPLOAD/target_hot
mlia server mkdir NEW_SERVER_FOLDER --logger=stdout
mlia server mv CF_HSTS_FOLDER_UPLOAD/200KB.2 CF_HSTS_FOLDER_UPLOAD/to.delete
mlia server upload [email protected] [email protected]:'{"paths":[{"source":"CF_SAMPLE_FILEPATH","destination":"NEW_SERVER_FOLDER/othername"}]}'
mlia server upload --src-type=pair [email protected]:'["CF_SAMPLE_FILEPATH","NEW_SERVER_FOLDER/othername"]'
mlia server upload --src-type=pair CF_SAMPLE_FILEPATH NEW_SERVER_FOLDER/othername
mlia server upload --to-folder=CF_HSTS_FOLDER_UPLOAD/target_hot --lock-port=12345 [email protected]:'{"EX_ascp_args":["--remove-after-transfer","--remove-empty-directories","--exclude-newer-than=-8","--src-base","source_hot"]}' source_hot
mlia server upload CF_SAMPLE_FILEPATH --to-folder=NEW_SERVER_FOLDER
mlia shares repository browse /
mlia shares repository delete /CF_SHARES_UPLOAD/CF_SAMPLE_FILENAME
mlia shares repository download --to-folder=LOCAL_FOLDER /CF_SHARES_UPLOAD/CF_SAMPLE_FILENAME
mlia shares repository upload --to-folder=/CF_SHARES_UPLOAD CF_SAMPLE_FILEPATH
mlia shares2 appinfo
mlia shares2 organization list
mlia shares2 project list --organization=Sport
mlia shares2 repository browse /
mlia shares2 userinfo
mlia sync start [email protected]:'{"sessions":[{"name":"test","reset":true,"remote_dir":"/sync_test","local_dir":"contents","host":"CF_HSTS1_ADDR","user":"user1","private_key_path":"/Users/laurent/.ssh/id_rsa"}]}'

...and more


$ mlia -h
    mlia -- a command line tool for Aspera Applications (v0.11.1)


    Use Aspera application to perform operations on command line.
    Documentation and examples:
    execute: mlia conf doc
    or visit:

    To list first level commands, execute: mlia
    Note that commands can be written shortened (provided it is unique).

    Options begin with a '-' (minus), and value is provided on command line.
    Special values are supported beginning with special prefix, like: @base64: @json: @zlib: @ruby: @csvt: @lines: @list: @val: @file: @path: @env: @stdin:.
    Dates format is 'DD-MM-YY HH:MM:SS', or 'now' or '-<num>h'

    Some commands require mandatory arguments, e.g. a path.

OPTIONS: global
        --interactive=ENUM           use interactive input of missing params: yes, no
        --ask-options=ENUM           ask even optional options: yes, no
        --format=ENUM                output format: table, ruby, json, jsonpp, yaml, csv, nagios
        --display=ENUM               output only some information: info, data, error
        --fields=VALUE               comma separated list of fields, or ALL, or DEF
        --select=VALUE               select only some items in lists, extended value: hash (column, value)
        --table-style=VALUE          table display style
        --flat-hash=ENUM             display hash values as additional keys: yes, no
    -h, --help                       Show this message.
        --bash-comp                  generate bash completion for command
        --show-config                Display parameters used for the provided action.
    -r, --rest-debug                 more debug for HTTP calls
    -v, --version                    display version
    -w, --warnings                   check for language warnings
        --ui=ENUM                    method to start browser: text, graphical
        --log-level=ENUM             Log level: warn, debug, info, error, fatal, unknown
        --logger=ENUM                log method: stderr, stdout, syslog
        --lock-port=VALUE            prevent dual execution of a command, e.g. in cron
        --query=VALUE                additional filter for API calls (extended value) (some commands)
        --insecure=ENUM              do not validate HTTPS certificate: yes, no
        --once-only=ENUM             process only new items (some commands): yes, no

COMMAND: config
SUBCOMMANDS: gem_path genkey plugins flush_tokens list overview open echo id documentation wizard export_to_cli detect coffee ascp email_test smtp_settings proxy_check folder file
        --value=VALUE                extended value for create, update, list filter
        --property=VALUE             name of property to set
        --id=VALUE                   resource identifier (modify,delete,show)
        --config-file=VALUE          read parameters from file in YAML format, current=/Users/laurent/.aspera/mlia/config.yaml
        --override=ENUM              override existing value: yes, no
    -N, --no-default                 do not load default configuration for plugin
        --use-generic-client=ENUM    wizard: AoC: use global or org specific jwt client id: yes, no
        --pkeypath=VALUE             path to private key for JWT (wizard)
        --ascp-path=VALUE            path to ascp
        --use-product=VALUE          use ascp from specified product
        --smtp=VALUE                 smtp configuration (extended value: hash)
        --fpac=VALUE                 proxy auto configuration URL
    -P, --presetVALUE                load the named option preset from current config file
        --default=VALUE              set as default configuration for specified plugin
        --secret=VALUE               access key secret for node
        --secrets=VALUE              access key secret for node
        --test-mode=ENUM             skip user validation in wizard mode: yes, no
        --ts=VALUE                   override transfer spec values (Hash, use @json: prefix), current={}
        --local-resume=VALUE         set resume policy (Hash, use @json: prefix), current=
        --to-folder=VALUE            destination folder for downloaded files
        --sources=VALUE              list of source files (see doc)
        --transfer-info=VALUE        additional information for transfer client
        --src-type=ENUM              type of file list: list, pair
        --transfer=ENUM              type of transfer: direct, httpgw, connect, node, aoc

COMMAND: shares
SUBCOMMANDS: repository admin
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password

SUBCOMMANDS: postprocess stream transfer cleanup forward access_key watch_folder service async central asperabrowser basic_token browse upload download api_details nagios_check events space info license mkdir mklink mkfile rename delete search
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password
        --validator=VALUE            identifier of validator (optional for central)
        --asperabrowserurl=VALUE     URL for simple aspera web ui
        --name=VALUE                 sync name
        --token=ENUM                 package box: aspera, basic, auto

COMMAND: orchestrator
SUBCOMMANDS: info workflow plugins processes
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password
        --params=VALUE               parameters hash table, use @json:{"param":"value"}
        --result=VALUE               specify result value as: 'work step:parameter'
        --synchronous=ENUM           work step:parameter expected as result: yes, no

SUBCOMMANDS: subscription
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password

COMMAND: aspera
SUBCOMMANDS: apiinfo bearer_token organization tier_restrictions user workspace packages files gateway admin automation servers
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password

SUBCOMMANDS: cluster access_key api_key aws_trust_policy
        --ibm-api-key=VALUE          IBM API key, see
        --instance=VALUE             ATS instance in ibm cloud
        --ats-key=VALUE              ATS key identifier (ats_xxx)
        --ats-secret=VALUE           ATS key secret
        --params=VALUE               Parameters access key creation (@json:)
        --cloud=VALUE                Cloud provider
        --region=VALUE               Cloud region
        --auth=ENUM                  type of Oauth authentication: body_userpass, header_userpass, web, jwt, url_token, ibm_apikey
        --operation=ENUM             client operation for transfers: push, pull
        --client-id=VALUE            API client identifier in application
        --client-secret=VALUE        API client passcode
        --redirect-uri=VALUE         API client redirect URI
        --private-key=VALUE          RSA private key PEM value for JWT (prefix file path with @val:@file:)
        --workspace=VALUE            name of workspace
        --eid=VALUE                  identifier
        --name=VALUE                 resource name
        --link=VALUE                 public link to shared resource
        --new-user-option=VALUE      new user creation option
        --from-folder=VALUE          share to share source folder
        --scope=VALUE                scope for AoC API calls
        --notify=VALUE               notify users that file was received
        --bulk=ENUM                  bulk operation: yes, no

SUBCOMMANDS: entitlement
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password

COMMAND: xnode
SUBCOMMANDS: postprocess cleanup forward
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password
        --filter-transfer=VALUE      Ruby expression for filter at transfer level (cleanup)
        --filter-file=VALUE          Ruby expression for filter at file level (cleanup)

SUBCOMMANDS: cluster access_key api_key aws_trust_policy
        --ibm-api-key=VALUE          IBM API key, see
        --instance=VALUE             ATS instance in ibm cloud
        --ats-key=VALUE              ATS key identifier (ats_xxx)
        --ats-secret=VALUE           ATS key secret
        --params=VALUE               Parameters access key creation (@json:)
        --cloud=VALUE                Cloud provider
        --region=VALUE               Cloud region

COMMAND: faspex5
SUBCOMMANDS: node package
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password

        --service-credentials=VALUE  IBM Cloud service credentials (Hash)
        --region=VALUE               IBM Cloud Object storage region
        --bucket=VALUE               IBM Cloud Object storage bucket

COMMAND: faspex
SUBCOMMANDS: nagios_check package source me dropbox v4 address_book login_methods
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password
        --link=VALUE                 public link for specific operation
        --delivery-info=VALUE        package delivery information (extended value)
        --source-name=VALUE          create package from remote source (by name)
        --storage=VALUE              Faspex local storage definition
        --box=ENUM                   package box: inbox, sent, archive

COMMAND: shares2
SUBCOMMANDS: repository organization project team share appinfo userinfo admin
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password
        --organization=VALUE         organization
        --project=VALUE              project
        --share=VALUE                share

COMMAND: preview
SUBCOMMANDS: scan events folder check test
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password
        --skip-format=ENUM           skip this preview format (multiple possible): png, mp4
        --folder-reset-cache=ENUM    reset folder cache: no, header, read
        --skip-types=VALUE           skip types in comma separated list
        --previews-folder=VALUE      preview folder in storage root
        --temp-folder=VALUE          path to temp folder
        --skip-folders=VALUE         list of folder to skip
        --iteration-file=VALUE       path to iteration memory file
        --overwrite=ENUM             when to overwrite result file: no, header, read
        --file-access=ENUM           how to read and write files in repository: no, header, read
        --video-conversion=ENUM      method for video preview generation: preview, reencode, clips
        --vid-size=VALUE             preview only: video size
        --vid-offset-seconds=VALUE   preview only: 
        --vid-framecount=VALUE       preview only: 
        --vid-blendframes=VALUE      preview only: 
        --vid-framepause=VALUE       preview only: 
        --vid-fps=VALUE              preview only: 
        --reencode-size=VALUE        reencode only: video size
        --clips-size=VALUE           clips only: video size of clip
        --clips-offset-seconds=VALUE clips only: start time
        --clips-length=VALUE         clips only: length in seconds of each clips
        --clips-count=VALUE          clips only: number of clips
        --thumb-vid-size=VALUE       size of thumbnail of video (ffmpeg scale argument)
        --thumb-vid-fraction=VALUE   fraction of video where to take snapshot for thumbnail
        --thumb-img-size=VALUE       height of thumbnail of non video
        --validate-mime=ENUM         produce warning if mime type of node api is different than file analysis: yes, no
        --check-extension=ENUM       check additional extension that are not supported by node api: yes, no
        --max-size=VALUE             maximum size of preview file

SUBCOMMANDS: start admin
        --parameters=VALUE           extended value for session set definition
        --session-name=VALUE         name of session to use for admin commands, by default first one
/Users/laurent/workspace/Rubytools/asperalm/lib/asperalm/ssh.rb:5: warning: method redefined; discarding old default_keys
/usr/local/lib/ruby/gems/2.7.0/gems/net-ssh-6.1.0/lib/net/ssh/authentication/session.rb:139: warning: previous definition of default_keys was here

COMMAND: server
SUBCOMMANDS: nagios nodeadmin userdata configurator ctl download upload browse delete rename ls rm mv du info mkdir cp df md5sum
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password
        --ssh-keys=VALUE             ssh key path list (Array or single)
        --ssh-options=VALUE          ssh options (Hash)
        --cmd-prefix=VALUE           prefix to add for as cmd execution, e.g. sudo or /opt/aspera/bin 

COMMAND: console
SUBCOMMANDS: transfer nagios_check
        --url=VALUE                  URL of application, e.g.
        --username=VALUE             username to log in
        --password=VALUE             user's password
        --filter-from=DATE           only after date
        --filter-to=DATE             only before date

Note that actions and parameter values can be written in short form.

Application Plugins

mlia comes with several Aspera application plugins.

General: Application URL and Authentication

REST APIs of Aspera legacy applications (Aspera Node, Faspex, Shares, Console, Orchestrator, Server) use simple username/password authentication: HTTP Basic Authentication.

Those are using options:

  • url
  • username
  • password

Those can be provided using command line, parameter set, env var, see section above.

Aspera on Cloud relies on Oauth, refer to the Aspera on Cloud section.

Aspera on Cloud

Aspera on Cloud uses the more advanced Oauth mechanism for authentication (HTTP Basic authentication is not supported). This requires additional setup.

Configuration Wizard

mlia provides a configuration wizard. Here is a sample invocation :

$ mlia config wizard
option: url>
Detected: Aspera on Cloud
Preparing preset: aoc_myorg
Please provide path to your private RSA key, or empty to generate one:
option: pkeypath> 
using existing key:
Using global client_id.
option: username> [email protected]
Updating profile with new key
creating new config preset: aoc_myorg
Setting config preset as default for aspera
saving config file
You can test with:
mlia aspera user info show

Optionally, it is possible to create a new organization-specific "integration". For this, specify the option: --use-generic-client=no.

This will guide you through the steps to create

Configuration details

Several types of OAuth authentication are supported:

  • Web based authentication : authentication is made by user using a browser (simpler)
  • JSON Web Token (JWT) : authentication is secured by a private key (recommended)
  • URL Token : external users authentication with url tokens (external links)

The authentication method is controled by option auth.

For a quick start, follow the mandatory and sufficient section: API Client Registration (auth=web) as well as option preset for Aspera on Cloud.

For a more convenient, browser-less, experience follow the JWT section (auth=jwt) in addition to Client Registration.

In Oauth, a "Bearer" token are generated to authenticate REST calls. Bearer tokens are valid for a period of time.mlia saves generated tokens in its configuration folder, tries to re-use them or regenerates them when they have expired.

API Client Registration

The first step is to declare mlia in Aspera on Cloud using the admin interface.

(official documentation: ).

Let's start by a registration with web based authentication (auth=web):

  • Open a web browser, log to your instance: e.g.
  • Go to Apps→Admin→Organization→Integrations
  • Click "Create New"
    • Client Name: mlia
    • Redirect URIs: http://localhost:12345
    • Origins: localhost
    • uncheck "Prompt users to allow client to access"
    • leave the JWT part for now
  • Save

Note: for web based authentication, mlia listens on a local port (e.g. specified by the redirect_uri, in this example: 12345), and the browser will provide the OAuth code there. For `mlia, HTTP is required, and 12345 is the default port.

Once the client is registered, a "Client ID" and "Secret" are created, these values will be used in the next step.

option preset for Aspera on Cloud

It is convenient to save several of those parameters in an option preset for mlia in its configuration file. Lets create an option preset called: my_aoc_org using ask interactive input (client info from previous step):

$ mlia config id my_aoc_org ask url client_id client_secret
option: url>
option: client_id> BJLPObQiFw
option: client_secret> yFS1mu-crbKuQhGFtfhYuoRW...
updated: my_aoc_org

(This can also be done in one line using the command config id my_aoc_org update --url=...)

Define this option preset as default configuration for the aspera plugin:

$ mlia config id default set aspera my_aoc_org

Note: Default auth method is web and default redirect_uri is http://localhost:12345. Leave those default values.

First Use

Once client has been registered and option preset created: mlia can be used:

$ mlia aspera files br /
Current Workspace: Default Workspace (default)

Note that it requires a web based authentication. Refer to section Graphical Interactions to customize the way browser is started.

For direct browser-less authentication, follow the JWT section.

Activation of JSON Web Token (JWT) for direct authentication

In addition to basic API Client registration, the following steps are required for a Browser-less, Private Key-based authentication.

Key Pair Generation

In order to use JWT for Aspera on Cloud API client authentication, a private/public key pair must be generated (without passphrase) This can be done using any of the following method:

(TODO: add passphrase protection as option).

  • using the CLI:
$ mlia config genkey ~/.aspera/mlia/aocapikey
  • ssh-keygen:
$ ssh-keygen -t rsa -f ~/.aspera/mlia/aocapikey -N ''
  • openssl

(on some openssl implementation (mac) there is option: -nodes (no DES))

$ APIKEY=~/.aspera/mlia/aocapikey
$ openssl genrsa -passout pass:dummypassword -out ${APIKEY}.protected 2048
$ openssl rsa -passin pass:dummypassword -in ${APIKEY}.protected -out ${APIKEY}
$ openssl rsa -pubout -in ${APIKEY} -out ${APIKEY}.pub
$ rm -f ${APIKEY}.protected

API Client JWT activation

JWT needs to be authorized in Aspera on Cloud. This can be done in two manners:

  • Open a web browser, log to your instance:
  • Go to Apps→Admin→Organization→Integrations
  • Click on the previously created application
  • select tab : "JSON Web Token Auth"
  • Modify options if necessary, for instance: activate both options in section "Settings"
  • Click "Save"
Using command line
$ mlia aspera admin res client list
:     id     :  name   :
: BJLPObQiFw : mlia :
$ mlia aspera admin res client --id=BJLPObQiFw modify @json:'{"jwt_grant_enabled":true,"explicit_authorization_required":false}'

User key registration

The public key must be assigned to your user. This can be done in two manners:


open the previously generated public key located here: $HOME/.aspera/mlia/

  • Open a web browser, log to your instance:
  • Click on the user's icon (top right)
  • Select "Account Settings"
  • Paste the Public Key in the "Public Key" section
  • Click on "Submit"
Using command line
$ mlia aspera admin res user list
:   id   :      name      :
: 109952 : Tech Support   :
: 109951 : LAURENT MARTIN :
$ mlia aspera user info modify @ruby:'{"public_key"=>"~/.aspera/mlia/"))}'   

Note: the aspera user info show command can be used to verify modifications.

option preset modification for JWT

To activate default use of JWT authentication for mlia using the option preset, do the folowing:

  • change auth method to JWT
  • provide location of private key
  • provide username to login as (OAuthg "subject")


$ mlia config id my_aoc_org update --auth=jwt [email protected]:@file:~/.aspera/mlia/aocapikey [email protected]

Note: the private key argument represents the actual PEM string. In order to read the content from a file, use the @file: prefix. But if the @file: argument is used as is, it will read the file and set in the config file. So to keep the "@file" tag in the configuration file, the @val: prefix is added.

After this last step, commands do not require web login anymore.


The admin command allows several administrative tasks (and require admin privilege).

It allows actions (create, update, delete) on "resources": users, group, nodes, workspace, etc... with the admin resource command.

Bulk operations are possible using option bulk (yes,no(default)): currently: create only. In that case, the operation expects an Array of Hash instead of a simple Hash using the Extended Value Syntax.

To get more resources when doing request add:

[email protected]:'{"per_page":10000}'

other query parameters can be used:

[email protected]:'{"member_of_any_workspace":true}'
[email protected]:'{"q":"laurent"}'

Refer to the AoC API for full list of query parameters.

Access Key secrets

In order to access some administrative actions on "nodes" (in fact, access keys), the associated secret is required, it is usually provided using the secret option. For example in a command like:

$ mlia aspera admin res node --id="access_key1" --secret="secret1" v3 info

It is also possible to provide a set of secrets used on a regular basis. This can be done using the secrets option. The value provided shall be a Hash, where keys are access key ids, and values are the associated secrets.

First choose a repository name, for example my_secrets, and populate it like this:

$ mlia conf id my_secrets set 'access_key1' 'secret1'
$ mlia conf id my_secrets set 'access_key2' 'secret2'
$ mlia conf id default get config

Here above, one already has set a config global preset to preset cli_default (refer to earlier in documentation), then the repository can be read by default like this (note the prefix @val: to avoid the evaluation of prefix @preset:):

$ mlia conf id cli_default set secrets @val:@preset:my_secrets

A secret repository can always be selected at runtime using [email protected]:xxxx, or [email protected]:'{"accesskey1":"secret1"}'


  • Bulk creation
$ mlia aspera admin res user create --bulk=yes @json:'[{"email":"[email protected]"},{"email":"[email protected]"}]'
:  id   : status  :
: 98398 : created :
: 98399 : created :
  • Find with filter and delete
$ mlia aspera admin res user list --query='@json:{"q":"dummyuser"}' --fields=id,email
:  id   :         email          :
: 98398 : [email protected] :
: 98399 : [email protected] :
$ thelist=$(echo $(mlia aspera admin res user list --query='@json:{"q":"dummyuser"}' --fields=id,email --field=id --format=csv)|tr ' ' ,)
$ echo $thelist
$ mlia aspera admin res user --bulk=yes [email protected]:[$thelist] delete
:  id   : status  :
: 98398 : deleted :
: 98399 : deleted :
  • Display current user's workspaces
$ mlia aspera user workspaces
:  id  :            name            :
: 16   : Engineering                :
: 17   : Marketing                  :
: 18   : Sales                      :
  • Create a sub access key in a "node"

Creation of a sub-access key is like creation of access key with the following difference: authentication to node API is made with accesskey (master access key) and only the path parameter is provided: it is relative to the storage root of the master key. (id and secret are optional)

$ mlia aspera admin resource node --name=_node_name_ --secret=_secret_ v4 access_key create [email protected]:'{"storage":{"path":"/folder1"}}'
  • Display transfer events (ops/transfer)
$ mlia aspera admin res node --secret=_secret_ v3 transfer list [email protected]:'[["q","*"],["count",5]]'
          # page=1&per_page=10&q=type:(file_upload+OR+file_delete+OR+file_download+OR+file_rename+OR+folder_create+OR+folder_delete+OR+folder_share+OR+folder_share_via_public_link)&sort=-date
          #[email protected]'events',{'q'=>'type:(file_upload OR file_download)'})[:data]
          # can add filters: tag=aspera.files.package_id%3DLA8OU3p8w
          # filter= 'id', 'short_summary', or 'summary'
          # count=nnn
          # tag=x.y.z%3Dvalue
          # iteration_token=nnn
          # after_time=2016-05-01T23:53:09Z
          # active_only=true|false
  • Display node events (events)
$ mlia aspera admin res node --secret=_secret_ v3 events
  • display members of a workspace
$ mlia aspera admin res workspace_membership list --fields=member_type,manager, [email protected]:'{"page":1,"per_page":50,"embed":"member","inherited":false,"workspace_id":11363,"sort":"name"}'
: member_type : manager :            :
: user        : true    : [email protected]            :
: user        : false   : [email protected] :
: user        : false   : [email protected]               :
: user        : false   : [email protected]         :
: group       : false   :                                  :
: user        : false   : [email protected]            :

other query parameters:

  • add all members of a workspace to another workspace

a- get id of first workspace

WS1='First Workspace'
WS1ID=$(mlia aspera admin res workspace list [email protected]:'{"q":"'"$WS1"'"}' [email protected]:'{"name":"'"$WS1"'"}' --fields=id --format=csv)

b- get id of second workspace

WS2='Second Workspace'
WS2ID=$(mlia aspera admin res workspace list [email protected]:'{"q":"'"$WS2"'"}' [email protected]:'{"name":"'"$WS2"'"}' --fields=id --format=csv)

c- extract membership information and change workspace id

mlia aspera admin res workspace_membership list --fields=manager,member_id,member_type,workspace_id [email protected]:'{"per_page":10000,"workspace_id":'"$WS1ID"'}' --format=jsonpp > ws1_members.json

d- convert to creation data for second workspace:

grep -Eve '(direct|effective_manager|_count|storage|"id")' ws1_members.json|sed '/workspace_id/ s/"'"$WS1ID"'"/"'"$WS2ID"'"/g' > ws2_members.json

or, using jq:

jq '[.[] | {member_type,member_id,workspace_id,manager,workspace_id:"'"$WS2ID"'"}]' ws1_members.json > ws2_members.json

e- add members to second workspace

mlia aspera admin res workspace_membership create --bulk=yes @json:@file:ws2_members.json
  • get users who did not log since a date
$ mlia aspera admin res user list --fields=email [email protected]:'{"per_page":10000,"q":"last_login_at:<2018-05-28"}' 
:             email             :
: [email protected]          :
: [email protected]      :
  • list "Limited" users
$ mlia aspera admin res user list --fields=email [email protected]:'{"per_page":10000}' [email protected]:'{"member_of_any_workspace":false}'
  • Perform a multi Gbps transfer between two remote shared folders

In this example, a user has access to a workspace where two shared folders are located on differente sites, e.g. different cloud regions.

First, setup the environment (skip if already done)

$ mlia conf wizard --url= [email protected]
Detected: Aspera on Cloud
Preparing preset: aoc_sedemo
Using existing key:
Using global client_id.
Please Login to your Aspera on Cloud instance.
Navigate to your "Account Settings"
Check or update the value of "Public Key" to be:
-----END PUBLIC KEY-----
Once updated or validated, press enter.

creating new config preset: aoc_sedemo
Setting config preset as default for aspera
saving config file
You can test with:
mlia aspera user info show

This creates the option preset "aoc_<org name>" to allow seamless command line access and sets it as default for aspera on cloud.

Then, create two shared folders located in two regions, in your files home, in a workspace.

Then, transfer between those:

$ mlia -Paoc_show aspera files transfer --from-folder='IBM Cloud SJ' --to-folder='AWS Singapore' 100GB.file [email protected]:'{"target_rate_kbps":"1000000","multi_session":10,"multi_session_threshold":1}'
  • create registration key to register a node

    $ mlia aspera admin res admin/client create @json:'{"data":{"name":"laurentnode","client_subject_scopes":["alee","aejd"],"client_subject_enabled":true}}' --fields=token --format=csv
  • delete all registration keys

$ mlia aspera admin res admin/client list --fields=id --format=csv|mlia aspera admin res admin/client delete --bulk=yes [email protected]:@stdin:
| id  | status  |
| 99  | deleted |
| 100 | deleted |
| 101 | deleted |
| 102 | deleted |

Shared folders


  • list shared folders in node
$ mlia aspera admin res node --id=8669 shared_folders
  • list shared folders in workspace
$ mlia aspera admin res workspace --id=10818 shared_folders
  • list members of shared folder
$ mlia aspera admin res node --id=8669 v4 perm 82 show

Send a Package

Send a package:

$ mlia aspera packages send [email protected]:'{"name":"my title","note":"my note","recipients":["[email protected]","[email protected]"]}' [email protected] my_file.dat


  • the value parameter can contain any supported package creation parameter. Refer to the API, or display an existing package.
  • to list recipients use fields: "recipients" and/or "bcc_recipients". mlia will resolve the list of email addresses to expected user ids. If a recipient is not already registered and the workspace allows external users, then the package is sent to an external user, and
    • if the option new_user_option is @json:{"package_contact":true} (default), then a public link is sent and the external user does not need to create an account.
    • if the option new_user_option is @json:{}, then external users are invited to join the workspace

Receive only new packages

It is possible to automatically download new packages, like using Aspera Cargo:

$ mlia aspera packages recv --id=ALL --once-only=yes --lock-port=12345
  • --id=ALL (case sensitive) will download all packages
  • --once-only=yes keeps memory of any downloaded package in persistency files located in the configuration folder.
  • --lock-port=12345 ensures that only one instance is started at the same time, to avoid collisions

Typically, one would regularly execute this command on a regular basis, using the method oif your choice:

  • Windows scheduler
  • cron
  • etc...

Download Files

Download of files is straightforward with a specific syntax for the aspera files download action: Like other commands the source file list is provided as a list with the sources option. Nevertheless, consider this:

  • if only one source is provided, it is downloaded
  • if multiple sources must be downloaded, then the first in list is the path of the source folder, and the remaining items are the file names in this folder (without path).

Find Files

The command aspera files find [--value=expression] will recursively scan storage to find files matching the expression criteria. It works also on node resource using the v4 command. (see examples)

The expression can be of 3 formats:

  • empty (default) : all files, equivalent to: exec:true
  • not starting with exec: : the expression is a regular expression, using ruby regex syntax. equivalent to: exec:f['name'].match(/expression/)

For instance, to find files with a special extension, use --value='\.myext$'

  • starting with exec: : the ruby code after the prefix is executed for each entry found. the entry variable name is f. the file is displayed if the result is true;

Examples of expressions: (think to prefix with exec: and put in single quotes using bash)

  • find files more recent than 100 days
f["type"].eql?("file") and (["modified_time"]))<100
  • expression to find files older than 1 year on a given node and store in file list
$ mlia aspera admin res node --name='my node name' --secret='my secret' v4 find / --fields=path --value='exec:f["type"].eql?("file") and (["modified_time"]))<100' --format=csv > my_file_list.txt
  • delete the files, one by one
$ cat my_file_list.txt|while read path;do echo mlia aspera admin res node --name='my node name' --secret='my secret' v4 delete "$path" ;done
  • delete the files in bulk
cat my_file_list.txt | mlia aspera admin res node --name='my node name' --secret='my secret' v3 delete @lines:@stdin:


The activity app can be queried with:

$ mlia aspera admin analytics transfers

It can also support filters and send notification email with a template:

$ mlia aspera admin analytics transfers --once-only=yes --lock-port=123455 \
[email protected]:'{"status":"completed","direction":"receive"}' \
[email protected]:'{"to":"<''%=transfer[:user_email.to_s]%>","subject":"<''%=transfer[:files_completed.to_s]%> files received","body":"Dear <''%=transfer[:user_email.to_s]%>\nWe received <''%=transfer[:files_completed.to_s]%> files for a total of <''%=transfer[:transferred_bytes.to_s]%> bytes, starting with file:\n<''%=transfer[:content.to_s]%>\n\nThank you."}'
  • once_only keep track of last date it was called, so next call will get only new events
  • query filter (on API call)
  • notify send an email as specified by template, this could be places in a file with the @file modifier.

Note this must not be executed in less than 5 minutes because the analytics interface accepts only a period of time between 5 minutes and 6 months. here the period is [date of previous execution]..[now].

IBM Aspera High Speed Transfer Server (transfer)

This plugin works at FASP level (SSH/ascp/ascmd) and does not use the node API.


Both password and SSH keys auth are supported.

Multiple SSH key paths can be provided. The value of the parameter ssh_keys can be a single value or an array. Each value is a path to a private key and is expanded ("~" is replaced with the user's home folder).


$ mlia server --ssh-keys=~/.ssh/id_rsa
$ mlia server [email protected]:,~/.ssh/id_rsa
$ mlia server [email protected]:'["~/.ssh/id_rsa"]'

The underlying ssh library net::ssh provides several options that may be used depending on environment. By default the ssh library expect that an ssh-agent is running, but if you get the error message:

ERROR -- net.ssh.authentication.agent: could not connect to ssh-agent: Agent not configured

This means that you dont have such agent, check env var: SSH_AGENT_SOCK, check if the key is protected with a passphrase. check the manual

To diable use of ssh-agent, use the option ssh_option like this (or set in preset):

$ mlia server [email protected]:'{use_agent: false}' ...


One can test the "server" application using the well known demo server:

$ mlia config id aspera_demo_server update --url=ssh:// --username=asperaweb --password=demoaspera
$ mlia config id default set server aspera_demo_server 
$ mlia server browse /aspera-test-dir-large
$ mlia server download /aspera-test-dir-large/200MB

This creates a option preset "aspera_demo_server" and set it as default for application "server"

IBM Aspera High Speed Transfer Server (node)

This plugin gives access to capabilities provided by HSTS node API.

Simple Operations

It is possible to:

  • browse
  • transfer (upload / download)
  • ...


The central subcommand uses the "reliable query" API (session and file). It allows listing transfer sessions and transfered files.

Filtering can be applied:

$ mlia node central file list

by providing the validator option, offline transfer validation can be done.

FASP Stream

It is possible to start a FASPStream session using the node API:

Use the "node stream create" command, then arguments are provided as a transfer-spec.

$ mlia node stream create [email protected]:'{"direction":"send","source":"udp://","destination":"udp://","remote_host":"localhost","remote_user":"stream","remote_password":"XXXX"}' --preset=stream


Refer to Aspera documentation for watch folder creation.

mlia supports remote operations through the node API. Operations are:

  • Start watchd and watchfolderd services running as a system user having access to files
  • configure a watchfolder to define automated transfers
$ mlia node service create @json:'{"id":"mywatchd","type":"WATCHD","run_as":{"user":"user1"}}'
$ mlia node service create @json:'{"id":"mywatchfolderd","type":"WATCHFOLDERD","run_as":{"user":"user1"}}'
$ mlia node watch_folder create @json:'{"id":"mywfolder","source_dir":"/watch1","target_dir":"/","transport":{"host":"","user":"user1","pass":"mypassword"}}'

Out of Transfer File Validation

Follow the Aspera Transfer Server configuration to activate this feature.

$ mlia node central file list --validator=mlia [email protected]:'{"file_transfer_filter":{"max_result":1}}'
: session_uuid :    file_id   :   status   :              path                    :
: 1a74444c-... : 084fb181-... : validating : /home/xfer.../PKG - my title/200KB.1 :
$ mlia node central file update --validator=mlia [email protected]:'{"files":[{"session_uuid": "1a74444c-...","file_id": "084fb181-...","status": "completed"}]}'

Example: SHOD to ATS

Access to a "Shares on Demand" (SHOD) server on AWS is provided by a partner. And we need to transfer files from this third party SHOD instance into our Azure BLOB storage. Simply create an "Aspera Transfer Service" instance (, which provides access to the node API. Then create a configuration for the "SHOD" instance in the configuration file: in section "shares", a configuration named: awsshod. Create another configuration for the Azure ATS instance: in section "node", named azureats. Then execute the following command:

$ mlia node download /share/sourcefile --to-folder=/destinationfolder --preset=awsshod --transfer=node [email protected]:azureats

This will get transfer information from the SHOD instance and tell the Azure ATS instance to download files.

Create access key

$ mlia node access_key create [email protected]:'{"id":"eudemo-sedemo","secret":"mystrongsecret","storage":{"type":"local","path":"/data/asperafiles"}}'

IBM Aspera Faspex

Note that the command "v4" requires the use of APIv4, refer to the Faspex Admin manual on how to activate.

Sending a Package

Provide delivery info in JSON, example:

[email protected]:'{"title":"my title","recipients":["[email protected]"]}'

a note can be added: "note":"Please ..."

metadata: "metadata":{"Meta1":"Val1","Meta2":"Val2"}

Note for full details, refer to: Reference on Developer Site

operation on dropboxes


$ mlia faspex v4 dropbox create [email protected]:'{"dropbox":{"e_wg_name":"test1","e_wg_desc":"test1"}}'
$ mlia faspex v4 dropbox list
$ mlia faspex v4 dropbox delete --id=36

remote sources

Faspex lacks an API to list the contents of a remote source (available in web UI). To workaround this, the node API is used, for this it is required to add a section ":storage" that links a storage name to a node config and sub path.


  username: admin
  password: MyPassword
      node: "@preset:my_faspex_node"
      path: /myfiles
  username: node_faspex
  password: MyPassword

In this example, a faspex storage named "testlaurent" exists in Faspex, and is located under the docroot in "/myfiles" (this must be the same as configured in Faspex). The node configuration name is "my_faspex_node" here.

Note: the v4 API provide an API for nodes and shares.

Automated package download (cargo)

It is possible to tell mlia to download newly received packages, much like the official cargo client, or drive. Refer to the same section in the Aspera on Cloud plugin:

$ mlia faspex packages recv --id=ALL --once-only=yes --lock-port=12345

IBM Aspera Shares

Aspera Shares supports the "node API" for the file transfer part. (Shares 1 and 2)

In Shares2, users, groups listing are paged, to display sequential pages:

$ for p in 1 2 3;do mlia shares2 admin users list [email protected]:'{"page":'$p'}';done

Aspera Transfer Service

ATS is usable either :

  • from an AoC subscription : mlia aspera admin ats

  • or from an IBM Cloud subscription : mlia ats

IBM Cloud ATS : creation of api key

First get your IBM Cloud APIkey. For instance, it can be created using the IBM Cloud web interface, or using command line:

$ ibmcloud iam api-key-create mykeyname -d 'my sample key'
API key mykeyname was created

Please preserve the API key! It cannot be retrieved after it's created.

Name          mykeyname   
Description   my sample key
Created At    2019-09-30T12:17+0000   
API Key       my_secret_api_key_here_8f8d9fdakjhfsashjk678
Locked        false   
UUID          ApiKey-05b8fadf-e7fe-4bc4-93a9-6fd348c5ab1f  


Then, to register the key by default for the ats plugin, create a preset. Execute:

$ mlia config id my_ibm_ats update --ibm-api-key=my_secret_api_key_here_8f8d9fdakjhfsashjk678
$ mlia config id default set ats my_ibm_ats
$ mlia ats api_key instances
| instance                             |
| aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee |
$ mlia config id my_ibm_ats update --instance=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee
$ mlia ats api_key create
| key    | value                                        |
| id     | ats_XXXXXXXXXXXXXXXXXXXXXXXX                 |


Example: create access key on softlayer:

$ mlia ats access_key create --cloud=softlayer --region=ams [email protected]:'{"storage":{"type":"softlayer_swift","container":"_container_name_","credentials":{"api_key":"value","username":"_name_:_usr_name_"},"path":"/"},"id":"_optional_id_","name":"_optional_name_"}'

Example: create access key on AWS:

$ mlia ats access_key create --cloud=aws --region=eu-west-1 [email protected]:'{"id":"testkey3","name":"laurent key AWS","storage":{"type":"aws_s3","bucket":"my-bucket","credentials":{"access_key_id":"AKIA_MY_API_KEY","secret_access_key":"my/secret/here"},"path":"/laurent"}}'

Example: create access key on Azure SAS:

$ mlia ats access_key create --cloud=azure --region=eastus [email protected]:'{"id":"testkeyazure","name":"laurent key azure","storage":{"type":"azure_sas","credentials":{"shared_access_signature":""},"path":"/"}}'

(Note that the blob name is mandatory after server address and before parameters. and that parameter sr=c is mandatory.)

Example: create access key on Azure:

$ mlia ats access_key create --cloud=azure --region=eastus [email protected]:'{"id":"testkeyazure","name":"laurent key azure","storage":{"type":"azure","credentials":{"account":"myaccount","key":"myaccesskey","storage_endpoint":"myblob"},"path":"/"}}'

delete all my access keys:

for k in $(mlia ats access_key list --field=id --format=csv);do mlia ats access_key id $k delete;done

IBM Cloud Object Storage

BETA: experimental

The IBM Cloud Object Storage provides the possibility to execute transfers using FASP.

Required information are:

  • service credentials
  • region
  • bucket

Service credentials are directly created using the IBM cloud web ui. Navigate to:

Navigation Menu → Resource List → Storage → Cloud Object Storage → Service Credentials → <select or create credentials> → view credentials → copy

Then save the copied value to a file, e.g. : $HOME/cos_service_creds.json

or using the CLI:

$ ibmcloud resource service-keys
$ ibmcloud resource service-key aoclaurent --output JSON|jq '.[0].credentials'>$HOME/service_creds.json

(if you dont have jq installed, extract the structure as follows)

It consists in the following structure:

  "apikey": "xxxxxxx.....",
  "cos_hmac_keys": {
    "access_key_id": "xxxxxxx.....",
    "secret_access_key": "xxxxxxx....."
  "endpoints": "",
  "iam_apikey_description": "my description ...",
  "iam_apikey_name": "my key name",
  "iam_role_crn": "crn:v1:bluemix:public:iam::::serviceRole:Writer",
  "iam_serviceid_crn": "crn:v1:bluemix:public:iam-identity::a/xxxxxxx.....",
  "resource_instance_id": "crn:v1:bluemix:public:cloud-object-storage:global:a/xxxxxxx....."

For convenience, let us create a default configuration, for example:

$ mlia conf id mycos update [email protected]:@json:@file:$HOME/service_creds.json  --region=us-south --bucket=laurent
$ mlia conf id default set cos mycos

Now, Ready to do operations, a subset of "node" plugin operations are supported, basically node API:

$ mlia cos node browse /
$ mlia cos node upload myfile.txt

IBM Aspera Sync

A basic plugin to start an "async" using mlia. The main advantage is the possibility to start from ma configuration file, using mlia standard options.


The preview generates "previews" of graphical files, i.e. thumbnails (office, images, video) and video previews on an Aspera HSTS for use primarily in the Aspera on Cloud application. This is based on the "node API" of Aspera HSTS when using Access Keys only inside it's "storage root". Several parameters can be used to tune several aspects:

  • methods for detection of new files needing generation
  • methods for generation of video preview
  • parameters for video handling

Candidate detection for creation or update (or deletion)

The tool will find candidates for preview generation using three commands:

  • events : only recently uploaded files will be tested
  • scan : deeply scan all files under the access key's "storage root"
  • folder : same as scan, but only on the specified folder's "file identifier"
  • file : for an individual file generation

Note that for the event, the option iteration_file should be specified so that successive calls only process new events. This file will hold an identifier telling from where to get new events.

It is also possible to test a local file, using the test command.

Once candidate are selected, once candidates are selected, a preview is always generated if it does not exist already, else if a preview already exist, it will be generated using one of three overwrite method:

  • always : preview is always generated, even if it already exists and is newer than original
  • never : preview is generated only if it does not exist already
  • mtime : preview is generated only if the original file is newer than the existing

Deletion of preview for deleted source files: not implemented yet.

If the scan or events detection method is used, then the option : skip_folders can be used to skip some folders. It expects a list of path starting with slash, use the @json: notation, example:

$ mlia preview scan [email protected]:'["/not_here"]'

The option folder_reset_cache forces the node service to refresh folder contents using various methods.

Files types

Not all file types support preview: only those file types being able to be rendered are supported:

  • image
  • video
  • office
  • pdf
  • plaintext

File type is primarily base on file extension detected by the node API and translated info a mime type returned by the node API. Optionally, the tool can also locally detect the mime type using option: validate_mime=yes

To avoid generation for some types, specify a list using option skip_types.

Two types of preview can be generated:

  • png: thumbnail
  • mp4: video preview (only for video)

Access to original files and preview creation

Standard open source tools are used to create thumnails and video previews. Those tools require that original files are accessible in the local file system and also write generated files on the local file system. The tool provides 2 ways to read and write files with the option: file_access

If the preview generator is run on a system that has direct access to the file system, then the value local can be used. In this case, no transfer happen, source files are directly read from the storage, and preview files are directly written to the storage.

If the preview generator does not have access to files on the file system (it is remote, no mount, or is an object storage), then the original file is first downloaded, then the result is uploaded, use method remote.

External tools: Linux

The tool requires the following external tools available in the PATH:

  • ImageMagick : convert composite
  • OptiPNG : optipng
  • FFmpeg : ffmpeg ffprobe
  • Libreoffice : libreoffice

Here shown on Redhat/CentOS.

Other OSes should work as well, but are note tested.

Imagemagick and optipng:

yum install -y ImageMagick optipng


pushd /tmp
mkdir -p /opt/
cd /opt/
tar xJvf /tmp/ffmpeg-release-64bit-static.tar.xz
ln -s ffmpeg-* ffmpeg
ln -s /opt/ffmpeg/{ffmpeg,ffprobe} /usr/bin


As installation is a little complex, it is possible to not install libreoffice, and skip office document preview generation by using option: --skip-types=office

yum install libreoffice

Xvfb (for Libreoffice)

Although libreoffice is run headless, older versions may require an X server. If you get error running libreoffice headless, then install Xvfb:

yum install -y Xvfb
# !/bin/bash
# chkconfig: 345 95 50
# description: Starts xvfb on display 42 for headless Libreoffice
if [ -z "\$1" ]; then
  echo "\`basename \$0\` {start|stop}"
case "\$1" in
start) /usr/bin/Xvfb :42 -screen 0 1280x1024x8 -extension RANDR&;;
stop) killall Xvfb;;
chmod a+x /etc/init.d/xvfb
chkconfig xvfb on
service xvfb start

Aspera Server configuration

Specify the previews folder as shown in:

By default, the preview plugin expects previews to be generated in a folder named previews located in the storage root. On the transfer server execute:

# /opt/aspera/bin/asconfigurator -x "server;preview_dir,previews"
# /opt/aspera/bin/asnodeadmin --reload

If another folder is configured on the HSTS, then specify it to mlia using the option previews_folder.

The HSTS node API limits any preview file to a parameter: max_request_file_create_size_kb (1 KB is 1024 bytes). This size is internally capped to 1<<24 Bytes, i.e. 16,777,216 Bytes.

To change this parameter in aspera.conf, use asconfigurator. To display the value, use asuserdata:

$ asuserdata -a | grep max_request_file_create_size_kb
  max_request_file_create_size_kb: "1024"

If you use a value different than 16,777,216, then specify it using option max_size.


Like any mlia commands, parameters can be passed on command line or using a configuration option preset. Note that if you use the mlia run as xfer user, like here, the configuration file must be created as the same user. Example using a option preset named my_preset_name (choose any name relevant to you, e.g. the AoC node name, and replace in the following lines):

# su -s /bin/bash - xfer
$ mlia config id my_preset_name update --url=https://localhost:9092 --username=my_access_key --password=my_secret --skip-types=office --lock-port=12346
$ mlia config id default set preview my_preset_name

Here we assume that Office file generation is disabled, else remove the option. For the lock_port option refer to a previous section in thsi manual.

Once can check if the access key is well configured using:

$ mlia -Pmy_preset_name node browse /

This shall list the contents of the storage root of the access key.


The tool intentionally supports only a "one shot" mode in order to avoid having a hanging process or using too many resources (calling REST api too quickly during the scan or event method). It needs to be run regularly to create or update preview files. For that use your best reliable scheduler. For instance use "CRON" on Linux or Task Scheduler on Windows.

Typically, for "Access key" access, the system/transfer is xfer. So, in order to be consiustent have generate the appropriate access rights, the generation process should be run as user xfer.

Lets do a one shot test, using the configuration previously created:

# su -s /bin/bash - xfer
$ mlia preview scan --overwrite=always

Configuration for Execution in scheduler

Here is an example of configuration for use with cron on Linux. Adapt the scripts to your own preference.

We assume here that a configuration preset was created as shown previously.

Here the cronjob is created for root, and changes the user to xfer, also overriding the shell which should be aspshell. (adapt the command below, as it would override existing crontab). It is also up to you to use directly the xfer user's crontab. This is an example only.

# crontab<<EOF
2-59 * * * * su -s /bin/bash - xfer -c 'nice +10 timeout 10m mlia preview event --log-level=info --logger=syslog --iteration-file=/tmp/preview_restart.txt'
0 * * * *    su -s /bin/bash - xfer -c 'nice +10 timeout 30m mlia preview scan  --log-level=info --logger=syslog'

Nopte that the options here may be located in the config preset, but it was left on the command line to keep stdout for command line execution of preview.

SMTP for email notifications

Amelia can send email, for that setup SMTP configuration. This is done with option smtp.

The smtp option is a hash table (extended value) with the following fields:

fielddefaultexampledescription server address
tlstruefalseuse of TLS
port587 for tls
25 else
587port for service
domaindomain of servergmail.comemail domain of user
username-[email protected]user to authenticate on SMTP server, leave empty for open auth.
password-[email protected]password for above username
from\_emailusername if defined[email protected]address used if received replies
from\_namesame as emailJohn Waynedisplay name of sender

Example of configuration:

$ mlia config id smtp_google set server
$ mlia config id smtp_google set username [email protected]
$ mlia config id smtp_google set password [email protected]


$ mlia config id smtp_google init @json:'{"server":"","username":"[email protected]","password":"[email protected]"}'

Set this configation as global default, for instance:

$ mlia config id cli_default set smtp @val:@preset:smtp_google
$ mlia config id default set config cli_default


Check settings with smtp_settings command. Send test email with email_test.

$ mlia config [email protected]:smtp_google smtp
$ mlia config [email protected]:smtp_google email [email protected]

Tool: asession

This gem comes with a second executable tool providing a simplified standardized interface to start a FASP session: asession.

It aims at simplifying the startup of a FASP session from a programmatic stand point as formating a transfer-spec is:

  • common to Aspera Node API (HTTP POST /ops/transfer)
  • common to Aspera Connect API (browser javascript startTransfer)
  • easy to generate by using any third party language specific JSON library

Hopefully, IBM integrates this diectly in ascp, and this tool is made redundant.

This makes it easy to integrate with any language provided that one can spawn a sub process, write to its STDIN, read from STDOUT, generate and parse JSON.

The tool expect one single argument: a transfer-spec.

If not argument is provided, it assumes a value of: @json:@stdin:, i.e. a JSON formated transfer-spec on stdin.

Note that if JSON is the format, one has to specify @json: to tell the tool to decode the hash using JSON.

During execution, it generates all low level events, one per line, in JSON format on stdout.

Note that there are special "extended" transfer-spec parameters supported by asession:

  • EX_loglevel to change log level of the tool
  • EX_file_list_folder to set the folder used to store (exclusively, because of garbage collection) generated file lists. By default it is [system tmp folder]/[username]_asession_filelists

Note that in addition, many "EX_" transfer-spec parameters are supported for the "local" transfer agent (used by asession), refer to section transfer-spec.

Comparison of interfaces

language integrationanyanyC/C++
additional components to ascpRuby
startupJSON on stdin
(standard APIs:
command line argumentsAPI
eventsJSON on stdoutnone by default
or need to open management port
and proprietary text syntax

Simple session


echo "${MY_TSPEC}"|asession

Asynchronous commands and Persistent session

asession also supports asynchronous commands (on the management port). Instead of the traditional text protocol as described in ascp manual, the format for commands is: one single line per command, formatted in JSON, where parameters shall be "snake" style, for example: LongParameter -> long_parameter

This is particularly useful for a persistent session ( with the transfer-spec parameter: "keepalive":true )

$ asession

(events from FASP are not shown in above example. They would appear after each command)

Example of language wrapper



$ asession -h
    asession -h|--help
    asession <transfer spec extended value>

    If no argument is provided, default will be used: @json:@stdin
    -h, --help display this message
    <transfer spec extended value> a JSON value for transfer_spec, using the prefix: @json:
    The value can be either:
       the JSON description itself, e.g. @json:'{"xx":"yy",...}'
       @json:@stdin, if the JSON is provided from stdin
       @json:@file:<path>, if the JSON is provided from a file
    Asynchronous commands can be provided on STDIN, examples:
Note: debug information can be placed on STDERR, using the "EX_loglevel" parameter in transfer spec (debug=0)
    asession @json:'{"remote_host":"","remote_user":"asperaweb","ssh_port":33001,"remote_password":"demoaspera","direction":"receive","destination_root":"./test.dir","paths":[{"source":"/aspera-test-dir-tiny/200KB.1"}]}'
    echo '{"remote_host":...}'|asession @json:@stdin

Hot folder


mlia maybe used as a simple hot folder engine. A hot folder being defined as a tool that:

  • locally (or remotely) detects new files in a top folder
  • send detected files to a remote (respectively, local) repository
  • only sends new files, do not re-send already sent files
  • optionally: sends only files that are not still "growing"
  • optionally: after transfer of files, deletes or moves to an archive

In addition: the detection should be made "continuously" or on specific time/date.

Setup procedure

The general idea is to rely on :

  • existing ascp features for detection and transfer
  • take advantage of mlia configuration capabilities and server side knowledge
  • the OS scheduler for reliability and continuous operation

ascp features

Interesting ascp features are found in its arguments: (see ascp manual):

  • ascp already takes care of sending only "new" files: option -k 1,2,3, or transfer_spec: resume_policy
  • ascp has some options to remove or move files after transfer: --remove-after-transfer, --move-after-transfer, --remove-empty-directories
  • ascp has an option to send only files not modified since the last X seconds: --exclude-newer-than (--exclude-older-than)
  • --src-base if top level folder name shall not be created on destination

Note that:

  • mlia takes transfer parameters exclusively as a transfer_spec, with --ts parameter.
  • not all native ascp arguments are available as standard transfer_spec parameters
  • native ascp arguments can be provided with the transfer-spec parameter: EX_ascp_args (array), only for the "local" transfer agent (not connect or node)

server side and configuration

Virtually any transfer on a "repository" on a regular basis might emulate a hot folder. Note that file detection is not based on events (inotify, etc...), but on a stateless scan on source side.

Note: parameters may be saved in a option preset and used with -P.


Once mlia parameters are defined, run the command using the OS native scheduler, e.g. every minutes, or 5 minutes, etc... Refer to section Scheduling.


$ mlia server upload source_hot --to-folder=/Upload/target_hot --lock-port=12345 [email protected]:'{"EX_ascp_args":["--remove-after-transfer","--remove-empty-directories","--exclude-newer-than=-8","--src-base","source_hot"]}'

The local (here, relative path: source_hot) is sent (upload) to basic fasp server, source files are deleted after transfer. growing files will be sent only once they dont grow anymore (based ona 8 second cooloff period). If a transfer takes more than the execution period, then the subsequent execution is skipped (lock-port).

Module: Asperalm

Main components:

  • Asperalm generic classes for REST and OAuth
  • Asperalm::Fasp: starting and monitoring transfers. It can be considered as a FASPManager class for Ruby.
  • Asperalm::Cli: mlia.

A working example can be found in the gem, example:

$ mlia config gem_path
$ cat $(mlia config gem_path)/../examples/transfer.rb

This sample code shows some example of use of the API as well as REST API. Note: although nice, it's probably a good idea to use RestClient for REST.


When I joined Aspera, there was only one CLI: ascp, which is the implementation of the FASP protocol, but there was no CLI to access the various existing products (Server, Faspex, Shares). Once, Serban (founder) provided a shell script able to create a Faspex Package using Faspex REST API. Since all products relate to file transfers using FASP (ascp), I thought it would be interesting to have a unified CLI for transfers using FASP. Also, because there was already the ascp tool, I thought of an extended tool : which was accepting all ascp options for transfer but was also able to transfer to Faspex and Shares (destination was a kind of URI for the applications).

There were a few pitfalls:

  • The tool was written in the aging perl language while most Aspera application products (but the Transfer Server) are written in ruby.
  • The tool was only for transfers, but not able to call other products APIs

So, it evolved into mlia:

  • portable: works on platforms supporting ruby (and ascp)
  • easy to install with the gem utility
  • supports transfers with multiple Transfer Agents, that's why transfer parameters moved from ascp command line to transfer-spec (more reliable , more standard)
  • ruby is consistent with other Aspera products

Release Notes

  • 0.11.1

    • enhanced short_link creation commands (see examples)
  • 0.11

    • add option to provide file list directly to ascp like this (only for direct transfer agent):
... [email protected] [email protected]:'{"paths":[],"EX_file_list":"filelist"}'
  • 0.10.18

    • new option in. server : ssh_options
  • 0.10.17

    • fixed problem on server for option ssh_keys, now accepts both single value and list.
    • new modifier: @list:<saparator>val1<separator>...
  • 0.10.16

  • 0.10.15

    • in case of command line error, display the error cause first, and non-parsed argument second
    • AoC : Activity / Analytics
  • 0.10.14

    • added missing bss plugin
  • 0.10.13

    • added Faspex5 (use option value to give API arguments)
  • 0.10.12

    • added support for AoC node registration keys
    • replaced option : local_resume with transfer_info for agent direct
    • Transfer agent is no more a Singleton instance, but only one is used in CLI
    • @incps : new extended value modifier
    • ATS: no more provides access keys secrets: now user must provide it
    • begin work on "aoc" transfer agent
  • 0.10.11

    • minor refactor and fixes
  • 0.10.10

    • fix on documentation

    • add total number of items for AoC resource list
    • better gem version dependency (and fixes to support Ruby 2.0.0)
    • removed aoc search_nodes
  • 0.10.8

    • removed option: fasp_proxy, use pseudo transfer spec parameter: EX_fasp_proxy_url
    • removed option: http_proxy, use pseudo transfer spec parameter: EX_http_proxy_url
    • several other changes..
  • 0.10.7

    • fix: mlia fails when username cannot be computed on Linux.
  • 0.10.6

    • FaspManager: transfer spec authentication no more needed for local tranfer to use aspera public keys. public keys will be used if there is a token and no key or password is provided.
    • gem version requirements made more open
  • 0.10.5

    • fix faspex package receive command not working
  • 0.10.4

    • new options for AoC : secrets
    • ACLI-533 temp file list folder to use file lists is set by default, and used by asession
  • 0.10.3

    • included user name in oauth bearer token cache for AoC when JWT is used.
  • 0.10.2

    • updated search_nodes to be more generic, so it can search not only on access key, but also other queries.
    • added doc for "cargo" like actions
    • added doc for multi-session
  • 0.10.1

    • AoC and node v4 "browse" works now on non-folder items: file, link
    • initial support for AoC automation (do not use yet)
  • 0.10

    • support for transfer using IBM Cloud Object Storage
    • improved find action using arbitrary expressions
  • 0.9.36

    • added option to specify file pair lists
  • 0.9.35

    • updated plugin preview , changed parameter names, added documentation
    • fix in ats plugin : instance id needed in request header
  • 0.9.34

    • parser "@preset" can be used again in option "transfer_info"
    • some documentation re-organizing
  • 0.9.33

    • new command to display basic token of node
    • new command to display bearer token of node in AoC
    • the --fields= option, support +fieldname to add a field to default fields
    • many small changes
  • 0.9.32

    • all Faspex public links are now supported
    • removed faspex operation recv_publink
    • replaced with option link (consistent with AoC)
  • 0.9.31

    • added more support for public link: receive and send package, to user or dropbox and files view.
    • delete expired file lists
    • changed text table gem from text-table to terminal-table because it supports multiline values
  • 0.9.27

    • basic email support with SMTP
    • basic proxy auto config support
  • 0.9.26

    • table display with --fields=ALL now includes all column names from all lines, not only first one
    • unprocessed argument shows error even if there is an error beforehand
  • 0.9.25

    • the option value of command find, to filter on name, is not optional
    • find now also reports all types (file, folder, link)
    • find now is able to report all fields (type, size, etc...)
  • 0.9.24

    • fix bug where AoC node to node transfer did not work
    • fix bug on error if ED25519 private key is defined in .ssh
  • 0.9.23

    • defined REST error handlers, more error conditions detected
    • commands to select specific ascp location
  • 0.9.21

    • supports simplified wizard using global client
    • only ascp binary is required, other SDK (keys) files are now generated
  • 0.9.20

    • improved wizard (prepare for AoC global client id)
    • preview generator: addedoption : --skip-format=<png,mp4>
    • removed outdated pictures from this doc
  • 0.9.19

    • added command aspera bearer --scope=xx
  • 0.9.18

    • enhanced aspera admin events to support query
  • 0.9.16

    • AoC transfers are now reported in activity app
    • new interface for Rest class authentication (keep backward compatibility)
  • 0.9.15

    • new feature: "find" command in aspera files
    • sample code for transfer API
  • 0.9.12

    • add nagios commands
    • support of ATS for IBM Cloud, removed old version based on aspera id
  • 0.9.11

    • Breaking change: @stdin is now @stdin:
    • support of ATS for IBM Cloud, removed old version based on aspera id
  • 0.9.10

    • Breaking change: parameter transfer-node becomes more generic: transfer-info
    • Display SaaS storage usage with command: aspera admin res node --id=nn info
    • cleaner way of specifying source file list for transfers
    • Breaking change: replaced download_mode option with http_download action
  • 0.9.9

    • Breaking change: "aspera package send" parameter deprecated, use the --value option instead with "recipients" value. See example.
    • Now supports "cargo" for Aspera on Cloud (automatic package download)
  • 0.9.8

    • Faspex: use option once_only set to yes to enable cargo like function. id=NEW deprecated.
    • AoC: share to share transfer with command "transfer"
  • 0.9.7

    • homogeneous transfer-spec for node and local
    • preview persistency goes to unique file by default
    • catch mxf extension in preview as video
    • Faspex: possibility to download all paclages by specifying id=ALL
    • Faspex: to come: cargo-like function to download only new packages with id=NEW
  • 0.9.6

    • Breaking change: @param:is now @preset: and is generic
    • AoC: added command to display current workspace information
  • 0.9.5

    • new parameter: new_user_option used to choose between public_link and invite of external users.
    • fixed bug in wizard, and wizard uses now product detection
  • 0.9.4

    • Breaking change: onCloud file list follow --source convention as well (plus specific case for download when first path is source folder, and other are source file names).
    • AoC Package send supports external users
    • new command to export AoC config to Aspera CLI config
  • 0.9.3

    • REST error message show host and code
    • option for quiet display
    • modified transfer interface and allow token re-generation on error
    • async add admin command
    • async add db parameters
    • Breaking change: new option "sources" to specify files to transfer
  • 0.9.2

    • Breaking change: changed AoC package creation to match API, see AoC section
  • 0.9.1

    • Breaking change: changed faspex package creation to match API, see Faspex section
  • 0.9

    • Renamed the CLI from aslmcli to mlia
    • Automatic rename and conversion of former config folder from aslmcli to mlia
  • 0.7.6

    • add "sync" plugin
  • 0.7

    • Breaking change: AoC package recv take option if for package instead of argument.
    • Breaking change: Rest class and Oauth class changed init parameters
    • AoC: receive package from public link
    • select by col value on output
    • added rename (AoC, node)
  • 0.6.19

Breaking change:

  • ats server list provisioned → ats cluster list
  • ats server list clouds → ats cluster clouds
  • ats server list instance --cloud=x --region=y → ats cluster show --cloud=x --region=y
  • ats server id xxx → ats cluster show --id=xxx
  • ats subscriptions → ats credential subscriptions
  • ats api_key repository list → ats credential cache list
  • ats api_key list → ats credential list
  • ats access_key id xxx → ats access_key --id=xxx

    • 0.6.18

some commands take now --id option instead of id command.

  • 0.6.15
  • Breaking change: "files" application renamed to "aspera" (for "Aspera on Cloud"). "repository" renamed to "files". Default is automatically reset, e.g. in config files and change key "files" to "aspera" in option preset "default".


  • This is best effort code without official support, dont expect full capabilities. This code is not supported by IBM/Aspera. You can contact the author for bugs or features.

only one value for any option

Some commands and sub commands may ask for the same option name. Currently, since option definition is position independant (last one wins), it is not possible to give an option to a command and the same option with different value to a sub command.

For instance, if an entity is identified by the option id but later on the command line another id option is required, the later will override the earlier one, and both entity will use the same id. As a workaround use another option, if available, to identify the entity.

This happens typically for the node sub command, e.g. identify the node by name instead of id.

ED255519 key not supported

ED255519 keys are deactivated since version 0.9.24 so this type of key will just be ignored. Without this deactivation, if such key was present the following error was generated:

OpenSSH keys only supported if ED25519 is available

Which meant that you do not have ruby support for ED25519 SSH keys. You may either install the suggested Gems, or remove your ed25519 key from your .ssh folder to solve the issue.



Send comments !

Create your own plugin !