Aspera Requirements

This includes FAQs regarding prerequisites and general requirements for use.

Question Answer
What is required for Aspera Upload Acceleration use? Multiple requirements must be met:
  • “NetStorage::Aspera” must be on your contract. It's included by default with all contracts that have NetStorage.
  • Aspera must be enabled for at least one NetStorage Storage Group Upload Account, on that contract.
  • Each Upload Account must be configured with an SSH Key--the Public instance of the key must be properly associated with the Upload Account, while the matching Private instance must be applied via the Aspera Client in use.
  • An appropriate version of Aspera software must be installed:
    • Aspera Client - Must be v3.3.4 or later
    • ASCP CLI - Must be 3.3.x or later (3.5.1 or later is recommended)
What is the “Akamai License” for Aspera and where is it required? Aspera Upload Acceleration uses a separate, third party component (the “Aspera Client”) to perform file transfer. This component requires a specific license, but it doesn't necessarily need to be the “Akamai License”.

If you have purchased Aspera Upload Acceleration directly from Akamai, you will be provided with the Client as well as the specific Akamai License.

If you have purchased a supported client from Aspera, you use a license provided to you by Aspera.

What ports does Aspera Upload Acceleration use? Aspera requires two ports:
  • TCP 22 - For ssh connection and file browsing, and
  • TCP/UDP 33001 - For file transfers
Does Aspera Upload Acceleration have a minimum performance requirement (that is, is my client/network too slow)? Minimum performance requirements are 300 mbits per second, per connected session. If your client system or network is incapable of transfer rates of at least this speed, you should look into a traditional NetStorage transfer method, such as FTP, SCP, etc.).