Set up load balancing for on premise setup of Enhanced Audio/Video (WebRTC)

Last updated on 30 November 2022

Set up load balancing for on premise setup of Enhanced Audio/Video (WebRTC)

The purpose of this document is to explain setting up load balancing for on prem setup of Enhanced Audio/Video.

As an example, we will use the AWS Application Load Balancer, but the same logic can be applied to any other load balancer.

This is a simplified diagram of our example setup:

DiagramDescription automatically generated

We have 3 types of nodes: signaling, media and recording, and in this example we have the Adobe Connect 12 server in the same network, so our load balancer does not need to be exposed to the internet (internal).

The load balancer has 3 listeners:

HTTP port 80 – used by media servers to connect to signaling nodes
HTTPS port 443 – used by Adobe Connect 12 server to connect to the Enhanced Audio/Video cluster
HTTP 9090 – used by the cluster admins to connect to the web interface of Liveswitch (to manage the WebRTC stack)

While creating the load balancer we will also create first target groups for the first listener, we will add the other later.

Since one of our listeners is HTTPS we will need a certificate. To achieve this we will create a DNS record that will point to the load balancer, and use the certificate for the domain.

Creating the Load balancer

Open the AWS console then navigate to EC2 console and to Load Balancers section.
Select Create Load Balancer and then select Application Load Balancer.
Name the load balancer and select Internal.
Select the VPC and subnets where your signaling nodes are placed.
Select or create the security group that will allow the traffic to ports 80, 443 and 9090 from the local network.
For the first listener leave the protocol as HTTP and port 80 and select Create target group.
A new tab will open with the target group creation dialog. Select Instances as type, give target group a name, set HTTP protocol, port 18443 and select the VPC where your nodes reside.
For health checks, enter the path /health.
Select Next. Then select your signaling nodes from the list and select Include as pending and Create target group.
After closing the tab and returning to the load balancer creation page, click the refresh button in the listener section and select the target group that you just created.
Select Create load balancer.

Additional listeners and target groups

On the Load balancers console, select the load balancer that you have created.
Select the Listeners tab and select Add listener.
Change the protocol to HTTPS, port to 443, select the same target group that you used for the first one and select the certificate for HTTPS.
Select Add. For the last listener, select Add listener again.
Select HTTP port 9090 and select Forward to as action.
Select Create target group and repeat the steps from the previous section for creating the target group, but with target port 9090.
One more setting that is different on this target group is the health check, since the traffic port is different, so we need to set override.
Select the target group that you have created.