Background Information

HAProxy, or High Availability Proxy is used by RightScale for load balancing in the cloud.

HAProxy is installed with RightScale load balancer ServerTemplates. Load-balancer servers are also known as front-end servers. Generally, their purpose is to direct users to available application servers. A load-balancer server may have only the load balancer application (HAProxy) installed or, in rare cases, it may be an application server in addition to a load balancer, which is not a recommended configuration.

Each load-balancer server has its own public IP address (typically an Elastic IP address in the case of Amazon EC2 clouds), but shares the same fully qualified domain name (e.g. host.domain.tld) as the other load-balancer servers in your configuration.

Example: Server A: (IP address:, Server B: (IP address:

HAProxy can be used with HTTP and HTTPS traffic.

Get more details in our white paper: Load Balancing in the Cloud: Tools, Tips, and Techniques.


HTTP Using Port 80

  1. The user's web browser sends a request to the load balancer over port 80, using the fully qualified domain name/URI (e.g. http://host.domain.tld:80).
  2. The Domain Name System (DNS) resolves the URI to one of the static IP addresses associated with that fully qualified domain name. (All load-balancer servers share the same fully qualified domain name but have unique static IP addresses.) Example: There are two load balancers, Server A and Server B. DNS directs the first client request to Server A, the second to Server B, the third to Server A, and so on.

  3. If a load-balancer server is unavailable, the request to that server will time out. However, when this happens, most browsers resend the client request to DNS, and the request is directed to the second load balancer in this case. Thus, if one of your two load-balancer servers is unavailable, it will result in half of the traffic to your site having a slower initial load time.

  4. Because each load-balancer server has the Apache HTTP Server configured to monitor port 80, Apache processes all incoming client requests to your load-balancer servers.

  5. Apache's virtual host configuration has a rewrite rule that sends the request to (that is, localhost on port 85).

  6. HAProxy is configured to monitor, and receives the request.

  7. Referencing the load-balancer pool in its configuration file, HAProxy determines the application server to route the client request to, based on a round-robin system. This server receiving the request is generally part of an auto-scaling array consisting of dedicated application servers. HAProxy forwards the request to the server port referenced in its configuration file (generally port 80).

HTTPS Using Port 443

When you configure a server to use HTTP Secure (HTTPS), the load-balancer server performs SSL termination for incoming client connections as described in the FAQ titled How do I set up SSL?.

Required Boot Scripts

LB HA proxy install. Installs HAProxy. The following inputs are used with this RightScript.

Note: Inputs prefixed by OPT\_ are typically optional, not mandatory.


Optional for testing, but required for production. This references a path from www root to a web page that should return an OK 200 response. The contents of the page are not important, but its name should be unique (preferably containing a random number). The same page is used for all application servers to determine whether the server is running (up). The page contents can be as simple as the text, OK. For example, if the page were and its content was just two letters, OK, you would simply specify a HEALTH_CHECK_URI of: /hlthchk378923.html. While you can use index.html as the health-check page, this is not recommended. This is because most web sites have an index.html page which creates the risk that your load balancer will direct client traffic to a web site other than your own in the cloud.

Example: The Amazon EC2 cloud recycles IP addresses so if one server was terminated and another launched for a different site—with the same IP address and page name as your health-check page name—HAProxy could consider the server to be running even though it is someone else's, and direct traffic to it.

For this reason, you should always use a health-check URI with a unique file name. This value displays in the HAProxy configuration file as:

  # When internal servers support a status page
  option httpchk GET /hlthchk378923.html

Name of a pool of HAProxy load-balancer servers; for example, www. Load-balancer servers with the same LB_LISTENER_NAME become part of the same pool. The HAProxy configuration file includes this value in the configuration block:

  # Example: listen myapp
  listen www
  mode http
  balance roundrobin

This is the IP address that HAProxy listens on, which is normally the localhost specified by IP address:

This is the port that HAProxy listens on, which is normally 85.

This is the name of the base HAProxy configuration file that will be used.  This file is modified according to the defined input values. The current values are:


Note: Do not use the haproxy_fullssl option to enable SSL for your load-balancer server. This function is performed using a RightScript ("WEB apache FrontEnd https vhost") as described in the FAQ titled How do I set up SSL?

Used to set a password for the HAProxy status report (stats) page.

Normally set to haproxy-status, this setting defines how to access the HAProxy status report web page, which provides information about which servers are running and listening as part of the load-balancer pool. For example, if you set this value to haproxy-status, you would use http://host.domain.tld/haproxy-status to access the status report page. You can change this URI. This value displays in the HAProxy configuration file as:

  # Haproxy status page
  stats uri /haproxy-status

This can be used to set a user name for the HAProxy status page.

LB Apache reverse proxy configure. Sets up the Apache web server as a reverse proxy, and includes the /etc/httpd/rightscale.d folder, which contains vhost files for Apache. There are no inputs.

Required Application Server Scripts

The following scripts must run on the application servers in your configuration to enable interaction with your HAProxy load balancer servers.

LB Application to HAProxy connect. Connects the instance to the servers running HAProxy. This script must run on each application server that will join the load-balancer pool.

The fully qualified hostname for all servers with HAProxy installed on them. For example, if has two associated load-balancer servers with static IP addresses, you would enter as the LB_HOSTNAME. These hosts must be registered with DNS so that the script can locate all HAProxy servers and update their configuration files.

When set to True HAProxy will reconnect sessions to the last server they were connected to (session stickiness), via a cookie.

LB Application to HAProxy disconnect. Disconnects the instance from the servers running HAProxy (i.e. removes it from the load-balancer pool), typically on server shutdown. This is generally run as a decommission script on application servers.

Configuration Files

The /etc/haproxy/haproxy.cfg file is the primary configuration file for HAProxy.

The last lines in this file list the application servers in the load-balancer pool. When LB Application to HAProxy connect runs on an application server, it adds that server to all the HAProxy configuration files on all load-balancer servers with the same LB_HOSTNAME.

#server srv3.0 cookie srv03.0 check inter 2000 rise 2 fall 3

server i-b70793de cookie i-b70793de check inter 3000 rise 2 fall 3 maxconn 255

The /etc/httpd/rightscale.d directory contains the vhost files for the Apache web server. For example: