Tether Your Aspera Transfer Server to Aspera on Cloud
To attach your own user-managed High-Speed Transfer Server (HSTS) to Aspera on Cloud, you must configure it as a tethered node. This article covers prerequisites and provides a map of the process. Linked articles describe the configuration steps in detail.
To tether (attach) your HSTS node to Aspera on Cloud, you must configure the transfer server for communication with Web applications and set up a user account on the server so that it conforms with AoC requirements. Then you must protect your Aspera on Cloud transfer nodes with an Nginx reverse proxy.
Prerequisites
Before you can configure the transfer server for use as a tethered node with AoC, you must have the following:
- The Aspera High-Speed Transfer Server (latest available version) installed on a supported platform, and configured for your entitlement or license. See the IBM Aspera High-Speed Transfer Server Admin Guide for your platform.
- To connect your HSTS node to storage in the public cloud, your HSTS must be in the same region as the cloud storage you want to access through the HSTS node.
- The public DNS name of the node accessible from all internal and external clients, as well as the node itself.
- The node clock synchronized with an NTP server. For information in this regard, see the platform OS product documentation.
- A signed certificate and key from an authorized, globally trusted Certificate Authority listed in the Mozilla CA bundle installed on the node. You'll install the certificate on your node as a part of this process; see Installing SSL certificates for tethered nodes.
- Allow traffic on TCP/443 (refer to Firewall requirements for tethered nodes).
Process map
This illustration shows the required steps to tether your HSTS node to your Aspera on Cloud organization. Linked topics guide you through the process.
To start, go to Installing SSL certificates for tethered nodes.