How to upgrade Enterprise Server to version 3.4 in your AWS Aspera On Demand


This article is for customers who have Aspera On Demand (APOD, SOD, FOD and SHOD) running Enterprise Server v3.0 or v3.1.0 and would like to upgrade to Enterprise Server v3.4.

NOTE: If you don't know your Enterprise Server version, you can SSH into your AMI host from a Terminal or a Command Prompt and run ascp -A to find out the version information.

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


Upgrade Procedure

(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 -

   NOTE: make sure the permission of the key is set to 400.


(2) Download the ES 3.4 package from our website

You can use the 'wget' utilty to download the server RPM, as follows:

# wget


(3) Manually stop asperanoded, asperatrapd and asperalee

       # /etc/init.d/asperanoded stop
      # /etc/init.d/asperatrapd stop
      # /etc/init.d/asperalee stop

    Then check to make sure they are stopped:

    # ps aux | grep aspera

    You should not see any of these processes running:

    If they are still running, kill the processes by running

      # kill -9 [PID of the process]


(4) Install Enterprise Server v.3.4

     # rpm -Uvh aspera-entsrv-


 (5) Verify your Enterprise Server has been successfully upgraded to v.3.4

  # ascp -A


NOTE: in case of FOD (i.e.) old installations provided  a transfer account (faspex) with browse capability disabled. The new aspera component requires that this user has that capability.

If it is not the case,  Faspex WEB page can display an error message like " Server configuration, access denied"

If happens after an upgrade, please login to the instance via ssh, get root privileges and execute:

      # /opt/aspera/bin/asconfigurator -F 'set_user_data;user_name,faspex;dir_allowed,true' 
# /etc/init.d/asperanoded restart





Powered by Zendesk