Get Started with an Aspera Transfer Server

As a server, the Aspera transfer server is a remote endpoint that accepts authenticated connections from Aspera client applications and that participates as a source or destination for authorized transfers.

Your server can also take the role of a client and connect to other Aspera servers to initiate transfers. For information about preparing your system for that role, see Get Started as a Transfer Client.

To prepare the system for its role as a server:

  1. Review the system requirements and install Enterprise Server.
    See Requirements and Product Setup.
  2. Secure your server.
    1. Configure your firewall (see Configuring the Firewall).
    2. Change and secure the TCP port (see Securing Your SSH Server).
    3. Determine if you want to use server-side encryption at rest. See Server-Side Encryption at Rest (EAR) for instructions on configuring this in the GUI or aspera.conf - Server-Side Encryption at Rest (EAR) for instructions on configuring this from the command line.
    You can also restrict user access to your server, which is described in a later step.
  3. Add users and configure their access.
    Aspera client applications authenticate to the server using operating system accounts on the server. For example, if a remote client user, "marketing_mgr" wants to transfer with the server, add marketing_mgr as a system user on the server and then add marketing_mgr as an Aspera transfer user. To secure your server, restrict marketing_mgr's access to only certain directories on the server (set a docroot), set transfer permissions, and set the default shell as aspshell.
    1. For instructions on adding users, assigning users to aspshell, and setting a docroot, see Setting Up Users for instructions using the GUI or Setting Up Transfer Users (Terminal).
    2. If you prefer to have your users authenticate to the server using SSH keys rather than with passwords, gather their public keys and install them on the server. For instructions, see Setting Up a User's Public Key on the Server.
  4. Configure transfer settings and control bandwidth usage.
    Aspera FASP transfers can be configured globally, by group, or by user. You can set bandwidth caps and limit the total number of transfers. For more information on user-specific settings, see Configuring the Transfer Server (GUI) or Configuring the Transfer Server (Command Line).

    You can also set "virtual" bandwidth caps that can be assigned to incoming or outgoing transfers by group or by user. For more information, see Controlling Bandwidth Usage with Virtual Links (GUI) or Controlling Bandwidth Usage with Virtual Links (Command Line).

  5. Set up email notifications and other file processing, if needed.
    Email notifications triggered by the start or end of a file transfer or transfer session can be configured with a built-in pre/post-processing script (see Setting Up Email Notification). The email notifications that can be configured in the GUI are only available for transfers initiated by your server in a client role (see Configuring Transfer Notifications).

    You can configure your server to run other customized scripts when an individual file transfer starts or stops, or when a transfer session starts or stops. For more information, see File Pre- and Post-Processing (Prepost).

    You can protect your server against malicious software in uploaded files by using inline file validation. For more information, see Configuring Inline File Validation.

  6. If you plan to add your server as a node in another Aspera product, configure your server as required by that product.
    For more information, see Configuring for Other Aspera Products and the Admin guide for that product.
  7. If your server is installed on a virtual machine in object storage, update the configuration as required.
    For more information, see Configuring for Object Storage and HDFS.
  8. Test that a remote client can access and transfer with your server.
    For instructions, see Testing a User-Initiated Remote Transfer. If you have problems, review the topics in Troubleshooting.
Once you confirm that remote clients can access your server, your basic server set up is complete.