Setting up HTTP fallback on Aspera Shares On Demand


This article shows customers how to set up direct HTTP Fallback with the Aspera On Demand to S3.  When either the required ssh port or UDP port 33001 is blocked, transfer falls back to HTTP on TCP 8080 or HTTPS on TCP 8443.


 HTTP fallback is a Aspera file transfer service which uses HTTP as the file transfer protocol. This service is available if you happen to be one of the unfortunate few whose Network Administrators do not allow you to do FASP Transfers. This service comes as part of the Aspera Enterprise Server installation package. 



This article assumes the following:

  • You have purchased and booted up Shares on Demand (SHOD) v.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 Shares On Demand Instance
  • Both your Web Application and Transfer Server are on the same machine



1) Connect to your AMI host from a Terminal/Command Prompt via SSH as root

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


 2) Upgrade Enterprise Server to v.

# wget
# /etc/init.d/asperanoded stop
# /etc/init.d/asperatrapd stop
# /etc/init.d/asperalee stop
# rpm -Uvh aspera-entsrv-


3) Ensure the transfer user has a doc root set to a S3 bucket on the Transfer Server.   

If you are not sure how to set transfer user's doc root to a S3 bucket, please see this article.


4) Set http_server in aspera.conf

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

and add the following section before </CONF> in the configuration file.



5) Restart asperanoded

# service asperanoded restart


6) Set encryption to aes-128

Log on to Shares Web UI as admin, go to Admin -> Transfers -> Encryption and select AES-128.  Save.



7) Start asperahttpd

Since asperahttpd listens on TCP 8080, make sure no other process is listening on this port before you start asperahttpd.

# /etc/init.d/asperahttpd start 
Powered by Zendesk