Getting Started with the Aspera Trapd Service

Trapd is the Aspera service that enables Aspera servers to write to cloud or on-premises object storage, as well as Hadoop Distributed File System (HDFS). Trapd is currently only available with Enterprise Server for Linux. The Enterprise Server should be in close proximity to the object storage to reduce any latency.

Requirements and Set Up

Trapd is included with Aspera On Demand applications and Aspera Enterprise Server for Linux 64-bit. Trapd is enabled in Aspera On Demand, but is disabled by default in Enterprise Server. Trapd can be enabled by running the following command:
```
# /opt/aspera/bin/astrap-config.sh enable
```
The Aspera server must be configured to access the object storage. For stand-alone servers, this configuration is typically done when setting the docroot in aspera.conf (see Setting Docroots for Object Storage and HDFS). The Aspera client may also specify the object storage path and credentials as part of the transfer command (see Ascp Transfers with Object Storage and HDFS). For multi-tenant use cases, such as the Aspera Transfer Cluster Manager (ATCM) or the Aspera Transfer Service (ATS), configuration is done as part of creating an access key (see the documentation for those products for more information).

Configuration

For general information about configuring Trapd, see General Trap Configuration Reference.

For information about using Trapd features, see Working with Trap.

Trapd works with many types of storage and comes packaged with templates of configuration files for all supported storage types. For more information, see the topics relevant to your storage type.