Loading ...
close

Would you like to discuss your environment with a knowledgable engineer?

Preferred communication *

Thank you. We will be in touch with you shortly

aiScaler and Elastic Load Balancer (ELB)

In this post I will walk you through possibilities of setting up aiScaler with Elastic Load Balancer (ELB) from Amazon Web Services (AWS). More specifically I will talk about the followings:
– aiScaler behind multiple Elastic Load Balancers, how can this work and where you could use it;
– using aiScaler instead of multiple Elastic Load Balancers;
– Elastic Load Balancer behind aiScaler.

aiScaler behind multiple Elastic Load Balancers.

Some of our customers were interested in this particular scenario, they had multiple Elastic Load Balancers that each would serve as one SSL termination, and each of them would go to the same origin, that origin being an aiScaler machine. This set up is easily achieved by setting up aiScaler as instance in Elastic Load Balancer configuration, like in the image below:

ELB-with-aiScaler

Setting up aiScaler instance in each Elastic Load Balancer configuration will achieve in the end the goal of having one aiScaler instance behind multiple Elastic Load Balancers.

Using aiScaler instead of multiple Elastic Load Balancers

In the scenario above users had to have multiple Elastic Load Balancers because of the need to have multiple SSL terminations. In aiScaler you have this possibility, you can add one SSL certificate per IP/port pair, thus creating multiple SSL terminations in one instance. This way users can simplify their stack with having just one aiScaler instance instead of multiple Elastic Load Balancers. There are 2 ways to achieve this:
– having multiple SSL certificates bound to the same IP address but different ports in aiScaler, like in the following configuration example for example.com and domain.com:

listen https 1.1.1.1 443 /path/to/example.com.cert /path/to/example.com.key AES256-SHA:RC4-MD5 example.com
listen https 1.1.1.1 8443 /path/to/domain.com.cert /path/to/check.com.key AES256-SHA:RC4-MD5 domain.com

– binding multiple IP addresses to the aiScaler instance through the Amazon Web Services (AWS) console and then bingind a certificate to each IP address, like in the following configuration example for example.com and domain.com:

listen https 1.1.1.1 443 /path/to/example.com.cert /path/to/example.com.key AES256-SHA:RC4-MD5 example.com
listen https 1.1.1.2 443 /path/to/domain.com.cert /path/to/check.com.key AES256-SHA:RC4-MD5 domain.com

Elastic Load Balancer behind aiScaler

There can be scenarios where you might want to place aiScaler in front of an Elastic Load Balancer. This can be for example if you put an Elastic Load Balancer inside a Virtual Private Cloud (VPC) and put the aiScaler instance on the edge of the Virtual Private Cloud (VPC) from where users would connect to the origin instances, like in the following image:

aiScaler-before-ELB

Here you also create a layer of security for your origin servers. You just need to add the Elastic Load Balancer as origin in aiScaler configuration and the set up is complete.

If you have any questions related to this post or any other one, you can always take advantage of TWO FREE HOURS SUPPORT for every installation. This usually includes a full installation and basic configuration for your application specifics.

Have fun using aiScaler 😉

US 1 (408) 744-6078   EU +44 20 7993 4587