# Configuration Deka GLB

After creating Deka GLB, the next step i s add backend configuration and frontend configuration. Make sure you already have a VM Instance that uses a floating IP. On the Load Balancer page, click the Configuration button.

The Load Balancer Configuration page appears which displays three labels.

There are three tabs available on the Configuration Load Balancer page including is **General** tab, **Backend** tab, and **Frontend** tab. This section explains several configurations that can be done.

1. **Add Configuration**, for further explanation, can you follow the steps in the sub-chapter **Add Backend Configuration** and **Add Frontend Configuration**.
2. **Edit Configuration,** for further explanation, can you follow the steps in the sub-chapter **Edit Configuration Backend**, and **Edit Configuration Frontend**.
3. **Delete Configuration**, for further explanation, can you follow the steps in the sub-chapter **Delete Configuration**.

### Add Backend Configuration

To add Backend Configuration in Load Balancer, you should add a VM Instance that already has an floating IP. Follow these steps to configure Backend in Load Balancer:

* The Configuration Load Balancer click Backend tab, then click Create Backend.

* The Create Backend page appears, fill in the form provided.

<table><thead><tr><th width="230">Colum</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>The backend configuration and for naming characters can only use A-Z, a-z, and “_” underscore</td></tr><tr><td><strong>Load Balancer Method</strong></td><td><p>In this column there are 3 options including</p><p>Roundrobin, Least Connection, and Source.</p></td></tr><tr><td><strong>Mode</strong></td><td><p>There are 2 Modes including the following:</p><ol><li>HTTP</li><li>TCP</li></ol></td></tr></tbody></table>

If in the Mode column select HTTP protocol, the following columns will appears.

(input gambar disini)

<table><thead><tr><th width="202">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Advanced Check</strong></td><td>If in the Mode column, you select HTTP then click <strong>httpchk</strong>.</td></tr><tr><td><strong>Http Check Method</strong></td><td><p>There are 2 options:</p><ol><li><strong>GET</strong>, used to make data request for retrieve data.</li><li><strong>POST</strong>, used for request to create new data.</li></ol></td></tr><tr><td><strong>Http Check URI</strong></td><td>This column is used to determine whether the server status is active or inactive. In this section type /_health.php</td></tr></tbody></table>

If in the Mode column select TCP protocol, the following column will appear.

(input gambar disini)

<table><thead><tr><th width="207">Colum</th><th>Description</th></tr></thead><tbody><tr><td><strong>Advanced Check</strong></td><td><p>There are 2 options including the following:</p><ol><li><strong>SSL Hello Check</strong> is used to ensure that an SSL connection to the backend server can be established successfully.</li><li><strong>TCP Check</strong> is used to check the availability or health of TCP connection between two devices or nodes in a network.</li></ol></td></tr></tbody></table>

After determining the protocol used, in the Servers section you can add more than one server to use for the Backend configuration. In the Server Name, you can select Other if you add the server used to another organization on Cloudeka portal service.

(input gambar disini)

<table><thead><tr><th width="247">Colum</th><th>Description</th></tr></thead><tbody><tr><td><strong>Servers - Server Name</strong></td><td>VM Instance that have floating IP exist in projects in one organization or another.</td></tr><tr><td><strong>Servers - Server Port</strong></td><td>The port that the server will use.</td></tr><tr><td><strong>Servers - Max Connection</strong></td><td>The maximum number of connections accepted on the server.</td></tr><tr><td><strong>Servers - Weight</strong></td><td>The load that will be received by the server.</td></tr></tbody></table>

* After filling in all the forms on the Create Backend page, click the Create Backend button.

* A notification Backend Configuration has successfully created!.

(input gambar disini)

### Add Frontend Configuration

After you configure backend, for next step configure frontend following these stepsuntuk langkah selanjutnya mengkonfigurasi frontend dengan mengikuti tahpan berikut:

* On the Configuration Load Balancer click Frontend tab , and click Create Frontend.

* The Create Frontend page appears, fill in the form provided.

(input gambar disini)

<table><thead><tr><th width="212">Colum</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Frontend configuration name and for frontend naming characters only A-Z, a-z, and _ underscore</td></tr><tr><td><strong>Default Backend</strong></td><td>Select the backend that was previously created.</td></tr></tbody></table>

If you want to add a Backend configuration press the Add Backend button.

(input gambar disini)

<table><thead><tr><th width="198">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Backend Name</strong></td><td>Backend configuration name.</td></tr><tr><td><strong>ACL Name</strong></td><td>To define rules that control access or behavior of specific traffic.</td></tr><tr><td><strong>Criteria</strong></td><td><p>To determine whether a request should be directed to a specific backend or not. There are 3 options including:</p><ol><li><strong>req.hdr(Host)</strong> is criteria that checks the value of the Host header in an HTTP request.</li><li><strong>path_beg</strong> is this criterion checks whether the request URL path starts with a certain value.</li><li><strong>path_end</strong> is this criterion checks whether the request URL path ends with a certain value.</li></ol></td></tr><tr><td><strong>Value</strong></td><td><p>This column adjusts from your selection in the Criteria column.</p><ol><li><strong>req.hdr(Host)</strong> for example www.example.com</li><li><strong>path_beg</strong> is a path that starts with a path prefix“/”. Example:“/example.php”</li><li><strong>path_end</strong> is the path that a particular file extension ends with. Example:“.php”</li></ol></td></tr><tr><td><strong>Condition</strong></td><td><p>There are two options among them:</p><ol><li><strong>Equal</strong> used to checkwhether a value is the same as the value entered in the ACL column.</li><li><strong>Not Equal</strong> used to check whether a value is not the same as the value entered in the ACL column.</li></ol></td></tr><tr><td><strong>Action</strong></td><td>There is a Delete button to delete the Backend configuration that has been added.</td></tr></tbody></table>

After determining the Backend configuration used, there are other columns that must be filled in.

(input gambar disini)

<table><thead><tr><th width="181">Colum</th><th>Description</th></tr></thead><tbody><tr><td><strong>Bind Address</strong></td><td>Because Deka GLB configuration select Internet.</td></tr><tr><td><strong>Mode</strong></td><td><p>There are 3 options:</p><ol><li>HTTPS</li><li>HTTP</li><li>TCP</li></ol></td></tr></tbody></table>

If you select HTTPSin the Mode column, the following columns will appear:

(input gambar disini)

<table><thead><tr><th width="166">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Bind Port</strong></td><td>By default it used port 443.</td></tr><tr><td><strong>Certificate File</strong></td><td>You can upload the certificate file that you have. If you use the Cloudeka Portal Service, namely Deka SSL, you can download files in the SSL menu in the SSL Menu in the Manage Module.</td></tr><tr><td><strong>Key File</strong></td><td>You can upload the key file that you have. If you use the Cloudeka Portal Service, namely Deka SSL, you can download files in the SSL Menu in the Manage Module.</td></tr></tbody></table>

If the Mode column select the HTTP protocol or TCP protocol, the following columns will appear:

(input gambar disini)

<table><thead><tr><th width="199">Column</th><th>Description</th></tr></thead><tbody><tr><td><strong>Bind Port</strong></td><td><p>Determine the protocol used</p><ol><li>The HTTP protocol is immediately filled with port 80,</li><li>The TCP protocol determines the port to be used</li></ol></td></tr></tbody></table>

* After filling in all the forms on the Create Backend page, click the Create Backend button.

* A notification “Frontend Configuration has successfully created!”.

(input gambar disini)

### Edit Backend Configuration

The following are the steps for update the Deka GLB backend configuration:

* On the page Configuration Load Balancer, click Backend tab. On backend\_satu in the Backend Name column, click the Edit button.

* The Edit Backend page, the only things that can be changed are the Load Balance Method, Advanced Check, Http Check Method, Http Check URI, and you can add Servers by clingking Add Servers. Then click Update Backend.

* A notification Backend Configuration has successfully updated!

(input gambar disini)

### Edit Frontend Configuration

You can change frontend configuration that you have created by following that you have created by following these steps:

* On the page Configuration Load Balancer, click tab Frontend. On frontend\_satu in the Frontend Name column, click Edit button.
* The Edit Frontend page, only the columns that can be change Default Backend, Additional Backend if you want to add another Backend by button click Add Backend, Bind Address, and Bind Port. Then click Update Frontend button.
* A notification Frontend Configuration has successfully updated! That the Load Balancer frontend configuration has been updated.

(input gambar disini)

### Delete Backend/Frontend Configuration

To delete backend and frontend configuration in Deka GLB configuration. The initial step isto delete the frontend configuration and then delete the backend configuration. On the Configuration Load Balancer in Frontend tab. Select Delete button.

Display the Delete Frontend window, enter the name of the frontend configuration and click the Confirm button to continue deletion process.

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

After successfully deleting the frontend configuration, the next step is to delete the backend configuration. If you have not deleted the frontend configuration, a notification will appear “Please detach default backend from frontend configuration!” On the Backend tabselect the button Delete.

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

Wait until the process is complete and the notification "Frontend 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:

```
GET https://docs.cloudeka.ai/guidance-for-individual/deka-flexi/deka-glb/configuration-deka-glb.md?ask=<question>
```

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.
