To connect Confluent Cloud to PeerDB, you need a Confluent Cloud account with Kafka Server running.
And then in UI you can create the Confluent Cloud / Kafka peer like so:
Create Peer
Kafka
Name
use a desired name, e.g. confluent_kafka_1
, only lowercase alphanumeric and underscores are allowed.Bootstrap Servers
use the bootstrap.servers
value from the previous step. Multiple servers can be specified as a comma separated list.Security Protocol
use SASL_SSL
.SASL Mechanism
use PLAIN
.Username
use the CLUSTER_API_KEY
from the previous step.Password
use the CLUSTER_API_SECRET
from the previous step.Validate Connection
Create Peer
PeerDB only supports plaintext and SASL authentication. If username isn’t supplied then PeerDB will attempt to connect without authentication.
Partitioner can be usually be ignored; it maps to partitioning strategies in franz-go. To set partitioning keys you’ll need to specify Script
when creating mirror, see Lua reference for details.
To connect Confluent Cloud to PeerDB, you need a Confluent Cloud account with Kafka Server running.
And then in UI you can create the Confluent Cloud / Kafka peer like so:
Create Peer
Kafka
Name
use a desired name, e.g. confluent_kafka_1
, only lowercase alphanumeric and underscores are allowed.Bootstrap Servers
use the bootstrap.servers
value from the previous step. Multiple servers can be specified as a comma separated list.Security Protocol
use SASL_SSL
.SASL Mechanism
use PLAIN
.Username
use the CLUSTER_API_KEY
from the previous step.Password
use the CLUSTER_API_SECRET
from the previous step.Validate Connection
Create Peer
PeerDB only supports plaintext and SASL authentication. If username isn’t supplied then PeerDB will attempt to connect without authentication.
Partitioner can be usually be ignored; it maps to partitioning strategies in franz-go. To set partitioning keys you’ll need to specify Script
when creating mirror, see Lua reference for details.