Create a Load Balancer with the CloudHub API

You can create a dedicated load balancer (DLB) using the CloudHub API.

Prerequisites

To create a load balancer using the CloudHub API, ensure that you perform the following:

Ensure that you are an administrator in the organization where you are creating the load balancer.
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

To create a load balancer using the CloudHub API, use the following endpoints:

anypoint.mulesoft.com/cloudhub/api/organizations/orgid/loadbalancers
anypoint.mulesoft.com/cloudhub/api/organizations/orgid/vpcs

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.

The CloudHub DLB name cannot start with internal-. Starting the DLB name with internal- results in error message: LB name=internal-dlb-name cannot start with -internal.

Enable TLS 1.0 on a DLB Using the CloudHub API

Although TLS 1.0 is not recommended due to security vulnerabilities, you can enable support if required for communication with legacy clients.

You can enable TLS 1.0 support only on the default SSL endpoint of the DLB. Enabling TLS 1.0 support applies to the entire DLB, not a single SSL endpoint.

For security reasons, do not leave TLS 1.0 enabled. After you no longer need TLS 1.0, replace the default cipher suite, for example, with NewDefault.

To enable TLS 1.0 support on a DLB using the CloudHub API:

Run the following command:

curl -X PATCH \
  https://anypoint.mulesoft.com/cloudhub/api/organizations/myOrgID/vpcs/myVpcID/loadbalancers/myDlbID \
  -H 'authorization: Bearer myAccessToken' \
  -H 'content-type: application/json' \
  -d '[
  {
    "op": "replace",
    "path": "/sslEndpoints/0/tlsv1",
    "value": "true"
  }
]'

In the command:

myOrgID is the organization ID.
myVpcID is the ID for the VPC.
myDlbID is the ID for the DLB.
myAccessToken is the access token you generated.

The response includes the following:

"tlsv1": true,

Change the default cipher suite to OldDefault.

See Change the Default Cipher Suite to Support TLS 1.0.

Create a Load Balancer with the CloudHub API

Prerequisites

Create a Load Balancer

Enable TLS 1.0 on a DLB Using the CloudHub API

See Also