# Configuration Deka SLB After creating Deka SLB, for the next steps, add backend configuration and frontend configuration. On the Load Balancer page, press the Configuration button.

Config Deka SLB

The Load Balancer Configuration page will appear, displaying three tabs.

Config Deka SLB

There are three tabs available on the Load Balancer Configuration page, namely the General tab, Backend tab, and Frontend tab. This section explains some configurations that can be performed. 1. **Add Configuration**, for further details, you can follow the steps in subsections [Add Backend Configuration](#add-backend-configuration) and [Add Frontend Configuration](#add-frontend-configuration). 2. **Edit Configuration**, for further details, you can follow the steps in subsections [Edit Configuration Backend](#edit-backend-configuration) and [Edit Configuration Frontend.](#edit-frontend-configuration) 3. **Delete** **Configuration**, for further details, you can follow the steps in subsections [Delete Configuration](#delete-configuration-backend-frontend). ## **Add Backend Configuration** Here are the steps to add Backend configuration in Deka SLB on the Cloudeka portal service: * Navigate to the Configuration Load Balancer page and click on the Backend tab, then click Create Backend.

Config Backend

* On the Create Backend page, fill in the available form.

Config Backend

ColumnDescription
NameConfigure the backend with a name adhering to the character restrictions of using only A-Z, a-z, and "_" underscore.
Load Balancer MethodIn this column, there are three options available Roundrobin, Least Connection, and Source.
Mode

There are two modes to choose from:

  1. HTTP
  2. TCP
If you select the HTTP protocol in the Mode column, the following columns will appear:

Config Backend

ColumnDescription
Advanced CheckIf you choose HTTP in column Mode, click httpchk.
Http Check Method

You will have 2 options:

  1. GET, used to request data to retrieve information..
  2. POST, used to request the creation of new data.
Http Check URIThis column is used to determine whether the server is active or inactive. In this section, type /_health.php
If you choose the TCP protocol in the Mode column, the following columns will appear.

Config Backend

ColumnDescription
Advanced Check

There are 2 options available:

  1. SSL Hello Check used to ensure that an SSL connection to the backend server can be successfully established.
  2. TCP Check used for checking the availability or health of a TCP connection between two devices or nodes in the network.
After determining the protocol to be used, in the Server section, you can add more than one server if your backend configuration involves multiple VMs or instances. This allows you to configure load balancing for multiple servers, distributing traffic among them based on the chosen algorithm and health check settings.

Config Backend

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.

Config Backend

* A notification will appear "Backend Configuration has successfully created!"

Config Backend

## **Add Frontend Configuration** After you have configured the backend, the next step is to configure the frontend by following these steps: * On the Configuration Load Balancer page click on the Frontend tab, and then click Create Frontend.

Config Frontend

* On the Create Frontend page, fill in the available form.

Config Frontend

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.
If you want to add a Backend configuration press the Add Backend button.

Config Frontend

ColumnDescription
Backend NameBackend configuration name.
ACL NameTo define rules that control access or behavior for specific traffic.
Criteria

To determine whether a request should be directed to a specific backend or not. There are 3 options, namely:

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

These criteria are adjusted based on your selection in the Criteria column.

  1. req.hdr(Host) as an example www.example.com
  2. path_beg for paths starting with “/”. Example: “/example.php”
  3. path_end for paths ending with a specific file extension. Example: “.php”
Condition

There are two options:

  1. Equal used to check if a value is equal to the value entered in the ACL Column.
  2. Not Equal used to check if a value is not equal to the value entered in the ACL column.
ActionThere is a Delete button to remove added Backend configurations.
After determining the Backend configuration to be used, there are other columns that need to be filled.

Config Frontend

ColumnDescription
Bind Address

There are 2 options:

  1. Internet
  2. Internal
Mode

There are 3 options:

  1. HTTPS
  2. HTTP
  3. TCP
If you choose HTTPS in the Mode column, the following columns will appear:

Config Frontend

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 the Mode column selects the **HTTP** or **TCP** protocol, the following columns will appear.

Config friontend - HTTP - TCP

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 the forms on the Create Backend page, click the Create Backend button.

Config Frontend

* If the HTTPS load balancer frontend is successfully created, a notification will appear “Frontend Configuration has successfully created!”.

Config Frontend

## **Edit Backend Configuration** You can modify the backend configuration you've created by following these steps: * On the Backend tab of the Configuration Load Balancer, select Backend configuration you want to update by clicking the Edit button.

Edit Configuration Backend

* The Edit Backend page, you can modify the Load Balance Method, Advanced Check, Http Check Method, Http Check URI, and add Servers by click Add Servers. Then click Update Backend.

Edit Configuration Backend (a)

Edit Configuration Backend (b)

* A notification will appear Backend Configuration has successfully updated!

Edit Configuration Backend Success

## **Edit Frontend Configuration** Here are steps to modify the existing Frontend configuration: * On the Configuration Load Balancer, click on the tab Frontend. Select the frontend configuration you want to update by click the Edit button.

Edit Configuration

* The Edit Frontend page will appear, you can modify Default Backend, Additional Backend if you want to add another backend, click the Add Backend button, Bind Address, and Bind Port. Then click Update Frontend.

Edit Configuration Frontend (a)

Edit Configuration Frontend (b)

* A notification will appear Frontend Configuration has successfully updated! indicating that the frontend Load Balancer configuration has been successfully modified.

Edit Configuration Frontend Success

## **Delete Configuration Backend/Frontend** To delete the backend and frontend configuration in the Deka SLB configuration. The initial step is to delete the frontend configuration and then delete the backend configuration. On the **Configuration Load Balancer page**, on the **Frontend** tab, select the **Delete** button.

Delete Configuration FE

The **Delete Frontend window** appears, **enter the frontend configuration name** and click the **Confirm** button to continue the configuration deletion process.

Delete Configuration FE

Wait until the process is complete and the notification "**Frontend configuration has been successfully deleted**!" appears.

Success Delete Configuration FE

After successfully deleting the frontend configuration, the **next step** is to **delete the backend configuration**. **If you haven't deleted the frontend configuration, a notification will appear "Please detach default backend from frontend configuration!"** On the **Backend** tab, select the **Delete button**.

Delete Configuration BE

The **Delete Backend** window appears, **enter the frontend configuration name** and press the **Confirm** button to continue the configuration deletion process.

Delete Configuration BE

Wait until the process is complete, and a notification will appear “**Frontend configuration has successfully deleted!**”

Success Delete Configuration BE

--- # Agent Instructions: 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: ``` GET https://docs.cloudeka.id/deka_flexi/deka-slb/configuration-deka-slb.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.