Follow the instructions in
the Aspera Transfer Cluster
Manager Admin Guide for AWS: Launching the ATC Manager AMI to create
a new ATC Manager instance. Name the instance with the version of ATC Manager to
avoid confusion.
Use the following custom script to connect it to your RDS
and ELB, making sure "restore"
is set to
true
and replacing
your_rds_endpoint_url and
your_elb_name with their actual
values.
{
"restore": true,
"statestore_backup_period": "1m",
"database": {
"host": "your_rds_endpoint_url",
"port": 3306,
"user": "db_username",
"password": "db_password"
}
}
-----SCRIPT-----
#!/bin/bash
# assign elastic load balancer
elb="your_elb_name"
curl="curl -sS http://169.254.169.254/2014-11-05/"
region=$($curl/dynamic/instance-identity/document/ | jq --raw-output '.region')
instance_id=$($curl/meta-data/instance-id)
aws elb register-instances-with-load-balancer --region="$region" --load-balancer-name "$elb" --instances "$instance_id"
elb_dnsname="$(aws elb describe-load-balancers --region="$region" | jq --arg elb "$elb" --raw-output '.LoadBalancerDescriptions[] | select(.LoadBalancerName == $elb) | .DNSName')"
echo "$(jq --arg elb_dnsname "$elb_dnsname" '.private_ip |= $elb_dnsname' /opt/aspera/atcm/etc/atc-api.conf)" > /opt/aspera/atcm/etc/atc-api.conf
Note: In order
to use this script, your cluster manager needs the ELB IAM policy.