Initiating high-speed transfers

Aspera High-Speed Transfer Server (HSTS) allows an unlimited number of concurrent users to transfer files of any size at high speed using an Aspera client.

HSTS configuration and transfer testing

After you have finished installation (see High-Speed Transfer Server deployment), you need to configure HSTS itself. You should also test a transfer to verify successful configuration.

Architectural overview

HSTS server is deployed using number of different pods. In some cases the pods contain a number of containers.


The Fast Adaptive Secure Protocol (FASP) is the high-speed, secure data transfer protocol on which HSTS is based. FASP has built-in security mechanisms that do not affect the transmission speed.

The transfer engine that is used on both the server and client side to transmit data using the FASP protocol. An incoming connection is routed to ascp for transfers.
The daemon that serves up the Node API, which is the HSTS primary REST API. The API has multiple functions, including authorizing transfers, transfer initiation, transfer status, file system browsing, setting permissions, and file system operations.
Aspera Event Journal daemon reports events, which are primarily transfer-related events. The ascp pod writes the events to Redis during a transfer. The events are read from the Redis database, for example, when HSTS is configured for Event Streams integration.
Proxy Pods
Proxy pods are used to expose the ascp and asperanoded pods to the outside world. The TCP proxy is used to proxy the SSH connection. The HTTP-proxy pod is used to proxy the asperanoded pod.
Other Pods
  • engine aggregates cluster utilization based on aejd reporting.
  • tcp-scheduler is the Loadbalancer for TCP traffic. It uses the engine service to get live information about cluster utilization.
  • http-scheduler is the Loadbalancer for HTTP traffic. It uses the engine service to get live information about cluster utilization.