Get Started with an Aspera Transfer Server

As a server, HSTE 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. The following steps describe how to prepare your system as a server.

1. Review the system requirements and install HSTE.
   See Requirements and Installing HSTS
2. Secure your server.
   1. Configure your firewall (see Configuring the Firewall).
   2. Change and secure the TCP port (see Configuring the 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 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 Transfer Users.
   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 or by user. You can set bandwidth caps and limit the total number of transfers. For more information on user-specific settings, see aspera.conf - Transfer Server Configuration.

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

5. Set up file validation and processing, if needed.
   You can protect your server against malicious software in uploaded files by using out-of-line file validation or inline file validation. For more information, see Out-of-Transfer File Validation and Inline File Validation.

   You can configure your server to run other customized scripts at specific transfer events. For more information, see Automated Execution of Lua Scripts with Transfer Events.

6. 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.