IBM Aspera HST Admin Manual page 254

• An IBM Aspera On Demand instance in AWS S3, or HST Server for Linux or Windows version 3.7.3 or later
installed on a virtual machine instance in AWS with Trapd enabled. For instructions on setting up a HST Server
in the cloud, see the High-Speed Transfer Server Admin Guide for Linux: Enabling AWS EC2/AWS S3 Using the
Command Line.
• The S3 instance must have an On Demand entitlement and a Aspera Sync-enabled license.
• The async binary must be installed on both the source and destination server.
• Configure the S3 instance, or both S3 endpoints if you are running an S3-to-S3 synchronization, as described in
the following steps.
1. SSH into your instance as root by running the following command.
The command is for Linux but also works for Mac. Windows users must use an SSH tool, such as PuTTy.
# ssh -i identity_file -p 33001 ec2-user@ec2_host_ip
2. Elevate to root privileges by running the following command:
# su -
3. Set an S3 docroot for the system account user that will be used to run async.
# asconfigurator -x "set_user_data;user_name,username;absolute,s3://
s3.amazonaws.com/bucketname"
If you are not using IAM roles, then you must also specify the S3 credentials in your docroot:
s3://access_id:secret_key@s3.amazonaws.com/my_bucket
By setting the docroot for the system user, the account becomes an Aspera transfer user.
4. Set database and log directories for async.
These directories must be located in /mnt/ephemeral/data. The /mnt/ephemeral/ directory is no-
cost ephemeral storage that is associated with your instance. Aspera recommends creating a directory to use
that is named for the transfer user, and giving the transfer user write access. For example, if the transfer user is
ec2_user, run the following commands to create the directory /mnt/ephemeral/data/ec2_user, create
the database and log subdirectories, give ec2_user write access, and set the directories as the location for the
database and logs:
# mkdir /mnt/ephemeral/data/ec2_user
# mkdir /mnt/ephemeral/data/ec2_user/db
# mkdir /mnt/ephemeral/data/ec2_user/log
# chown -R ec2_user /mnt/ephemeral/data/ec2_user
# asconfigurator -x "set_node_data;async_db_dir,/mnt/ephemeral/data/
ec2_user/db"
# asconfigurator -x "set_node_data;async_log_dir,/mnt/ephemeral/data/
ec2_user/log"
Examples of Sync to or from S3
Note: If the client is on the cloud storage host, the following options are required:
• The log directory and local database directory must be specified by using the -L and -b options.
• The --apply-local-docroot option must be used in order to transfer content into the object storage, rather
than the local disk.
The following examples include the optional arguments --transfer-threads, --local-fs-threads, and
--remote-fs-threads, which improve performance when one or both endpoints are in cloud storage.
One-time push from local disk to S3:
| Aspera Sync | 254