Creating a Load Balancer

When you create a load balancer, you provide a name and the basic properties of the load balancer. Later, you must define server pools, create at least one listener, and optionally define the policies for the load balancer.

To complete this task, you must have the Oracle Load Balancer Service Administrator role. See About Oracle Load Balancer Cloud Service Roles. If the required role isn’t assigned to you or you’re not sure, then ask your system administrator to ensure that the role is assigned to you in Oracle Cloud My Services. See Modifying User Roles in Managing and Monitoring Oracle Cloud.

  1. Click the Network tab in the Oracle Compute Cloud Service console.
  2. Click the Load Balancers tab in the left pane, and then click Load Balancers.
    The Load Balancers page displays any existing load balancers you have already created.

    If you created a new load balancer recently and it is not appearing on the Load Balancers page, click Refresh icon to refresh the list of load balancers.

  3. To create a new load balancer, click the Create Load Balancer button.
    The Create Load Balancer dialog box is displayed.
  4. Enter details for the following fields:
    • Name - Unique identifier for the load balancer.
      You must follow these conventions for the Name field:
      • It can contain only alphanumeric characters, hyphens, and underscores.

      • First and last characters cannot be hyphen or underscore.

      • It must not be more than 30 characters.

      • Period is not supported.

    • IP Networks - Select the IP network to be associated with the load balancer. The IP network should be pre-created as described in Creating an IP Network in Using Oracle Cloud Infrastructure Compute Classic.


      You can configure your PaaS service instance and load balancer associated with it in same IP network or in the IP networks connected through an IP network exchange. You must create an IP network, create a load balancer in that IP network, and while creating the PaaS service instance choose the same IP network (or some other IP network that's connected through an IP network exchange to the IP network intended to be used for the PaaS instance).

      See Managing IP Network Exchanges in Using Oracle Cloud Infrastructure Compute Classic.

    • Description - A short description for the load balancer. The description must not exceed 1000 characters.
    • Permitted Methods - The permitted HTTP methods for this load balancer. You can select the predefined methods (GET, POST, PUT, PATCH, DELETE, or HEAD) or you can also create your own custom methods. Requests with methods not listed in this field will result in a 403 (unauthorized access) response.

      This option is useful if you want to limit the operations performed on the origin servers in the server pool. For example, for a typical Web server implementation, clients should only need to perform basic HTML methods, such as GET and POST. Additional methods, such as PUT and DELETE can be destructive. To take extra steps to protect your data, you can restrict the load balancer to only accept and route only GET and POST requests.

    • Scheme - Select a scheme for the load balancer:
      • Internet-facing - This scheme allows you to create an internet-facing load balancer in a given IP network using Oracle Cloud Infrastructure Load Balancing Classic. This option enables you to add a load balancer to your own IP Network, while assigning a internet addressable IP address to the load balancer. This allows your application to be accessible over the internet but at the same time protects the communication between the load balancer and the applications by putting both in the same IP network. In this scheme, the load balancer is typically terminating SSL as well, since the backend traffic is protected inside an IP network, no further encryption is necessary.

      • Internal - This scheme allows you to create an internal load balancer in a given IP network using Oracle Cloud Infrastructure Load Balancing Classic. This option enables you to add a load balancer to your own IP network for the sole consumption of other clients inside the same network. Since in this scheme, end to end communications from the client to the balancer and subsequently to the applications are all inside the same IP network, the traffic is entirely protected from the internet. In this scheme, encryption and SSL termination is no longer necessary.

    • SSL Certificate Port Mapping - A certificate name and port number pair which explicitly configures a certificate to be returned.
    • Enabled - Check this option to enable the load balancer.

      Disabling the load balancer results in access getting denied to all clients. For HTTP/HTTPS listeners, disabling results in 503 responses for new requests; existing requests result in 500 responses.

  5. Click Create.

    A new load balancer is created. If the newly created load balancer does not appear in the Load Balancers tab, click Refresh icon available in the dashboard to refresh the list of load balancers.


    • You cannot use a load balancer until you finish the configuration of the load balancer by adding a server pool and a listener. If you selected the IP networks option when creating the load balancer then two listeners (one HTTP and the other HTTPS on ports 80 and 443 respectively) are created by default.

    • If your load balancer was created by Oracle PaaS Service Manager (PSM) then certain parameters of the resources (load balancer, listener, server pool, etc) cannot be modified after the resource creation.