---
schema_version: "1"
id: fb4cf1d6c9ccc5791cd9324675eebdda4b2325ed4f163e68eed1e9551f10c8ad
title: Create a Load Balancer with Runtime Manager
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/cloudhub/lb-create-arm.md
canonical_url: https://docs.mulesoft.com/cloudhub/lb-create-arm
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 72b952969ce582ef1cf8755f8ce5889a30460d6692e38f3a8352c0ef669d4f31
description: MuleSoft Documentation Site
latest: true
---
---
product: CloudHub
---

# Create a Load Balancer with Runtime Manager

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

You can use Runtime Manager to create a dedicated load balancer (DLB) in your CloudHub environment.

## Prerequisites

Before creating a load balancer, perform the following:

- Ensure that your profile is authorized to perform this action by adding the **CloudHub Network
  Administrator** permission to the profile of the organization where you are creating the load
  balancer.

  Similarly, the administrator role of the same organization also provides the authorization
  required.

- Create an Anypoint Virtual Private Cloud (Anypoint VPC) in the organization where you want to
  create a load balancer.

- Create at least one certificate and private key for your certificate.

## Create a Load Balancer

1.  From Anypoint Platform, click **Runtime Manager**.

2.  Click **Load Balancers** > **Create Load Balancer**.

3.  Enter a name for your load balancer.

    The CloudHub DLB name must be unique across all DLBs defined in Anypoint Platform (by all
    MuleSoft customers). For this reason, you might want to append your organization name to your
    DLB name.

    > [!IMPORTANT] You cannot change the name of a DLB after you create it. To change the name,
    > delete and re-create it using the new name.

    Each dedicated load balancer exposes an external domain `_lb-name_.lb.anypointdns.net` name
    where `_lb-name_` is the name you provide.

    The CloudHub DLB name cannot start with `internal-`.

4.  Select a target Anypoint VPC from the drop-down list.

5.  Specify the amount of time the DLB waits for a response from the Mule application in the
    **Timeout in Seconds** field.

    The default value is 300 seconds.

6.  Add any allowlisted classless inter-domain routing (CIDR) as required.

    The IP addresses you specify here are the only IP addresses that can access the load balancer.
    The default value is `0.0.0.0/0`.

7.  Select the inbound HTTP mode for the load balancer.

    This property specifies the behavior of the load balancer when receiving an HTTP request. Valid
    values are:

    - **Off**

      Causes the load balancer to silently drop the request.

    - **On**

      Accepts the inbound request on the default SSL endpoint using the HTTP protocol.

    - **Redirect**

      Redirects the request to the same URL using the HTTPS protocol.

8.  Specify options:

    - **Enable Static IPs** specifies to use static IPs, which persist when the DLB restarts.

      For more information about static IP addresses, see
      [Static IP Addresses](https://docs.mulesoft.com/cloudhub/cloudhub-dedicated-load-balancer#static-ip-addresses).

    - **Keep URL encoding** specifies that the DLB passes only the `%20` and `%23` characters as is.

      If you deselect this option, the DLB decodes the encoded part of the request URI before
      passing it to the CloudHub worker.

    - **Transport Downstream Protocols** specifies the list of enabled TLS protocols for connections
      from the client to the DLB.

      Use the dropdown to add or remove protocols.

    - **Transport Upstream Protocols** specifies the list of enabled TLS protocols for connections
      from the DLB to the Mule application.

      Use the dropdown to add or remove protocols.

    - **Forward Client Certificate** specifies that the DLB forwards the client certificate to the
      CloudHub worker.

9.  Add a certificate.

    1.  Click **Add certificate**:

    2.  On the **Create Load Balancer | Add certificate** page, select **Choose File** to upload
        both public key and private key files.

    3.  If you want to add a trusted CA certificate, click **Choose File** to upload the file.

        The trusted CA certificate is used to verify client certificates.

    4.  If you want to add URL mapping rules, click the **\>** icon to display the options:

        If you add more than one URL mapping rule, order the rules in the list according to the
        priority in which they should be applied.

        Click **Add New Rule**, and then specify the input path, target app, output path, and
        protocol.

    5.  Click **Save Certificate**.

10. Click **Create Load Balancer**.

## See Also

- [Access Management](https://docs.mulesoft.com/access-management/)

- [Dedicated Load Balancers](https://docs.mulesoft.com/cloudhub/cloudhub-dedicated-load-balancer)

- [Add Certificates to a Dedicated Load Balancer](https://docs.mulesoft.com/cloudhub/lb-cert-upload)

- [Certificate Validation in Dedicated Load Balancers](https://docs.mulesoft.com/cloudhub/lb-cert-validation)

- [Allowlists](https://docs.mulesoft.com/cloudhub/lb-allowlists)

- [Mapping Rules](https://docs.mulesoft.com/cloudhub/lb-mapping-rules)