Launching the Aspera Transfer Cluster Manager

Make sure to review the requirements before proceeding with the installation. See Reviewing Aspera Transfer Cluster Manager Requirements.

Click EC2 under the Compute section. Select AMIs from the Images section on the left sidebar. Select the private AMI provided by Aspera and click Launch.
Choose an instance type. The Cluster Manager requires at minimum a M3-medium image type. Click Next: Configure Instance Details.
Select a VPC from the Network drop-down menu and enable Auto-assign Public IPto allow access to the Cluster Manager web application from outside of the VPC.
If you are using the remote RDS database, expand the Advanced Detail section and add user data.
The configuration of the external database occurs through user data passed to the instance on startup. The user data is a JSON structure containing remote database and backup configuration:
```
{ 
    "restore": false, 
    "database": { 
        "host": "hostname", 
        "port": port, 
        "user": "username", 
        "password": "password" 
    } 
} 
```
Tip: To start a replacement instance, set "restore" to true. For more information, see Recover a Failed ATCM Instance.
Click Next: Add Storage > Next: Tag Instance > Next: Configure Security Group.

Note: Adding storage and tagging your instance are optional steps. The default root partition is 8 GB. That size is sufficient if you are using a remote database (for example, RDS). If you are using a local database and plan to run this system in production, create a larger partition (for example, 20 GB).
Select Select an existing security group and select the atc-manager and the atp-manager security groups.
For more information on the atp-node security group, see Creating the Transfer Node Security Group. For more information on the atc-manager security group, see Creating the Cluster Manager Security Group.
Click Review and Launch > Launch.