HAProxy Enterprise Documentation 1.8r2

Amazon Web Services

Launch HAProxy Enterprise directly from the AWS Marketplace as an Amazon Machine Image (AMI), which creates a virtual machine instance with HAProxy Enterprise installed.

Launch the HAProxy Enterprise AMI

  1. From the AWS Marketplace, search for HAProxy Enterprise and choose an HAProxy Enterprise AMI from the list. Options include an Ubuntu Server edition and a Red Hat Enterprise Linux edition.

    https://cdn.haproxy.com/documentation/hapee/1-8r2/assets/aws-ami-ubuntu-104ad7c8d7ea4b5853fce505aff85acf1000cecf0463de7e8264300b5e08443e.png https://cdn.haproxy.com/documentation/hapee/1-8r2/assets/aws-ami-rhel-b54d8dc778191c9e104710dd6e830f3db0247e5164983e6b1cc250e85e7f0c46.png
  2. Click Continue to Subscribe to start a subscription to the HAProxy Enterprise software.

  3. Click Continue to Configuration and then Continue to Launch.

    https://cdn.haproxy.com/documentation/hapee/1-8r2/assets/aws-launch-through-ec2-569985bcb220b27b63441b9b3217dac3c419fac4590865cdeccdbd6763d83983.png
  4. Select the instance size.

    https://cdn.haproxy.com/documentation/hapee/1-8r2/assets/aws-choose-instance-type-f5927f3351a49d193b7b1bcbe154d75af2c10273da45557a1e200b66a6df03d5.png
  5. Create or import an RSA key pair, then launch the instance.

Connect to the HAProxy Enterprise instance

  1. If necessary, change the permissions of your private key:

    For example:

    $ chmod 600 my-private-key.pem
  2. Copy the public IPv4 address of the instance from the AWS instances console.

  3. Connect to the HAProxy Enterprise instance through its public IP:

    For example:

    Ubuntu
    $ ssh -i my-private-key.pem ubuntu@35.181.155.36
    RHEL
    $ ssh -i my-private-key.pem ec2-user@35.181.155.36

Note

You can also connect to the HAProxy Enterprise instance through its private IP from a bastion host.

Manage the HAProxy Enterprise service

The HAProxy Enterprise service runs at startup. You can manage the process with systemctl.

For example, use systemctl status to check that the service is running:

[ec2-user@ip-172-31-39-22 ~]$ systemctl status hapee-2.0-lb
● hapee-2.0-lb.service - HAPEE Load Balancer
   Loaded: loaded (/usr/lib/systemd/system/hapee-2.0-lb.service; enabled; vendor preset: disabled)
   Drop-In: /etc/systemd/system/hapee-2.0-lb.service.d
            └─override.conf
   Active: active (running) since Wed 2020-12-09 14:07:46 UTC; 14min ago
   Main PID: 918 (hapee-lb)
   CGroup: /system.slice/hapee-2.0-lb.service
            ├─918 /opt/hapee-2.0/sbin/hapee-lb -Ws -f /etc/hapee-2.0/hapee-lb.cfg -p /run/hapee-2.0-lb.pid -m 5212 -f /etc/hapee-2.0/dashboard-module.cfg
            └─920 /opt/hapee-2.0/sbin/hapee-lb -Ws -f /etc/hapee-2.0/hapee-lb.cfg -p /run/hapee-2.0-lb.pid -m 5212 -f /etc/hapee-2.0/dashboard-module.cfg

Access the Web Dashboard

  1. Display the Web Dashboard credentials, which are stored in the file /README.txt.

    For example:

    [ec2-user@ip-172-31-39-22 ~]$ sudo cat /README.txt
    
    username: dashboard
    password: 091l/Bw2
  2. Connect to the Web Dashboard through either HTTP (port 9022) or HTTPS (port 9023). The URLs are http://<Public IPv4 address>:9022/ and https://<Public IPv4 address>:9023/.

    https://cdn.haproxy.com/documentation/hapee/1-8r2/assets/aws-dashboard-e59c60b611e65769e2d4e874919a9e47dd80d302d9e4b6de3e6d26830e2bc595.png

    Note

    Connecting to http://<Public IPv4 address> displays the load balancer's statistics.


Next up

Kubernetes