# Plan a private route for a broker consumer

A broker endpoint service is part of the infrastructure that hosts your consumer and broker. It is not configured by Coordinator DB SQL. The destination database needs only a reachable native or HTTP listener and valid credentials.

## Draw the client connections

Identify the host running the consumer, the broker addresses it must resolve and the database address it will use. Check DNS resolution and network access from that host rather than from an administrator's laptop. A test from another network can succeed while the actual importer remains unable to connect.

Keep the broker's authentication and certificate configuration with the consumer. Configure Coordinator DB credentials independently. If the route includes a proxy or tunnel, test both a readiness request and a small authenticated INSERT followed by SELECT.

## Make failures attributable

Record which connection failed, the destination hostname, the time and the available request identifier. Do not send secrets or full private records in a support example. A retry policy should distinguish a failed connection from an ambiguous write response; only the latter needs destination reconciliation.

Coordinator DB does not advertise a broker endpoint service or provide a cloud networking API. Use your infrastructure provider's documented tooling for those resources.

See [native client](https://coordinatordb.com/docs/concepts/features/interfaces/client), [HTTP authentication](https://coordinatordb.com/docs/concepts/features/interfaces/http) and [configuration files](https://coordinatordb.com/docs/concepts/features/configuration/server-config/configuration-files).