Aspera Server on Demand can be configured to use S3 as storage. This article steps you through the process of setting up a user account on your Server to access S3.
This article assumes the following:
- You have purchased and booted up Aspera Server On Demand 3.x (SOD) or Aspera Application Platform On Demand (APOD)
- You have created an S3 bucket
- You have created an IAM role (recommended), or you know your S3 Access ID and Secret Key
- You know how to SSH as root to your Aspera On Demand Instance
- You have enabled 'Password Authentication' in the /etc/ssh/sshd_config file on your Aspera server, and restarted the sshd service. NOTE: This option is disabled by default.
- Log into the Console (Currently the Admin login is not integrated, so you have to login again. The default password is the Instance ID)
- Navigate to the Nodes Tab
- Click on the edit button for the Node
- Navigate to the Node 'Accounts' tab
- Click on the edit button for the user 'xfer2'. NOTE: You can also create a new account here. This example is just showing you how to add S3 storage to your xfer2 account.
- Add the S3 docroot for that user, in the syntax: s3://ACCESSID:SECRETKEY@s3.amazonaws.com/BUCKETNAME/ If your S3 Access ID or secret key contain a slash character, e.g. '/', then you will need to encode that character, by replacing it with a %2F. If you are using IAM roles for S3 access, then the syntax will be: S3://s3.amazonaws.com/BUCKETNAME/
- Click on 'Save Changes'
- Update the password for the xfer2 user, by clicking on the 'Change OS Password'.
- Congratulations! You have completed the setup. Next you can configure your Aspera client to transfer with this server.
NOTE: It is no longer needed to restart the node service after changing the aspera.conf file. However, in some cases it is necessary to restart Aspera Noded.
If you have having issues connecting to S3, then please restart Aspera Noded.
# service asperanoded restart