Connections

Create, test, and manage broker profiles with platform presets and secure credentials.

Overview

A connection stores protocol, endpoints, and optional auth. The UI only lists protocols from the control plane cascade (connectionProtocols), not a hardcoded list. Open the stream guide for your protocol (Kafka, MQTT, Pulsar, …) or compare all platforms.

Creating a connection (UI)

  1. Navigate to Connections.
  2. Select Protocol (e.g. Kafka).
  3. Optionally pick a Platform preset (MSK, Confluent Cloud, Event Hubs, IoT Core, Strimzi, …) to pre-fill fields.
  4. Enter Broker URL or cloud-specific endpoints.
  5. Configure TLS/SASL or API keys as required.
  6. Save, then Test connection to validate reachability.

REST API example

Kafka (local)

curl -X POST http://localhost:8080/api/v1/connections \
  -H "Content-Type: application/json" \
  -d '{
    "name": "local-kafka",
    "protocol": "KAFKA",
    "brokerUrl": "localhost:9092"
  }'

Test connection

curl -X POST http://localhost:8080/api/v1/connections/{id}/test

List connections

curl http://localhost:8080/api/v1/connections

Per-protocol notes

ProtocolTypical fields
KafkabrokerUrl, SASL mechanism, SSL truststore
PulsarService URL, tenant/namespace defaults
RabbitMQAMQP host, vhost, username/password
MQTTBroker URL, client id, TLS
JMSArtemis/OpenWire URL, destination type
KinesisRegion, stream name, AWS credentials or IAM role
GCP Pub/SubProject id, credentials JSON
Azure Service BusNamespace, shared access key or Entra ID
READONLY mode: connection create/update/delete returns 403. Use pre-provisioned profiles or switch to ADMIN/DEV for management.

Security