> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/5.1/security/tls-certificate-management.md).

# Manage TLS certificates

Manage TLS certificates to encrypt data in transit and verify system identity, ensuring secure communication in the WEKA cluster.

The TLS implementation in a WEKA cluster secures communication between clients and the system, and between WEKA servers and clients. TLS certificates serve two key purposes:

* **Data Protection:** Encrypting data in transit to ensure confidentiality and integrity.
* **Authentication:** Verifying the system’s identity to prevent unauthorized access.

By default, the WEKA system deploys a self-signed TLS certificate to secure access to the Web UI, CLI, and API over HTTPS (port 14000) . Users can enhance security by deploying their own TLS certificates, which requires providing an unencrypted private key and certificate in PEM format.

The system supports TLS 1.2 and higher, enforcing encrypted communication with a minimum of 128-bit ciphers.

To establish trust with external services, such as a Key Management System (KMS), the system relies on well-known CA certificates. If a custom CA certificate is required for WEKA servers to authenticate external services, manually configure the custom CA certificate on the WEKA servers.

<div data-with-frame="true"><figure><img src="https://2745724548-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZW262oqYA8pNNfGvXjHa%2Fuploads%2FO0lOE6XYf2If5SVqwRND%2FCertificate_topolgy.png?alt=media&amp;token=ad6b7150-0fdb-4d91-9d70-22f5d61e7584" alt="" width="563"><figcaption><p>TLS implementation</p></figcaption></figure></div>

**Related topics**

[Manage TLS certificates using GUI](/5.1/security/tls-certificate-management/manage-the-tls-certificate-using-the-gui.md)

[Manage TLS certificates using CLI](/5.1/security/tls-certificate-management/manage-the-tls-certificate-using-the-cli.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.weka.io/5.1/security/tls-certificate-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.