Configuring for Aspera on Cloud

If you plan to use the Aspera CLI to make transfers to or from an Aspera on Cloud workspace, you must configure both the CLI and AoC to work together.

Before You Begin

The instructions in this section assume that you have
  • A working Aspera on Cloud instance and at least one workspace.
  • The Aspera CLI, installed on a computer.

Configuration Steps

  1. Generate a key pair.
    Note: If you already have an SSH public/private key pair, you can use it for the Aspera CLI, but take care to have the public key in .pem format.
    1. At the command line, generate your SSH public/private key pair: 
      #openssl genpkey -algorithm RSA -out private_key.pem -pkeyopt rsa_keygen_bits:2048
    2. When you are prompted to Enter file in which to save the key, press Enter or enter a custom path or filename.
    3. When you are prompted to Enter passphrase (empty for no passphrase), press Enter or enter a passphrase.
    4. Confirm the passphrase.
    5. Extract the public key from the key pair, into a .pem file: 
      #openssl rsa -pubout -in private_key.pem -out public_key.pem
      This is the public key that you will add to Aspera on Cloud in a later step.
  2. Add your public key to your AoC account.
    1. In Aspera on Cloud, go to the user menu and select Account settings.
    2. On the Account settings screen, in the Public Key field, paste the public portion of your public/private key pair.

      If you accepted the defaults when you extracted the public key, it is named id_rsa.pub.pem.

    3. Click Submit.
  3. Add your private key to your CLI installation.

    The file must be located in installation_directory\cli\etc.

  4. Edit the CLI config file.
    1. Locate the .aspera_cli_conf configuration file: 
      ~/.aspera/cli/bin/.aspera_cli_conf
    2. In a text editor, edit the Aspera on Cloud section of the .aspera_cli_conf file to set the following:
      • The filename of the private key (private_key_file_name). The default value is private.pem.
      • The organization name and hostname of the Aspera on Cloud server.
    3. Save the .aspera_cli_conf file.

Configuration File Syntax

The Aspera CLI package installs a .aspera_cli_conf file with sample configurations that you can use to see the correct syntax for this file.

Defining Multiple Servers

You can define multiple Faspex servers in the .aspera_cli_conf file, and multiple sources for each server. To specify which server a given command applies to, form your Aspera CLI command sequences using the name value that you defined in the configuration file.