This procedure describes how to enable AtScale to use an AWS Load Balancer.
AtScale only supports TCP for our thrift services. We do support HTTP for our XMLA protocol but if customers want to deploy our thrift services for their JDBC connection, then you can only use TCP. To simplify the process, only select Load Balancer (LB) communication protocol via TCP.
The setting is the same regardless of TLS/non TLS, because we don’t do any TLS termination at the LB level but at the AtScale host. The certificate must be a valid generic host name for their domain.
Security Group
First, you need to set up proper security groups. Ensure your LB can access the same host and ports for AtScale. The ports that you need to use are 10500, 10502, 10503, and 11111; those are four ports that you need to map in your LB.
Target Group
Create a target group for your host.
You can use either instance or IP address.
Name your target groups to identify which one belongs to which port.
Select the right VPC, and make sure you use the one you created in your security group.
You can add/modify the health check, but for the most part leave these ports and timeout settings default.
After you complete the four ports for your target group, move to the next step.
Load Balancer Type
Use the first method - the Network Load Balancer.
You can either select internet-facing or internal scheme, depending on what the customer network security profile is. In this example, we use a simple internet-facing scheme because there isn't any other network profile in the security group.
Network mapping
This selection is important for selecting the right region where the host resides. Make sure to select the right security group (VPC) also.
Listeners
Select the correct listener to the port that you assigned. These are the target groups that you’ve created in the previous step.
The LB creation step is now complete.
As a verification, review the basic configuration. You’ll see that all of the host and target groups have been mapped.
Next, set up AtScale with the correct DNS name in the YAML file that points to your LB name.
Classic Load Balancer
The first step is to create a classic load balancer.
Add all four ports needed. In this scenario, we are using a few mixed examples of adding HTTP to HTTP and TCP to TCP. You can do so if the protocol you want only accepts HTTPS.
The next step is assigning a security group.
The next step is to assign a health check.
The last step is to add EC2 instances.
Review the configuration. You are done with the LB classic setup.
If you only have one node, make sure the port configuration has stickiness enabled so it doesn’t have to ping the right host.