How to enable your Aspera Shares On Demand 3.x to use S3 for storage

 

Summary

Aspera Shares on Demand 3.x  supports the ability to use S3 as storage.  This article steps you through the process of modifying your Aspera Shares On Demand, or your Aspera Server on Demand (with Shares option) 3.x to support this option.

 

Prerequisites

This article assumes the following:

  • You have purchased and booted up Aspera Shares On Demand 3.x (SOD) or Aspera Server On Demand with Shares (3.2.2)
  • You have created an S3 bucket
  • You know your S3 Access ID and Secret Key
  • You know how to SSH as root to your Aspera On Demand Instance

 

Configuration steps

  1. Log into your Aspera On Demand as the user 'admin' (this is the initial account that is provided with your AOD instance).  

  2. Navigate to the Management Console screen, by clicking on the  'Aspera Console' link in the upper right corner of the screen.

    Shares_home_screen.png  

  3. Log into the Console (Currently the Admin login is not integrated, so you have to login again.  The default password is the Instance ID)  

  4. Navigate to the Nodes Tab  

  5. Click on the edit button for the Node 

    Console_Edit_Node.png
  6. Navigate to the Node 'Accounts' tab  

  7. Click on the edit button for the user 'xfer2'

    Console_edit_user.png  

  8. 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/

    Console_user_docroot_setting.png  

  9. Click on 'Save Changes'  
      
  10. Log into Shares as Admin, and add a new Node by clicking on the '+' symbol next to the Node menu heading. 

    Shares_add_new_node.png
  11. Add the following fields, as depicted in the screenshot below:   

    Shares_add_node_details.png
  12. Set the API password.  (the default password is the instance ID.)  

  13. Browse the newly added node (S3 Storage) by clicking on it, and confirm that you can now see the contents of your S3 bucket  

    shares_browse_new_node.png
 
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
 
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk