Guide
TrainingSupportCommunity

Set up load balancing configurations

Suggest Edits

For Application Load Balancer, you need to set up a load balancing configuration that includes the data centers and liveness tests you want to use.

You use the Load Balancing Manager to create and manage these load balancing configurations.

Verify Conditional Origins for load balancing

Application Load Balancer uses Conditional Origins to represent data centers that are part of the load balancing and failover scheme.

At this point in the setup process, you should have a separate Conditional Origin for each data center included in your Application Load Balancing configuration.

Once you verify that you have the Conditional Origins you need, you can create a load balancing configuration.

Create a load balancing configuration

When you create a load balancing version, you set the load balancing type and configure data centers and liveness tests.

  1. Go to ☰ > CDN > Edge logic Cloudlets.

  2. On the main Cloudlets Policy Manager screen, select the Manage Load Balancing Setup tab.

  3. Click Create New Load Balancing Setup.

  4. Enter a unique load balancing ID using alphanumeric characters and underscores, and add a note describing the configuration.

  5. Click Create Load Balancing Setup.

    Version 1 of the load balancing configuration displays on the Load Balancing Version Details screen.

  6. Complete these fields:

FieldEntry
Version NotesEnter a description of how this particular configuration version differs from others.
Balancing TypeSelect the type of load balancing to use, which is either Weighted or Performance.

  • Weighted load balancing routes requests to live data centers exactly in the proportion configured.
  • Performance load balancing dynamically determines which route to use based on real-time load feedback and the shortest geographic route to the origin data center.Note: If a data center fails, the system automatically fails over to another data center.
    • Enable Liveness TestSelect to enable liveness testing for your load balancing configuration. You can enter additional (case-insensitive) HTTP headers to be included in the testing request.
    1. Click Add Data Center and select a data center from the dropdown.

    🚧

    If you are using Automatic or Custom failover

    Include all data centers that you want to use for failover in each load balancer configuration.

    A data center will not be used as a failover origin if it is not included in the load balancer's configuration.

    1. Complete the following data center fields:
    FieldEntry
    Percent TrafficEnter the percent of traffic that will be sent to the data center. The total for all data centers listed must equal 100%.

    The total for all data centers is automatically set to 100%.

    For example, if you add a data center and assign it 80% of the traffic, the next data center you add will automatically be set to 20%. If you then add a third data center, it will automatically be set to 0%. You will have to manually adjust this field across all data centers to get your desired traffic percentages.

    If the data center is used only for failover, you can set the amount of traffic sent to that data center as 0%.
    Is a Cloud ServiceIf selected, caching for the data center is updated at a certain interval. This is how caching works for cloud-based services, like AWS.

    If enabled, caching will occur at shortened intervals, as IP addresses used with cloud services can change.
    Data Center LocationStart typing the country and city where your data center is located. Once you select the country and city, the system auto-populates the latitude and longitude.

    If your city doesn't appear in the dropdown after typing it, manually add the latitude and longitude.
    Liveness ServersIf you enable liveness tests, enter the IP addresses or hostnames that are pinged by the liveness checks.

    📘

    Liveness test delay after Load Balancing configuration update

    After you update your Load Balancing configuration, a new liveness test is set up. The first check doesn't happen immediately but starts after a small randomized delay, which can be up to 5 minutes. This delay in the liveness test can cause a delay in the availability of the Data Center (DC). The system might assume the DC is unavailable or unresponsive during this delay, causing potential disruptions.

    To prevent unnecessary downtime or availability delays, we recommend that you:

    • Set DC %% to 0 (instead of removing the DC):
      • This reduces the percentage (%%) of traffic or load directed to that Data Center to 0 temporarily, without completely removing the DC from operation.
      • By setting it to 0%, the DC remains part of the system but won't be actively used until the liveness test confirms it is up and running.
    • Disable the liveness test when a single DC is used:
      • If there is only one Data Center being used (which means no failover options), disabling the liveness test altogether may be recommended. This ensures that the system doesn't incorrectly assume the single DC is unavailable due to a liveness test delay, avoiding unnecessary downtime or disruptions.
    1. Add and configure additional data centers until they're all configured.
    2. If you enabled the liveness test, complete these fields:
    FieldEntry
    ProtocolThe protocol or scheme for the database, either HTTP or HTTPS.

    If you select the HTTPS protocol, the Enable SSL Peer Certificate Validation checkbox appears below the Protocol field. Use this checkbox to verify the validity of an SSL certificate. This prevents the delivery of traffic to an origin that is operational but has an invalid or bad certificate, which can cause failure on the clients if they are sent to the origin.
    Pre-2023 Security PostureApplication Load Balancer is now using OpenSSL version 3. The temporary Pre-2023 Security Posture check box is a setting to enable backwards compatibility for Liveness endpoints that use older TLS protocols.

    Enable to allow liveness tests using pre-2023 security postures to operate.
    When disabled, older and less secure protocol features rejected by OpenSSL 3.x will cause liveness tests to fail.
    PortThe port for the test object. The default port is 80 which is standard for HTTP. For HTTPS, enter 443.
    Test Interval (sec)How often the liveness test occurs in seconds. The default is 60 seconds, and a minimum of 10 seconds is required.
    Timeout (sec)The number of seconds the system waits before failing the liveness test. The default is 25 seconds.
    PathThe path to the test object used for liveness testing. The test object resides on your origin.
    HTTP HeadersEnter the name and value of each HTTP header you want to include in liveness test requests. Click + to enter multiple headers.
    Redirects (3XX)Enable to mark the liveness test as failed when the request returns a 3xx (redirection) status code.
    Client Error (4XX)Enable to mark the liveness test as failed when the request returns a 4xx (client error) status code.
    Server Error (5XX)Enable to mark the liveness test as failed when the request returns a 5xx (server error) status code.
    1. Click Save Load Balancing Version.

    Edit a new load balancing version

    If you want to try out changes to a load balancing configuration, you can edit a new version of that configuration.

    1. Go to ☰ > CDN > Edge logic Cloudlets.

    2. On the main Cloudlets Policy Manager screen, select the Manage Load Balancing Setup tab.

    3. In the Load Balancing ID column of the Load Balancing Manager screen, click the name of the origin you want to edit load balancing settings for.

    4. In the Action column for the origin you want to edit, select Edit New Version.

    5. In the Origin Version Notes field, enter a description to distinguish this version from others.

    6. Click Edit New Version.

    7. Update the load balancing fields as needed.

    Activate a load balancing configuration

    Activate a Load Balancing configuration, which contains traffic and liveness testing settings.

    1. Go to ☰ > CDN > Edge logic Cloudlets.

    2. Click the Manage Load Balancing Setup tab.

    3. Click the action cog next to the load balancing version you want to activate.

    4. Select Activate Load Balancing Version.

    5. Complete the following fields:

    FieldAction
    Version to ActivateIf not already selected, choose the version of the load balancing configuration that you want to activate.
    Activation NetworkSelect the environment/network you want to activate the policy version on. Options are Staging and Production.

    1. Click Activate Load Balancing Version.

    2. Check the status of the activation on either the Load Balancing Manager or Load Balancing Details screen.

    Updated 3 months ago