Transfers with Aspera On Demand and Object-Storage-Based Aspera Servers
Tranfers with Aspera On Demand servers or Enterprise Servers located in object storage must provide credentials to the object storage in one of the following ways:
- Specify the storage password or secret key in the transfer user's docroot. (Preferred method)
- Set the storage password or secret key as an environment variable.
- Specify the storage password or secret key in the command line.
With Docroot Configured: Authenticate in the Docroot
If your transfer user account has a docroot set that includes credentials or credentials are configured in the .properties file, ascp transfers to and from Alibaba Cloud, Amazon S3, IBM COS - S3, Google Cloud Storage, Akamai, Softlayer, Azure, and are the same as regular ascp transfers. For command syntax examples, see Ascp General Examples.
For instructions on configuring a docroot for these types of storage, see Aspera
Enterprise Server Admin Guide (Linux): Docroot Path Formatting for Cloud, Object, and HDFS
Storage. You are prompted for the transfer user's password upon running these commands
unless you have set the ASPERA_SCP_PASS
environment variable or are using an
SSH key, as described previously.
With No Docroot Configured: Authenticate with Environment Variables
You can set an environment variable (ASPERA_DEST_PASS
) with the storage
password or access key using the command below:
$ export
ASPERA_DEST_PASS = secret_key
With this and ASPERA_SCP_PASS
set, run ascp with the
syntax listed in the table above, but you do not need to include the storage password or access
key, and are not prompted for the Aspera password upon running the command.
ASPERA_DEST_PASS
variable is not applicable to Google Cloud Storage
or Amazon S3 using IAM roles.With No Docroot Configured: Authenticate in the Command Line
If you do not have a docroot configured and do not set an environment variable (described
previously), you must authenticate in the command line. In the examples below, you include the
storage password or secret key as part of the destination path. You are prompted for the
transfer user's password upon running these commands unless you have set the
ASPERA_SCP_PASS
environment variable or are using an SSH key, as described
above.
Storage Platform | ascp Syntax and Examples |
---|---|
Alibaba Cloud | Aspera recommends running ascp transfers with Alibaba Cloud with a docroot configured. |
Amazon S3 |
Upload example:
Dowload syntax:
Download example:
|
Azure | These examples are for Azure blob storage. For Azure Files, use the syntax: azure-files://storage_account:storage_access_key@file.core.windows.net/share . Aspera recommends running
ascp transfers with Azure Data Lake Storage with a docroot
configured.Upload syntax:
Upload example:
Dowload syntax:
Download example:
|
Google Cloud Storage | Note: The examples below require that the VMI running the Aspera server is a
Google Compute instance.
Upload example:
Dowload syntax:
Download example:
|
HDFS | Aspera recommends running ascp transfers with HDFS with a docroot configured. |
IBM COS - S3 | Upload
syntax:
Upload example:
Dowload syntax:
Download example:
|
IBM Cloud Object Storage (COS) - Swift | Aspera recommends running ascp transfers with IBM Cloud Object Storage (COS) - Swift with a docroot configured. |
OpenStack Swift | Upload
syntax:
Example Upload:
Dowload syntax:
Download example:
Note: Swift
requires additional Trapd configuration settings that can be included as queries
attached to the docroot, with the format
docroot?setting. For example, for an upload to IBM COS - Swift, the path is written as follows:
|