> 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/ibm-event-streams.md).

# IBM Event Streams

This page describes how to connect Lenses to IBM Event Streams.

{% 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 %}

From the IBM Cloud console, locate your **`bootstrap_endpoints`**. for the service credentials you want to connect with.

In the Lenses bootstrap UI:

1. Set the bootstrap\_endpoints as bootstrap servers
2. Set **`SASL SSL`** as the security protocol
3. Set **`PLAIN`** as the security mechanism
4. Set the\*\*`jaas.conf`\*\* as the following, using the apiKey value as the password.

```bash
org.apache.kafka.common.security.plain.PlainLoginModule required
username="token"
password="[Your API KEY]"
```

{% hint style="info" %}
IBM Event Streams requires a replication factor of 3. Ensure you set the replication factor accordingly for Lenses internal topics.

See [Configuration](https://github.com/lensesio-dev/docs/blob/master/deployment/prepare-your-environment/configuration-reference.md#lenses-internal-kafka-topics).
{% endhint %}


---

# 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/ibm-event-streams.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.