Aspera On Demand (AOD) release v.3.2.2 and higher provides you the option to stop your instance if the instance is not in use. When you stop the instance, Amazon releases the public and private IP addresses for the instance, and assigns new ones when you restart it. A new IP address is assigned to your instance every time you start your stopped instance. Since Faspex and Transfer server doesn't get updated with the new IP address automatically, we recommend you to apply AWS Elastic IP (EIP) to your Faspex On Demand (FOD). This article shows you what are the required configuration steps after you stop and start your FOD instance.
This article assumes the following:
- You have purchased and booted up Aspera Faspex On Demand v.3.2.2 or higher
- You can SSH as root to your Aspera On Demand Instance
- You apply EIP to your Aspera Faspex On Demand instance. To learn how to use EIP with your AOD, please see this article.
1) Re-associate EIP to your FOD instance
Log in to your AWS Management Console and navigate to AWS Elastic IP menu. Select the IP address, click "Associate Address" and choose the instance ID of your FOD.
2) Update Transfer Server address in FOD Web UI
Log in to your FOD Web UI as Admin. Go to Server -> Configuration ->Transfer Server and enter your EIP in the "Primary transfer address or name" field.
3) update the aspera.conf file
a) SSH into your FOD server and change to be root user. If you don't know how to do so, please see this article.
b) The aspera.conf file contains a <server_name>...</server_name> parameter, which the Aspera Server uses to tell connecting browser plug-in clients what hostname/IP should be used for FASP transfers with the server. You will need to update the value in the <server_name> tag with the EIP.
# vi /opt/aspera/etc/aspera.conf
For example, change
4) update web server address
# asctl apache:hostname xx.xxx.xxx.xx
where xx.xxx.xxx.xx = your EIP