System requirements and browser support

Edit online

This article describes the very simple requirements for Aspera on Cloud. You must use a supported browser/version. If your organization includes users who cannot use the default transfer method, you must configure an alternative method. Depending on your network configuration, you may need to configure your firewall.

Select an IBM Aspera transfer method

All transfers between Aspera on Cloud and a user desktop require one of these two transfer methods:
  • IBM Aspera Connect transfer client

    As the typical transfer method, Aspera Connect is a free, lightweight, install-on-demand software program that powers high-speed transfers between desktops and Aspera servers. Users must download and install the Connect client and, for most browsers, install a browser extension. The guided, in-app installation is quick and easy. For details, see What is IBM Aspera Connect?.

    Important: If you are using MacOS 10.12 or earlier, you must upgrade your OS or use Aspera Connect v3.11.
  • IBM Aspera HTTP Gateway

    The Aspera HTTP Gateway is a standalone product that uses both HTTP/S and Aspera FASP to complete file transfers. This transfer option does not require users to download and install a client.

    Once you configure your Aspera HTTP Gateway, you can point your Aspera on Cloud organization to it. For details, see Transfer with Aspera HTTP Gateway instead of Aspera Connect.

Transfers between nodes (node-to-node transfers) in your Aspera transfer network do not require Aspera Connect or Aspera HTTP Gateway.

Minimum software version for tethered nodes

If you have your own IBM Aspera High-Speed Transfer Server (HSTS), you can attach or "tether" it to your Aspera on Cloud organization. Tethering enables you to give users in your AoC organization access to content on your HSTS.

If you tether your HSTS node to Aspera on Cloud, IBM highly recommends that you always use the most recently released version of Aspera transfer server software (IBM Aspera High-Speed Transfer Service) for user-managed (tethered) nodes attached to Aspera on Cloud.

Aspera transfer servers tethered to Aspera on Cloud must run software version 3.9.3 or higher.

Certificates for tethered nodes

To configure an Aspera High-Speed Transfer Server (HST Server) with an SSL certificate, you must have:

  • the key
  • the signed root certificate, or a certificate bundle (root certificate plus intermediate certificates)

The key and certificate files must be in .pem or .crt format.

Note: The key and certificate (or certificate bundle) must be provided by an authorized, globally trusted Certificate Authority (CA) included in the Mozilla CA bundle. You cannot use a self-generated SSL certificate.

Minimum MacOS version

If you are using MacOS 10.12 or earlier, you must upgrade your OS or use Aspera Connect v3.11.

Browser support

For browser version compatibility, see the Carbon Design System web page: https://www.carbondesignsystem.com/help/faq/#which-browsers-are-supported. Carbon is the underlying design system of the Aspera on Cloud user interface.