Skip to content

Latest commit

 

History

History
73 lines (45 loc) · 3.93 KB

begin-lb-config.md

File metadata and controls

73 lines (45 loc) · 3.93 KB
copyright lastupdated
years
2017, 2018
2018-11-07

{:shortdesc: .shortdesc} {:new_window: target="_blank"} {:codeblock: .codeblock} {:pre: .pre} {:screen: .screen} {:tip: .tip} {:download: .download} {:important: .important} {:note: .note}

Configure IBM Cloud Load Balancer parameters

Once you create a load balancer, you can then configure it for elastic load balancing. To do so:

  1. Name your load balancer, and, optionally, add a description.

    drawing

  2. Input the details of your application profile by identifying the protocols and ports your application is listening on. You can use the same configuration for both front-end and back-end, or expose a different front-end port (for security purposes, for instance).

  3. The default load balancing method is Round Robin. You may change it to Weighted Round Robin or Least Connections from the drop-down list, depending on your application needs.

  4. Optionally, you can enable Session stickiness. If enabled, all requests from a given end-user (for example, one with the same source IP) go to the same backend server for a system-defined "sticky" time.

  5. You can also set the Maximum connection limit against your application.

  6. Click Add Protocol to specify additional ports and protocols your application may be listening on. Be sure that all front-end ports are unique. You can choose HTTP, HTTPS or TCP as your front-end protocol.

    drawing

    3A maximum of two ports may be defined at the time of initial configuration. Additional ports may be added later after creating the service instance. Refer to Limitations on number of ports for more information on the maximum number of ports allowed. {:note:}

  7. The IBM© Cloud Load Balancer terminates incoming HTTPS (HTTP over SSL) connections and communicates in plain-text HTTP with the back-end application servers, and offloads processor-intensive SSL tasks from your servers. You must upload your SSL Certificate. Select one of your available certificates from the drop-down list.

    drawing

    If you do not have an existing certificate, then click Add a new Certificate. This takes you to an IBM Cloud certificate service where you can either purchase a new certificate or upload an existing one.

    After adding the certificate, return to the load balancer configuration page and click the refresh icon below the SSL Certificate drop-down list to view and add your newly-uploaded certificate.

    drawing drawing

    NOTE: Never delete any certificates associated with HTTPS listeners as this can cause issues with functionality.

  8. Click Next.

Configure Health Checks

The health check definition is mandatory for each of your application ports. These are the back-end ports identified in the previous basic configuration menu.

drawing

The system pre-populates a default health check configuration for these back-end ports. You may customize these settings to suit your application needs.

  • Interval: Interval in seconds between two consecutive health check attempts
  • Timeout: Maximum amount of time the system will wait for a response against a health check request
  • Max Trials: Maximum number of additional health check attempts the system will make prior to declaring a port unhealthy
  • Path: The HTTP URL path for the health check

Click Next to enable your choice.

What's Next

Identify your application's resources, such as origin pools and health check mechanisms.