Find the Kafka bootstrap endpoint and encrypted authentication settings in PD DigitalOcean Kafka. The module supplies connection information; configuring an application’s topics, consumers and delivery behaviour is a separate task.

Open the connection window

Open the intended client service’s Information page and choose View connection details once the cluster is ready. Enable Client: Connection details on the package. Copy the service’s host, port and username; reveal the masked password with Show only when needed.

Use the displayed endpoint rather than a port copied from a different service or a generic Kafka example. Keep passwords and connection strings containing them out of screenshots, public posts and support messages.

Use the module’s Kafka settings

The released module example uses SASL_SSL and the PLAIN mechanism with the displayed username and password. Authentication is carried over TLS; this is not a plaintext network connection. Configure those settings in the Kafka client you use rather than assuming similarly named fields or another SASL mechanism are interchangeable.

The example’s metadata request helps inspect a connection. It does not create topics, produce a test message, prove consumer permissions or test application delivery. The module does not expose customer topic or consumer-group administration controls in this workflow.

Trust the cluster certificate

Choose Download CA certificate, then configure the client to trust that certificate using its supported CA setting. The module example points to the downloaded CA file. Keep certificate and hostname verification enabled; do not bypass a certificate error by disabling verification.

DigitalOcean’s Kafka connection guide covers provider-side connection methods. Its alternative authentication examples do not establish that this module supplies every certificate, private key or user-management control required for those methods.

Diagnose a connection failure

Check the service’s current state, the application server’s allowed IPv4 source, current username/password, bootstrap host/port, CA trust and SASL settings. A visible Running status or stored endpoint is not a fresh application test; failed provider reads can leave stored information on screen.

Review the error alongside the current service state and client library/version. Do not recreate the Kafka service or repeatedly reset its password to diagnose an unknown connection failure.

See the PD DigitalOcean Kafka Blesta guide for related setup, or explore PD DigitalOcean Kafka.