Configuring your transfer users to transfer to object storage

Description

You can transfer to object storage (such as Amazon S3 storage or Azure object storage) by configuring the docroot of a transfer user to point to the URI of your object storage.

Once your transfer user has the object storage docroot, you can perform usual transfer actions to upload to the storage -- such as regular transfers, hot folder transfers on Windows, async transfers, and so on.

NOTE: Your transfer server must be in the same region (e.g. datacenter) as your object storage

Instructions

1. Ensure you have your object storage credentials -- the access ID/storage account, and the access key.

2. Set the docroot of a transfer user to the URI of your object storage.

Note: Ensure you are formatting the docroot path correctly as described in this article. In particular, note that parts of these paths MUST BE URL ENCODED.

The URI for Amazon S3 is the following, where the Storage access Key needs to be URL encoded:

s3://access_id:secret_key@s3.amazonaws.com/my_bucket/my_path

If your instance is using IAM roles for S3 access, then the syntax would be the following:

s3://3.amazonaws.com/my_bucket/my_path

The URI for Azure is the following, where the Storage access Key needs to be URL encoded:

azu://storage_account:storage_access_key@blob.core.windows.net/path/to/blob

You can set the docroot of a transfer user by running the following command:

asconfigurator -x "set_user_data;user_name,transfer_user;absolute,object_storage_URI"

3. Restart asperanoded

Linux
# service asperanoded restart
or
# /etc/init.d/asperanoded restart

Mac OS X
$ sudo launchctl stop com.aspera.asperanoded
$ sudo launchctl start com.aspera.asperanoded

Windows
> sc stop asperanoded
> sc start asperanoded
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk