Creating an Internal Elastic Load Balancer in AWS

If you run the Aspera Transfer Cluster Manager on a private VPC, Aspera recommends using an internal elastic load balancer (ELB). The Cluster Manager instance does not need to be set up to create a load balancer for it.

From the AWS console, go to Compute > EC2 > Load Balancers.
Create a new load balancer.
Click Create Load Balancer. Select Classic Load Balancer and click Continue.

Configure the load balancer.

Load Balancer name: Name the load balancer atc-internal-elb.
Create LB inside: Select the VPC where you plan to run your Cluster Manager from the drop-down menu.
Create an internal load balancer: Select the checkbox.

Listener Configuration: Create the following configurations:

Load Balancer Protocol	Load Balancer Port	Instance Protocol	Instance Port
TCP	22	TCP	22
TCP	5001	TCP	5001
TCP	5002	TCP	5002

Available subnets: Select the subnets where you plan to run your Cluster Manager by clicking the add (+) icon.

Click Next: Assign Security Groups.

Assign Security Groups.
Select your atc-manager security group, or create a new security group. For instructions, see Creating the Cluster Manager Security Group.
Click Next: Configure Security Settings.
Ignore the security warning and click Next: Health Check.
Update the Health Check.
Click the drop-down menu for Ping Protocol and select HTTPS. Change the Ping Port from 80 to 443.
Click Next: Add EC2 Instances.
Configure EC2 Instances.
Select your Cluster Manager if it is already set up. If it is not yet available, you can add it later by going to Compute > EC2 > Load Balancers, selecting the atc-internal-elb load balancer, clicking the Instances tab, clicking Edit Instances, and adding the Cluster Manager instance.
Leave cross-zone load balancing and connection draining enabled.

Click Next: Add Tags.
Add any required tags, then click Review and Create.
Confirm the configuration that is displayed on the Review page is correct, then click Create.
Once you receive the notification that your load balancer was created, click Close.
View the load balancer status and test it.
Select the atc-internal-elb load balancer and go to Description. The status row indicates if your instances are in service. If not, they might still be in the registration process or not yet added.
Once your Cluster Manager instance is in service, you can test it by entering the DNS name (for example, atc-internal-elb.us-west-2.elb.amazonaws.com) in a web browser. If the load balancer is working, the default page of your server is displayed.