Once you have launched the Aspera AMI, locate it under Instances in the navigation sidebar. From here, you can obtain the following On Demand server information:

• Login password, which is the string in the Instance field.
• Address, which can be derived from the Public DNS address.

From the example above, the Console On Demand can be accessed using the following information:

Enter the URL from the previous step into your web browser. When you access the URL, your browser may notify you of an untrusted connection. If this occurs, follow the on-screen instructions to accept the security certificate.

On the login screen, enter your admin name and password.

Once you are logged in and the app is enabled with a valid entitlement, click the admin user name in the Console banner and select Preferences.

Then select the User Info tab to update your admin account information:

Click Update when finished.

A transfer user account is needed to start fasp file transfers on the Aspera On Demand server. In Console, go to Nodes > edit for the 127.0.0.1 entry.

Open the Accounts tab. On the Node Accounts page, either create a new user (Add User) or edit the account configuration for the existing xfer or xfer2 user as described below.

Using xfer or xfer2: These two pre-configured accounts are provided for your use. Both are assigned to have a document root on the server in the /mnt/ephemeral/data/$username folder.

Note: The xfer and xfer2 accounts are designed as transfer accounts to be used with a web application, and therefore have been configured to require a valid token. If you want to transfer with the xfer or xfer2 account using a standard Aspera client, you will need to disable token authorization. This can be done using the account configuration settings in Console On Demand (Nodes > Edit > Accounts).

Creating a new transfer account: On the Node Maintenance page, open the Accounts tab and click the Add User button. The Creating New User page opens.

Enter the login information and click Create.

To log into the Aspera AMI instance over SSH, connect to your instance's IP address with your admin credentials. In this example, the Aspera AMI can be accessed over SSH using the following information:

Using this information, the following command may be run to log in to the Aspera AMI over SSH:

$ ssh ec2-user@77.77.77.77 -p 33001 -i ~/.ssh/asp1.pem

NOTE: The private key .pem file needs to have the correct permissions.  If you just downloaded it from AWS, then it most likely will have the wrong permissions.  If you get an error message about the key permissions when trying to SSH, change the permissions as follows:

$ chmod 600 asp1.pem

Once you have changed permissions, try to log in again. Once you are logged into the command prompt, you can use the sudo command to get root privileges, if needed. For example:

# sudo su -

The AMI instance does not store data when terminated; therefore,we advise that you back up the configuration before shutting down.

Backup: Log into Aspera On Demand Console and go to Configuration and open the Save/Restore tab. Click Download Current Configuration and save the file.

Restore: From the same page, under Restore Configuration, click Choose File and select the backup file. Click Restore to load the settings.