| Aspera Sync | 256
One-time push:
# async -L /async_log -N S3_sync -i /bear/.ssh/id_rsa --tags='{"aspera":
{"cloud-metadata":[{"location":"skye"}]}}' -K push -B /mnt/ephemeral/data/db
-d /clips -r ec2_user@192.0.04.24:/project
Aspera Sync with Basic Token Authorization
Aspera nodes that require access key authentication, such as IBM Aspera Transfer Cluster Manager or IBM Aspera
on Cloud transfer service (AoCts), can be used as synchronization endpoints by configuring the async database on
the node and authenticating the async session with a basic token. A basic token requires a docroot on the server and
allows access to all files in the docroot.
1.
On the client, set a location for the Aspera Sync snapshot database by running the following command:
# asconfigurator -x "set_node_data;async_db_dir,filepath"
2.
On the server, set a docroot for the transfer user.
Log in or SSH into the server and run the following command:
# asconfigurator -x "set_user_data;user_name,username;absolute,filepath"
3.
Create an Aspera access key.
ATC Manager: Open the Cluster Manager web UI. Click your cluster and click the Access Keys tab. Click New
and fill in the required information (for a description of the fields, see the Aspera Transfer Cluster Manager Admin
and Usage Guide).
AoCts: See https://ibm.ibmaspera.com/helpcenter/transfer-service/managing-access-keys/transfer-service-access-
keys.
4.
Create the basic token from the access key ID and secret.
Run the following command to encode the access key ID and secret in base64.
# echo -n access_key_id:secret | base64
The basic token looks similar to the following:
ZGlEZXVGTGNwRzlJWWRzdnhqMFNDcTRtT29oTkpUS3ZwNVEyblJXakRnSUE6YXNwZXJh
If the basic token breaks across lines in the output, rerun the command using the -w0 option to remove the line
break. For example:
# echo -n diDeuFLcpG9IYdsvxj0SCq4mOohNJTKvp5Q2nRWjDgIA:aspera | base64 -w0
5.
Run a synchronization, using the basic token.
Run async with the -W option or set the ASPERA_SCP_TOKEN environment variable. For example,
# async -N atcm_sync -d /images -r lion@10.0.0.1:/data/images -K push -W
"Basic
ZGlEZXVGTGNwRzlJWWRzdnhqMFNDcTRtT29oTkpUS3ZwNVEyblJXakRnSUE6YXNwZXJh"
If you are synchronizing with an ATC Manager node, specify its location as its IP address, rather than the DNS
name, to ensure that the file is transferred to the correct node.
To Next Page
Loading...
Need help?
General