> For the complete documentation index, see [llms.txt](https://docs.lenses.io/latest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lenses.io/latest/devx/5.5/getting-started/connections/kafka/apache-kafka.md).

# Apache Kafka

This page describes connecting Lenses to Apache Kafka.

{% hint style="success" %}
Lenses will not start without a valid Kafka Connection. You can either add the connection via the bootstrap wizard or use [provisioning ](/latest/devx/5.5/deployment/installation/automation.md)for automated deployments.
{% endhint %}

1. Add your bootstrap brokers including ports
2. Optionally, security protocol e.g. SASL\_SCRAM, SASL\_SSL
3. Optionally, SASL Mechanism, e.g. SCRAM-SHA-256

## SSL/TLS Configuration

***

If your Kafka connection requires TLS, set the following

* **Truststore**: The SSL/TLS trust store to use as the global JVM trust store. Available formats are `.jks`, `.p12`, `.pfx`.
* **Keystore**: The SSL/TLS keystore to use for the TLS listener for Lenses. Available format is `.jks`.

## JMX Metrics

Lenses allows you to connect to brokers JMX. Supported formats are:

1. Simple with and without SSL
2. Jolokia (JOLOKIAG and JOLOKIAP)
   1. With and without SSL
   2. With Basic Auth
   3. Custom http requests and suffix
3. AWS Open Monitoring


---

# 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.lenses.io/latest/devx/5.5/getting-started/connections/kafka/apache-kafka.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.