Enabling Faspex On Demand to use S3 for package storage


This article is for customers who want to enable their v.3.2.1+ Faspex on Demand (FOD) to use S3 storage.  If you are still investigating Aspera On Demand options and want to learn more, please view the Aspera Cloud site for more info.



This article assumes the following:

  • You have purchased and booted up Faspex On Demand 3.2.1 (FOD)
  • You have created an S3 bucket
  • You have booted your AMI using IAM roles, or know your S3 Access ID and Secret Key
  • You know how to SSH as root to your Faspex On Demand Instance



1) Connect to your v.3.2.1 FOD from a Terminal/Command Prompt via SSH as root

#  ssh -i [customer's perm] -p 33001 ec2-user@[ec2 host IP]
# sudo su -

If you are not sure how to login to your Aspera Server, please see this article.

2) Edit your aspera.conf

open /opt/aspera/etc/aspera.conf file and find the user faspex section (see note below regarding how to use 'asconfigurator' instead of vi.)

# vi /opt/aspera/etc/aspera.conf



If you are using IAM roles to access S3, then under the <absolute> tab, replace /home/faspex/faspex_packages to 

s3://s3.amazonaws.com/BucketName/   Otherwise, set the new value to: s3://AccessKeyID:SecretKey@s3.amazonaws.com/BucketName/   

NOTE 1: your secret key might contain one or more "+", "=" or  "/"  symbols. Replace all "+" with "%2B", all "=" with "%3D" and all  "/"  with "%2F"

NOTE 2:   You can also use the command 'asconfigurator' to configure aspera.conf.  Here is an example


# asconfigurator -x "set_user_data;user_name,faspex;absolute,s3://s3.amazonaws.com/BucketName"

Here is what the configuration would look like (if you have used the Access Key and Secrete Key)





3) Restart the node server

   # service asperanoded restart      

4) Restart the asperahttpd

   # service asperahttpd restart      
Powered by Zendesk