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)
- Navigate to Connections.
- Select Protocol (e.g. Kafka).
- Optionally pick a Platform preset (MSK, Confluent Cloud, Event Hubs, IoT Core, Strimzi, …) to pre-fill fields.
- Enter Broker URL or cloud-specific endpoints.
- Configure TLS/SASL or API keys as required.
- 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
| Protocol | Typical fields |
|---|---|
| Kafka | brokerUrl, SASL mechanism, SSL truststore |
| Pulsar | Service URL, tenant/namespace defaults |
| RabbitMQ | AMQP host, vhost, username/password |
| MQTT | Broker URL, client id, TLS |
| JMS | Artemis/OpenWire URL, destination type |
| Kinesis | Region, stream name, AWS credentials or IAM role |
| GCP Pub/Sub | Project id, credentials JSON |
| Azure Service Bus | Namespace, 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
- Secrets are stored server-side; never log raw passwords in application logs.
- Prefer IAM roles (Kinesis, MSK) or workload identity in Kubernetes over long-lived keys.
- Restrict ingress and enable network policies in Helm for production.