General Trap Configuration Reference
When HST Server is installed in a cloud-based virtual machine, it must
be configured to support transfers to object storage and for the specific type of storage. This
section describes configuration settings that apply to all cloud storage types.
Setting Docroots for Object Storage and HDFS
Docroot path syntax for object-storage based HST Server s is typically a protocol prefix that is followed by URL-encoded storage account access credentials and a path in that storage. Some storage configuration properties can also be set in the docroot or set in the protocol-specific Trapd .properties configuration file.
URL Encoding
Docroots that point to object storage are written as URIs, in which the variable components such as access IDs, passwords and secret keys, bucket names, and paths to folders must be URL encoded.
File Restrictions for URI Paths
Restrictions are similar to user docroots in that they restrict a client's access to the file system, but they are based on matching rather than a specific path. The primary purpose of restrictions is to allow access to certain storage (for example, Amazon S3) for clients that have their own storage credentials. A restriction limits the files a client is allowed to access for browsing and transfers. Files are rejected unless they match any restrictions that are present.
Configuring for Small File Uploads
If you need to upload many small files (100 Kb or less) to object storage, Aspera recommends updating your HST Server configuration to optimize transfer speed.
Resuming Transfers to Object Storage and HDFS
File transfer resume works differently when the target is object storage, and the process depends on the storage platform. Files are transferred to object storage in parts, which are finalized into a complete object once all parts have uploaded.
Naming Constraints
Object storage types vary in their support for characters and length of file and path names. Avoid transfer problems by correctly naming storage elements.