Managing Load Balancers

This topic describes how to create or delete a load balancer on your system.

Caution

Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

Prerequisites

To implement a working load balancer, you need:

  • For a public load balancer in a region with multiple availability domains , you need a VCN with a public regional subnet or at least two public AD-specific subnets. In the latter case, each AD-specific subnet must reside in a separate availability domain. For more information on subnets, See VCNs and Subnets and Public IP Address Ranges.

    Caution

    You cannot specify a private subnet for your public load balancer.
  • For a public load balancer in a region with only one availability domain, you need a VCN with at least one public subnet.
  • For a private load balancer in any region, you need a VCN with at least one private subnet.
  • Two or more backend servers (Compute instances) running your applications. For more information on Compute instances, see Creating an Instance.
Note

Private IP Address Consumption

A public load balancer created in one public regional subnet consumes two private IP addresses from the host subnet. The primary and secondary load balancers reside within the same subnet. Each load balancer requires a private IP address from that subnet. The Load Balancing service assigns a floating public IP address, which does not come from the host subnet.

A public load balancer created in two public AD-specific subnets consumes two private IP addresses, one from each host subnet. The primary and secondary load balancers reside within different subnets. Each load balancer requires one private IP address from its host subnet. The Load Balancing service assigns a floating public IP address, which does not come from the host subnets.

A private load balancer created in a single subnet consumes three private IP addresses from the host subnet. The primary and secondary load balancers reside within the same subnet. Each load balancer requires a private IP address from that subnet. The floating private IP address also comes from the host subnet.

Working with Load Balancers

For background information on Oracle Cloud Infrastructure Load Balancing, see Overview of Load Balancing.

For the purposes of access control, you must specify the compartment where you want the load balancer to reside. Consult an administrator in your organization if you're not sure which compartment to use. For information about compartments and access control, see Managing Compartments.

When you create a load balancer within your VCN, you get a public or private IP address, and provisioned total bandwidth. If you need another IP address, you can create another load balancer.

A public load balancer in a region with multiple availability domains requires one public regional subnet or two public AD-specific subnets to host the primary load balancer and a standby. In the latter case, each AD-specific subnet must reside in a separate availability domain. A public load balancer in a region with only one availability domain requires a single public subnet to host the primary load balancer and a standby. For more information on VCNs and subnets, see Networking Overview. You can associate the public IPv4 address with a DNS name from any vendor. You can use the public IP address as a front end for incoming traffic. The load balancer can route data traffic to any backend server that is reachable from the VCN.

A private load balancer requires only one subnet to host the primary load balancer and a standby. The private IP address is local to the subnet. The load balancer is accessible only from within the VCN that contains the associated subnet, or as further restricted by your security list rules. The load balancer can route data traffic to any backend server that is reachable from the VCN.

The essential components for load balancing include:

Optionally, you can associate your listeners with SSL server certificate bundles to manage how your system handles SSL traffic. See Managing SSL Certificates.

For information about the number of load balancers you can have, see Service Limits.

Configuration Changes and Service Disruption

For a running load balancer, some configuration changes lead to service disruptions. The following guidelines help you understand the effect of changes to your load balancer.

  • Operations that add, remove, or modify a backend server create no disruptions to the Load Balancing service.
  • Operations that edit an existing health check policy create no disruptions to the Load Balancing service.
  • Operations that trigger a load balancer reconfiguration can produce a brief service disruption with the possibility of some terminated connections.

Health Status

The Load Balancing service provides health status indicators that use your health check policies to report on the general health of your load balancers and their components. You can see health status indicators on the Console List and Details pages for load balancers, backend sets, and backend servers. You also can use the Load Balancing API to retrieve this information.

For general information about health status indicators, see Editing Health Check Policies.

Load Balancer Health Summary

The Console list of load balancers provides health status summaries that indicate the overall health of each load balancer. Health status indicators have four levels. The meaning of each level is:

The Console list of load balancers provides health status summaries that indicate the overall health of each load balancer. Health status indicators come in four levels. The meaning of each level is:

  • OK: All backend sets associated with the load balancer return a status of OK.
  • WARNING: All the following conditions are true:

    • At least one backend set associated with the load balancer returns a status of WARNING or UNKNOWN.
    • No backend sets return a status of CRITICAL.
    • The load balancer life-cycle state is ACTIVE.
  • CRITICAL: At least one backend set associated with the load balancer returns a status of CRITICAL.
  • UNKNOWN: Any one of the following conditions is true:

    • The load balancer life-cycle state is not ACTIVE.
    • No backend sets are defined for the load balancer.
    • All the following conditions are true:

      • More than half of the backend sets associated with the load balancer return a status of UNKNOWN.
      • None of the backend sets return a status of WARNING or CRITICAL.
      • The load balancer life-cycle state is ACTIVE.
    • The system could not retrieve metrics for any reason.

For guidance on detecting and correcting common issues, see Health Status.

Load Balancer Health Details

The load balancer Details page provides the same Overall Health status indicator found in the list of load balancers. It also includes counters for the Backend Set Health status values reported by the load balancer's child backend sets.

The health status counter badges indicate the following:

  • The number of child entities reporting the indicated health status level.
  • If a counter corresponds to the overall health, the badge has a fill color.
  • If a counter has a zero value, the badge has a light gray outline and no fill color.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be granted security access in a policy  by an administrator. This access is required whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a message that you don’t have permission or are unauthorized, verify with your administrator what type of access you have and which compartment  you should work in.

For administrators: For a typical policy that gives access to load balancers and their components, see Let network admins manage load balancers.

Also, be aware that a policy statement with inspect load-balancers gives the specified group the ability to see all information about the load balancers. For more information, see Details for Load Balancing.

If you're new to policies, see Getting Started with Policies and Common Policies.

Creating Load Balancers

To create a load balancer:

  1. Open the navigation menu. Under the Core Infrastructure group, go to Networking and click Load Balancers.
  2. Choose a Compartment you have permission to work in, and then click Create Load Balancer.

  3. Follow these workflows:

    Step 1 - Add Details

    Specify the attributes of the load balancer.

    • Load Balancer Name: Required. Accept the default name or specify a friendly name for the load balancer. It does not have to be unique, but it cannot be changed in the Console. (You can, however, change it with the API.) Avoid entering confidential information.
    • Choose Visibility Type: Specify whether your load balancer is public or private.

      • Public: Choose this option to create a public load balancer. You can use the assigned public IP address as a front end for incoming traffic and to balance that traffic across all backend servers.
      • Private: Choose this option to create a private load balancer. You can use the assigned private IP address as a front end for incoming internal VCN traffic and to balance that traffic across all backend servers.
    • Choose IP Address Type: Specify whether the public IP address is reserved or ephemeral.
      • Ephemeral IP Address: Choose this option to let Oracle specify an ephemeral IP address for you from the Oracle IP pool. This is the default.
      • Reserved IP Address: Choose this option to specify an existing reserved IP address by name, or to create a new reserved IP address by assigning a name and selecting a source IP pool for the address. If you don't select a pool you've created, the default Oracle IP pool is used.
    • Always Free: Enable this feature if you are creating your load balancer as an Always Free account. Although paid account users can create an Always Free shape, this shape cannot be changed to a different size as can be done for other shapes.

      The following options for choosing the maximum total bandwidth shape differ depending on whether Always Free is enabled or not.

      Note

      If you are creating a load balancer in an Always Free tenancy, the Always Free feature is enabled by default, and only Always Free shape options are available. If you disable the Always Free feature, you are prompted to upgrade to a paid user account. Upgrading is the only way an Always Free tenancy can select a bandwidth shape option other than the default Always Free size. For more information about Always Free resources, including other capabilities and limitations, see Oracle Cloud Infrastructure Free Tier.
    • Choose the Maximum Total Bandwidth: Required. Select the total bandwidth for your load balancer from the following options.

      If you are creating the load balancer as an Always Free user, you can only select the Always Free (10 Mbps) option.

      If you are creating the load balancer as a paid account user, you can create various shape options based on your limits and later adjust the bandwidth by changing the shape after the load balancer has been created. You can view your service limits and quotas in the Console by navigating to Governance > Limits, Quotas and Usage. Select "LbaaS" from the Service list. Your bandwidth size options are listed. See Service Limits for more information. You can also select the Always Free option if you have not used your one free tier account.

      Note

      If you are using non-universal credit (UCM) SKUs, ensure that your contract includes the shape you are updating to so you can prevent incurring overage charges.
      • Always Free (10 Mbps) - This is the only bandwidth option for Always Free clients.

      • 10 Mbps - Select this option if you are not an Always Free user but want a 10 Mbps load balancer.
      • 100 Mbps
      • 400 Mbps
      • 8000 Mbps
    • Enable IPv6 Address Assignment: Available only in the US Government Cloud. Specify whether the load balancer supports IPv6 addresses for incoming requests.

      Note

      • When you create a load balancer, you can optionally choose to have an IPv4/IPv6 dual-stack configuration. When you choose the IPv6 option, the Load Balancing service assigns both an IPv4 and an IPv6 address to the load balancer. The load balancer receives client traffic sent to the assigned IPv6 address. The load balancer uses only IPv4 addresses to communicate with backend servers. There is no IPv6 communication between the load balancer and the backend servers.
      • IPv6 address assignment occurs only at load balancer creation. You cannot assign an IPv6 address to an existing load balancer.
      • Only VCNs in the US Government Cloud currently support IPv6 addressing. For more information about Oracle Cloud Infrastructure's IPv6 implementation, see IPv6 Addresses.
    • Choose Networking

      If the current compartment contains at least one VCN, the Console provides a drop-down list of VCNs for you to choose from.

      • Virtual Cloud Network in <compartment>: Required. Specify a VCN for the load balancer.

        By default, the Console shows a list of VCNs in the compartment you’re currently working in. Click the Change Compartment link to select a VCN from a different compartment.

      • Subnet in <compartment>: Required. Select an available subnet. For a public load balancer, it must be a public subnet.

        By default, the Console shows a list of subnets in the compartment you’re currently working in. Click the Change Compartment link to select a subnet from a different compartment.

        Tip

        In addition to public or private, subnets can be either regional or AD-specific. Oracle recommends using regional subnets. For more information, see Overview of VCNs and Subnets.
      • Subnet (2 of 2) in <compartment>: Required for a public load balancer when you specify an AD-specific subnet for Subnet. Select a second public subnet. The second subnet must reside in a separate availability domain from the first subnet.

        Tip

        • If you chose to create a private load balancer under Visibility Type, the form prompts you to select only one subnet.
        • If you're working in a region that includes only one availability domain, a second subnet is not required. The form prompts you to select only one subnet.

      If the current compartment contains no virtual cloud networks, the Load Balancing service offers to create a VCN for you.

      • Virtual Cloud Network in <compartment>: When the current compartment contains no virtual cloud networks, the drop-down list is disabled. The system offers to create a VCN for you.

        If you want to use an existing VCN in another compartment, click the Change Compartment link and choose that compartment from the drop-down list.

        Virtual Cloud Network Name: Optional, when the system creates a VCN for you. Specify a friendly name for the new cloud network. It doesn't have to be unique, and it cannot be changed later in the Console (but you can change it with the API). Avoid entering confidential information.

        If you do not specify a name for the new VCN, the system generates a name for you.

    • Use Network Security Groups to Control Traffic: Check this box if you want to add your load balancer to a network security group (NSG). For more information about NSGs, see Network Security Groups.

      • Network Security Groups in <compartment>: Choose an NSG to add your load balancer to.

        By default, the Console shows a list of NSGs in the compartment you’re currently working in. Click the Change Compartment link to select an NSG from a different compartment.

      • (Optional) Click + Another Network Security Group to add your load balancer to another NSG.

      Tip

      You can change the NSGs that your load balancer belongs to after you create it. On the Load Balancer Details page, click the Edit link that appears beside the list of associated network security groups.
    • Show Advanced Options: Click this link to display the following options:

      • Management:

        • Create in Compartment: Optionally, you can select a different compartment to host the load balancer.
      • Tagging: If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, then skip this option (you can apply tags later) or ask your administrator.
    Step 2 - Choose Backends

    A load balancer distributes traffic to backend servers within a backend set. A backend set is a logical entity defined by a load balancing policy, a list of backend servers (Compute instances), and a health check policy.

    The load balancer creation workflow creates one backend set for your load balancer. Optionally, you can add backend sets and backend servers after you create the load balancer.

    • Specify a Load Balancing Policy: Required. Choose the load balancer policy for the backend set. The available options are:

      • Weighted Round Robin: This policy distributes incoming traffic sequentially to each server in a backend set list.
      • IP Hash: This policy ensures that requests from a particular client are always directed to the same backend server.
      • Least Connections: This policy routes incoming request traffic to the backend server with the fewest active connections.

      For more information on these policies, see How Load Balancing Policies Work.

    • Select Backend Servers: Optional. Add backend servers to the backend set. Click Add Backends to select resources from a list of available Compute instances.

      Important

      When you add backend servers, the Load Balancing service automatically creates security list rules for you. If you prefer to create security list rules manually, click Show Advanced Options and choose the option to Manually configure security list rules after the load balancer is created.
      • Add Backends: Select (check) the instances you want to include in the load balancer's backend set.

        To select instances from a different compartment, use the Change Compartment link and choose a compartment from the drop-down list.

        After you select the instances you want to add from the current compartment, click Add Selected Backends.

        Tip

        • You can choose instances from one compartment at a time. After you add instances from one compartment, you can choose Add More Backends to add instances from another compartment.
        • You cannot add a backend server marked as Backup to a backend set that uses the IP Hash policy.

      After you add instances to the backend set, they appear in the Select Backend Servers table. You can:

      • Specify the server Port to which the load balancer must direct traffic. The default is port 80.
      • Click the Actions icon (Actions icon) for a server and choose Delete to remove it from the backend set.
    • Specify Health Check Policy: Required. Specify the test parameters that confirm the health of your backend servers.

      • Protocol: Required. Specify the protocol to use for health check queries, either HTTP or TCP.

        Important

        Configure your health check protocol to match your application or service.
      • Port: Optional. Specify the backend server port against which to run the health check.

        Tip

        You can enter the value '0' to have the health check use the backend server's traffic port.
      • Interval in ms: Optional. Specify how frequently to run the health check, in milliseconds. The default is 10000 (10 seconds).
      • Timeout in ms: Optional. Specify the maximum time in milliseconds to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. The default is 3000 (3 seconds).
      • Number of retries: Optional. Specify the number of retries to attempt before a backend server is considered "unhealthy." This number also applies when recovering a server to the "healthy" state. The default is 3.
      • Status Code: (HTTP only) Optional. Specify the status code a healthy backend server must return.
      • URL Path (URI): (HTTP only) Required. Specify a URL endpoint against which to run the health check.
      • Response Body Regex: (HTTP only) Optional. Provide a regular expression for parsing the response body from the backend server.
    • Use SSL: Optional. Check to apply SSL to the load balancer backend. If you select this option, complete the following:
      • SSL Certificate: Select one of these options:

        • Choose SSL Certificate File: Drag and drop the certificate file into the SSL Certificate field. Alternatively, click Select Files and navigate your system to where you can select the certificate file for upload. Certificate files must be in PEM format and must have the .pem, .cer, or .crt file extensions.

          Important

          If you submit a self-signed certificate for backend SSL, you must submit the same certificate in the corresponding CA Certificate field.
        • Paste SSL Certificate: Copy and paste a certificate directly into this field.
      • Specify CA Certificate: Optional. (Recommended for backend SSL termination configurations.) Check this box if you want to provide a CA certificate. See Working with SSL Certificates for more information.
      • Specify Private Key: Optional. (Required for SSL termination.) Check this box if you want to provide a private key for the certificate.
    • Show Advanced Options: Click this link to access additional options. Select the tab for the corresponding functionality:

      • Backend Set Name: Specify a name for the backend set. It must be unique within the load balancer, and it cannot be changed. If you do not specify a name, the Load Balancing service creates one for you.

        Use only alphanumeric characters, dashes ("-"), and underscores ("_") for backend set names. Backend set names cannot contain spaces. Avoid entering confidential information.

      • Security List: Choose to manually configure subnet security list rules to allow the intended traffic or allow the system to create security list rules for you. To learn more about these rules, see Parts of a Security Rule.

        • Manually configure security list rules after the load balancer is created: When you choose this option, you must configure security list rules after load balancer creation.
        • Automatically add security list rules: Default. When you choose this option, the Load Balancing service creates security list rules for you.

          The system displays a table for egress rules and a table for ingress rules. Each table lets you choose the security list that applies to the relevant subnet.

          You can choose whether to apply the proposed rules for each affected subnet.

      • Session Persistence: Specify how the load balancer manages session persistence.

        Important

        See Session Persistence for important information on configuring these settings.
        • Disable Session Persistence: Choose this option to disable cookie-based session persistence.
        • Enable Application Cookie Persistence: Choose this option to enable persistent sessions from a single logical client when the backend application server response includes a Set-cookie header with the cookie name you specify.

          • Cookie Name: The cookie name used to enable session persistence. Specify * to match any cookie name. Avoid entering confidential information.
          • Disable Fallback: Check this box to disable fallback when the original server is unavailable.
        • Enable Load Balancer Cookie Persistence: Choose this option to enable persistent sessions based on a cookie inserted by the load balancer.

          • Cookie Name: Specify the name of the cookie used to enable session persistence. If blank, the default cookie name is X-Oracle-BMC-LBS-Route.

            Ensure that any cookie names used at the backend application servers are different from the cookie name used at the load balancer. Avoid entering confidential information.

          • Disable Fallback: Check this box to disable fallback when the original server is unavailable.
          • Domain Name: Optional. Specify the domain in which the cookie is valid.

            This attribute has no default value. If you do not specify a value, the load balancer does not insert the domain attribute into the Set-cookie header.

          • Path: Optional. Specify the path in which the cookie is valid. The default value is /.
          • Expiration Period in Seconds: Optional. Specify the amount of time the cookie remains valid. If blank, the cookie expires at the end of the client session.
          • Attributes

            • Secure: Specify whether the Set-cookie header should contain the Secure attribute. If selected, the client sends the cookie only using a secure protocol.

              If you enable this setting, you cannot associate the corresponding backend set with an HTTP listener.

            • HTTP Only: Specify whether the Set-cookie header should contain the HttpOnly attribute. If selected, the cookie is limited to HTTP requests. The client omits the cookie when providing access to cookies through non-HTTP APIs such as JavaScript channels.
      • SSL Policy: Specify the type of cipher suite to use:
        • TLS Version: Required. Specify each of the Transport Layer Security (TLS) versions you want:
          • 1.0
          • 1.1
          • 1.2 (recommended)

          You can select any combination of versions.

          • Specify the Cipher Suite: Required. Choose one of the following options:
            • Select Cipher Suite - Select a set of cipher suites from the list. (default).

              All cipher suites listed have at least one cipher from each of the TLS versions you selected.

            • Create Custom Cipher Suite - Add ciphers to a new suite.

              Perform the following:

              1. Enter the name of the customer cipher suite in the Suite Name field.
              2. Click Choose Ciphers.

                The Select Ciphers page appears.

              3. Check each cipher that you want to include in the suite.

                The TLS versions associated with each cipher are listed in the Version column. Ensure that any cipher you choose is compatible with the TLS versions you previously chose.

              4. Deselect any ciphers you want to exclude.

                Note

                Assign at least one cipher to a cipher suite you create. You cannot create a cipher suite that contains no ciphers.
              5. Click Select. Then select that custom cipher suite (or whatever suite you want to use) from the Select Cipher Suite list.

            • Click Show Cipher Suite Details to display the individual ciphers the selected cipher suite contains.
    Step 3 - Configure Listener
    • Listener Name: Required. Specify a friendly name for the listener. The name must be unique, and cannot be changed. Avoid entering confidential information.

      If you do not specify a name, the Load Balancing service creates one for you.

    • Specify the type of traffic your listener handles: Required. Specify the protocol to use. Choices are:
      • HTTPS
      • HTTP
      • TCP
    • Specify the port your listener monitors for ingress traffic: Required. Specify the port. Defaults are:

      • 443 for HTTPS
      • 80 for HTTP
      • 22 for TCP
    • If you chose the HTTPS protocol, or if you chose the TCP protocol and selected the Use SSL check box
      • Choose SSL Certificate File: Required. Drag and drop the certificate file, in PEM format, into the SSL Certificate field.

        Alternatively, you can choose the Paste SSL Certificate option to paste a certificate directly into this field.

        Important

        If you submit a self-signed certificate for backend SSL, you must submit the same certificate in the corresponding CA Certificate field.
      • Specify CA Certificate: Optional. (Recommended for backend SSL termination configurations.) Select (check) this box if you want to provide a CA certificate. See Working with SSL Certificates for more information.

        • Choose CA Certificate File: Drag and drop the CA certificate file, in PEM format, into the CA Certificate field.

          Alternatively, you can choose the Paste CA Certificate option to paste a certificate directly into this field.

      • Specify Private Key: Optional. (Required for SSL termination.) Select (check) this box if you want to provide a private key for the certificate.

        • Choose Private Key File: Drag and drop the private key, in PEM format, into the Private Key field.

          Alternatively, you can choose the Paste Private Key option to paste a private key directly into this field.

        • Enter Private Key Passphrase: Optional. Specify the private key passphrase.
    • Use SSL: Required for HTTPS, optional for TCP, not available for HTTP. Check to apply SSL to the load balancer listener. If you select this option, complete the following:
      • SSL Certificate: Select one of these options:

        • Choose SSL Certificate File: Drag and drop the certificate file into the SSL Certificate field. Alternatively, click Select Files and navigate your system to where you can select the certificate file for upload. Certificate files must be in PEM format and must have the .pem, .cer, or .crt file extensions.

          Important

          If you submit a self-signed certificate for backend SSL, you must submit the same certificate in the corresponding CA Certificate field.
        • Paste SSL Certificate: Copy and paste a certificate directly into this field.
      • Specify CA Certificate: Optional. (Recommended for backend SSL termination configurations.) Check this box if you want to provide a CA certificate. See Working with SSL Certificates for more information.
      • Specify Private Key: Optional. (Required for SSL termination.) Check this box if you want to provide a private key for the certificate.
    • Show Advanced Options: Click this link to access additional options. Select the tab for the corresponding functionality:

      • Timeout tab: Specify the maximum idle time in seconds. This setting applies to the time allowed between two successive receive or two successive send network input/output operations during the HTTP request-response phase.

        Note

        The maximum value is 7200 seconds. For more information, see Connection Management.
      • SSL Policy tab: Specify the type of cipher suite to use:
        • TLS Version: Required. Specify the Transport Layer Security (TLS) versions:
          • 1.0
          • 1.1
          • 1.2 (recommended)

          You can select any combination of versions. Choose the ones you want from the list.

          • Specify the Cipher Suite: Required. Choose one of the following options:
            • Select Cipher Suite - Select a predefined set of cipher suites. (default).

              Pick a choice from the Select Cipher Suite list. All cipher suites listed have at least one cipher from each of the TLS versions you selected.

            • Create Custom Cipher Suite - Add ciphers to a new suite.

              Perform the following:

              1. Enter the name of the customer cipher suite in the Suite Name field.
              2. Click Choose Ciphers.

                The Select Ciphers page appears.

              3. Check each cipher that you want to include in the suite.

                The TLS versions associated with each cipher are listed in the Version column. Ensure that any cipher you choose is compatible with the TLS versions you previously chose.

              4. Deselect any ciphers you want to exclude.

                Note

                Assign at least one cipher to a cipher suite you create. You cannot create a cipher suite that contains no ciphers.
              5. Click Select. Then select that custom cipher suite (or whatever suite you want to use) from the Select Cipher Suite list.

            • Click Show Cipher Suite Details to display what ciphers the selected cipher suite contains.
        • Server Order Preference: Select Enable to give preference to the server ciphers over the client.
  4. Click Create Load Balancer.

After the system provisions the load balancer, details appear in the load balancer list. To view more details, click the load balancer name.

Editing Load Balancers

To edit a load balancer
  1. Open the navigation menu. Under the Core Infrastructure group, go to Networking and click Load Balancers.
  2. Choose the Compartment that contains the load balancer you want to edit.
  3. Click the load balancer you want to edit under the Name column.

    The Details page for that load balancer appears.

  4. Click the various links under Resources to edit different aspects of the load balancer as wanted.

    See Creating Load Balancers for details on specific configurations.

Changing the Load Balancer Bandwidth

If you are not an Always Free user, you can adjust the size of the bandwidth to one of the other predefined sizes.

Note

Always Free users cannot change the bandwidth of a load balancer. Upgrade to a different account if you want to increase your bandwidth size.
To change a load balancer's bandwith
  1. Open the navigation menu. Under the Core Infrastructure group, go to Networking and click Load Balancers.

    The Load Balancer page appears listing the load balancers associated with the selected compartment.

  2. Choose the Compartment that contains the load balancer you want to change.
  3. Click the load balancer whose bandwidth you want to change.

    The selected load balancer's Details page appears.

  4. Click Update Shape.

    The Update Shape dialog box appears.

  5. Select the new bandwidth of the load balancer from the Total Bandwidth list. The existing bandwidth size of the load balancer is unavailable to select.

  6. Click Save Changes.

    Changing the bandwidth size of the load balancer requires resetting all existing sessions of the load balancer.

  7. Click Confirm to continue.

    The Details page reappears.

Terminating Load Balancers

To terminate a load balancer
  1. Open the navigation menu. Under the Core Infrastructure group, go to Networking and click Load Balancers.
  2. Choose the Compartment that contains the load balancer you want to delete.
  3. Find the load balancer you want to terminate.
  4. Click the Actions icon (Actions icon) associated with the load balancer you want to delete and then click Terminate.

    Alternatively, you can click the load balancer link to display the Details page and click Terminate.

    You are prompted to confirm you want to terminate the load balancer.

  5. Click Terminate to confirm the termination.

Moving a Load Balancer to a Different Compartment

You can move your load balancer from its current compartment into a different compartment. For information about compartments and access control, see Managing Compartments.

To move a load balancer to a different compartment
  1. Open the navigation menu. Under the Core Infrastructure group, go to Networking and click Load Balancers.
  2. Select a compartment under the List Scope section.
  3. Click the Actions icon (Actions icon) associated with the load balancer you want to move, then click Move Resource.

    The Move Resource dialog box appears.

  4. Choose the destination compartment from the list.
  5. Click Move Resource.

Managing Tags for a Load Balancer

You can apply tags to your resources, such as load balancers, to help you organize them according to your business needs. You can apply tags at the time you create a load balancer, or you can update the load balancer later with the wanted tags. For general information about applying tags, see Resource Tags.

To manage tags for a load balancer
  1. Open the navigation menu. Under the Core Infrastructure group, go to Networking and click Load Balancers.
  2. Choose the Compartment that contains the load balancer you want to tag, and then click the load balancer's name.
  3. Click the Tags tab to view or edit existing tags, or click Apply Tag(s) to add new ones.

For more information, see Resource Tags.

Logging

You can view logging on a variety of load balancer areas, including access and errors. See Details for Load Balancer Logs for more information.

Monitoring Resources

You can monitor the health, capacity, and performance of your Oracle Cloud Infrastructure resources by using metrics, alarms, and notifications. For more information, see Monitoring Overview and Notifications Overview.

For information about monitoring the traffic passing through your load balancer, see Load Balancing Metrics.

Using the API

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

Use these API operations to manage load balancers: