> For the complete documentation index, see [llms.txt](https://docs.cloudeka.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudeka.ai/deka-slb/configuration-deka-slb.md). # Configuration Deka SLB After creating Deka SLB, continue by adding the backend and frontend configurations. On the **Load Balancer** page, click **Configuration**. The **Load Balancer Configuration** page appears with three tabs. The available tabs are **General**, **Backend**, and **Frontend**. This section explains the available configuration actions. 1. **Add Configuration** — follow the steps in **Add Backend Configuration** and **Add Frontend Configuration**. 2. **Edit Configuration** — follow the steps in **Edit Backend Configuration** and **Edit Frontend Configuration**. 3. **Delete Configuration** — follow the steps in **Delete Configuration Backend/Frontend**. ### **Add Backend Configuration** Follow these steps to add a backend configuration in Deka SLB on the Cloudeka portal service: * Open the **Configuration Load Balancer** page, click the **Backend** tab, then click **Create Backend**. * On the **Create Backend** page, fill in the available form.
ColumnDescription
NameEnter a backend name using only A-Z, a-z, and the underscore character (_).
Load Balancer MethodThere are three available methods: Roundrobin, Least Connection, and Source.
Mode

There are two available modes:

  1. HTTP
  2. TCP
If you select **HTTP** in the **Mode** field, the following fields will appear:
ColumnDescription
Advanced CheckIf you choose HTTP in the Mode field, select httpchk.
Http Check Method

There are two available options:

  1. GET — requests data from the server.
  2. POST — sends data to create a new resource.
Http Check URIUse this field to check whether the server is active. In this example, enter /_health.php.
If you choose **TCP** in the **Mode** field, the following field will appear.
ColumnDescription
Advanced Check

There are two available options:

  1. SSL Hello Check — checks whether an SSL connection to the backend server can be established.
  2. TCP Check — checks the availability or health of the TCP connection.
After selecting the protocol, go to the **Server** section. You can add more than one server if the backend uses multiple VMs or instances. This allows the load balancer to distribute traffic based on the selected algorithm and health check settings.
ColumnDescription
Servers - Server NameVM instances that have been deployed to the VPC connected to Deka SLB.
Servers - Server PortThe port that the server will use.
Servers - Max ConnectionThe maximum number of connections accepted by the server.
Servers - WeightThe load that will be received by the server.
* After filling out all the forms on the Create Backend page, click the Create Backend button. * A notification will appear: **Backend Configuration has successfully created!** ### **Add Frontend Configuration** After the backend is configured, continue with the frontend configuration by following these steps: * On the **Configuration Load Balancer** page, click the **Frontend** tab, then click **Create Frontend**. * On the **Create Frontend** page, fill in the available form.
ColumnDescription
NameThe name of the frontend configuration, and the allowed characters for frontend naming are only A-Z, a-z, and "_" underscore.
Default BackendSelect the previously created backend.
ColumnDescription
NameEnter a frontend configuration name using only A-Z, a-z, and the underscore character (_).
Default BackendSelect the backend that was created earlier.
If you want to add another backend configuration, click **Add Backend**.
ColumnDescription
Backend NameThe backend configuration name.
ACL NameDefines a rule that controls access or behavior for specific traffic.
Criteria

Determines whether a request should be directed to a specific backend. There are three available options:

  1. req.hdr(Host) — checks the value of the Host header in the HTTP request.
  2. path_beg — checks whether the request URL path starts with a specific value.
  3. path_end — checks whether the request URL path ends with a specific value.
Value

This value depends on the selected criteria.

  1. req.hdr(Host) — for example, www.example.com
  2. path_beg — for a path starting with /, for example /example.php
  3. path_end — for a path ending with a file extension, for example .php
Condition

There are two available options:

  1. Equal — checks whether the value matches the ACL value.
  2. Not Equal — checks whether the value does not match the ACL value.
ActionUse the Delete button to remove an added backend configuration.
After selecting the backend configuration, complete the remaining fields.
ColumnDescription
Bind Address

There are two available options:

  1. Internet
  2. Internal
Mode

There are three available options:

  1. HTTPS
  2. HTTP
  3. TCP
If you choose **HTTPS** in the **Mode** field, the following fields will appear:
ColumnDescription
Bind PortBy default, it uses port 443.
Certificate FileYou can upload the certificate file you possess. If you are usign the Cloudeka Portal Service, namely Deka SSL, you can download the file in the SSL menu under the Manage Module.
Key FileYou can upload the key file you possess. If you are using the Cloudeka Portal Service, namely Deka SSL, you can download the file in the SSL menu under the Manage Module.
If you select **HTTP** or **TCP** in the **Mode** field, the following field will appear.
ColumnDescription
Bind Port

Adjusting to the protocol used:

  1. If the HTTP Protocol is selected, it will be automatically filled with port 80.
  2. If the TCP Protocol is selected, specify the port to be used.
* After filling out all fields on the **Create Frontend** page, click **Create Frontend**. * If the frontend is created successfully, a notification will appear: **Frontend Configuration has successfully created!** ### **Edit Backend Configuration** You can modify an existing backend configuration by following these steps: * On the **Backend** tab of the **Configuration Load Balancer** page, select the backend configuration you want to update, then click **Edit**. * On the **Edit Backend** page, you can update the **Load Balance Method**, **Advanced Check**, **Http Check Method**, **Http Check URI**, and add servers by clicking **Add Servers**. Then click **Update Backend**. * A notification will appear: **Backend Configuration has successfully updated!** ### **Edit Frontend Configuration** Follow these steps to modify an existing frontend configuration: * On the **Configuration Load Balancer** page, click the **Frontend** tab. Select the frontend configuration you want to update, then click **Edit**. * On the **Edit Frontend** page, you can update the **Default Backend**, **Additional Backend**, **Bind Address**, and **Bind Port**. If you want to add another backend, click **Add Backend**. Then click **Update Frontend**. * A notification will appear: **Frontend Configuration has successfully updated!** ### **Delete Configuration Backend/Frontend** To delete backend and frontend configurations in Deka SLB, delete the frontend configuration first, then delete the backend configuration. On the **Configuration Load Balancer** page, open the **Frontend** tab, then click **Delete**. The **Delete Frontend** window appears. Enter the frontend configuration name, then click **Confirm** to continue. Wait until the process is complete and the notification **Frontend configuration has been successfully deleted!** appears. After the frontend configuration is deleted, continue by deleting the backend configuration. If the frontend configuration has not been deleted yet, a notification will appear: **Please detach default backend from frontend configuration!** On the **Backend** tab, click **Delete**. The **Delete Backend** window appears. Enter the backend configuration name, then click **Confirm** to continue. Wait until the process is complete, and a notification will appear: **Backend configuration has been successfully deleted!** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.cloudeka.ai/deka-slb/configuration-deka-slb.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.