--- title: Load Balancer Info Tab --- # Load Balancer Info Tab The **Info** tab is the home of a load balancer's details. It shows configuration in two panels — **Basic** and **Peak Performance Features** — and lets you edit several settings in place. The Info tab is always available, regardless of status. This page covers every field and inline action on the Info tab. For lifecycle operations such as start, power off, upgrade, and delete, see [Actions](/docs/myaccount/load-balancer/manage/actions). :::note Inline edits are disabled while the load balancer is **Powered off**, **Creating**, **Deploying**, **Upgrading**, or **Terminating**. The portal shows a message such as "You can't edit Load Balancer in '\' state." Bring the load balancer to **Running** before editing. ::: --- ## Basic Panel | Field | What it shows | Inline action | | ------------------ | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- | | Load Balancer Name | The load balancer's name. | **Edit** — rename (letters, digits, hyphen, underscore). | | Public IP | The assigned public IP, or **None**. | Copy the IP; **Reserve Public IP** where the address can be reserved. Shown only for an external load balancer. | | Private IP | The first private IP from the attached VPC, or the node's private IP. | Copy the IP. | | Plan Name | The current plan, or **Private Cloud** for a private-cluster load balancer. | **Upgrade Plan** where eligible. | | Configuration | RAM, vCPU, and storage of the plan (for example, "4 GB RAM 2 VCPU 20 GB Storage"). | — | | Price | The current price for the plan, in your account currency. | — (hidden for Private Cloud). | | Access Details | **Enabled** or **Disabled** for access logs. | **Activate** / **Deactivate** access logs (shown only when Running or Backend Connection Failure). | | Frontend Protocol | The client-facing protocol — HTTP, HTTPS, or Both for an ALB; TCP for an NLB. | **Edit** (ALB only). | | SSL | The attached SSL certificate name, or **None** (ALB only). | **Edit** — choose an imported certificate. | | LB Listening Port | The port the load balancer accepts traffic on. | — | | Created On | When the load balancer was created. | — | | Last modified on | When it was last changed. | — | ### Edit Name, Frontend Protocol, or SSL Selecting **Edit** on the name, frontend protocol, or SSL opens a form where you can change: - **Name** — required; letters, digits, hyphen, and underscore only. - **Frontend Protocol** — **HTTP**, **HTTPS**, or **Both (HTTP and HTTPS)**. This controls the protocol between the client and the load balancer. - **SSL** — shown when the protocol is HTTPS or Both. Select an imported certificate, or use **Buy or Import SSL Certificate** to open the Certificate Manager. See [SSL Certificates](/docs/myaccount/load-balancer/features/ssl-certificates). - **HTTP Redirect** — a checkbox shown when the protocol is HTTPS or Both (see the Peak Performance Features panel below). ### Access Logs Access logs capture request-level data and store it in an E2E object storage (EOS) bucket you specify. Use **Activate** / **Deactivate** next to **Access Details** on the Info tab. To enable, provide: | Field | Requirement | | ---------- | ---------------------------------------------------------------------------------------------- | | EOS Bucket | The bucket that will store the logs. Up to 50 characters; letters, digits, hyphen, underscore. | | Access Key | The access key for the bucket. 12–32 characters. | | Secret Key | The secret key for that access key. 24–64 characters. | After activation, request logs appear under [Action Logs](/docs/myaccount/load-balancer/manage/logs#action-logs). The portal reminds you to "Activate Access Logs to view logs" until you do. You can disable access logging at any time. :::note For buckets and keys, see [Object Storage](/docs/myaccount/storage/object_storage) and [Object Storage Access Keys](/docs/myaccount/storage/object_storage/access_key). ::: ### Committed-Plan Details When the load balancer is on a committed plan, the Basic panel also shows: - **Active Committed Plan** — the committed period and rate (for example, "1 Year at ₹…/month"). - **Committed Period Ends On** — the end date of the commitment. - **Committed Node Settings** — the end-of-period behavior: "Auto renew committed period", "Apply hourly billing price", or "Auto deletion of Load Balancer". A tooltip notes this applies after the current committed period ends. To convert to committed or change these settings, see [Actions › Committed Load Balancer](/docs/myaccount/load-balancer/manage/actions#committed-load-balancer). --- ## Peak Performance Features Panel | Field | What it shows | Inline action | | ----------------------- | --------------------------------- | ---------------------------------------------- | | BitNinja | **Enabled** or **Disabled**. | **Buy** or **Terminate** the BitNinja license. | | HTTP Redirect | **True** or **False** (ALB only). | **Edit** — toggle Redirect HTTP to HTTPS. | | Connection Timeout | The current value (default 60). | **Edit** — 60–10000. | | Client Timeout | The current value (default 60). | **Edit** — 60–10000. | | Server Timeout | The current value (default 60). | **Edit** — 60–10000. | | HTTP Keep Alive Timeout | The current value (default 60). | **Edit** — 60–10000. | :::note **HTTP Redirect** can only be enabled when the front-end protocol is **HTTPS** or **Both**. The portal shows: "Ensure to select mode as 'HTTPS or Both' to enable HTTP Redirect." ::: ### BitNinja [BitNinja](/docs/myaccount/security/bitninja/) is a server security tool that defends the load balancer against attacks. - When disabled, the panel shows "Buying BitNinja license will protect your server from malicious attacks." Select **Buy** to purchase a license; you are charged per calendar month and receive an activation email. - When enabled, select **Terminate** to cancel the license. You can buy a new license later, billed as a new license. The Buy/Terminate control is disabled while the load balancer is Powered off, Creating, Deploying, Upgrading, or Terminating. ### Timeouts Edit the connection, client, server, and HTTP keep-alive timeouts to match your traffic. Each value is between 60 and 10000. Changes redeploy the load balancer. --- ## Related Resources | Resource | Use it for | | --------------------------------------------------------------------------- | -------------------------------------------------------- | | [Manage Load Balancers](/docs/myaccount/load-balancer/manage) | The management hub and tab overview. | | [Actions](/docs/myaccount/load-balancer/manage/actions) | Start, power off, upgrade, convert to committed, delete. | | [SSL Certificates](/docs/myaccount/load-balancer/features/ssl-certificates) | Import and attach certificates for HTTPS. | | [Backend Mapping](/docs/myaccount/load-balancer/manage/backends) | Manage backend groups and servers. |