The Conjur architecture utilizes a specific set of ports to maintain high availability and security across a distributed cluster. Port 443 is the primary interface for all HTTPS-based API calls and UI management. Port 444 is a specialized, unauthenticated port used by load balancers to perform health checks without requiring complex credentials. For internal database synchronization, Conjur relies on Port 5432, the standard for PostgreSQL, to replicate data from the Leader to Standbys and Followers. To maintain a centralized audit trail, Port 1999 is dedicated to streaming log data from downstream Followers back to the Leader. Finally, Port 22 is the standard port used for administrative SSH access to the server or container.

CyberArk Conjur Enterprise Documentation: System Requirements - Network Ports. This official resource lists all required ingress and egress ports for the Conjur cluster, including 443 (HTTPS), 444 (Health), 1999 (Audit), and 5432 (Replication).

CyberArk Docs: High Availability and Replication. This section details the PostgreSQL streaming replication mechanism and its reliance on the default database port (5432).

CyberArk Technical Support Knowledge Base: Load Balancer Configuration for Conjur. Explains the logic behind Port 444 for simple HTTP health probes.

PostgreSQL Global Development Group: Chapter 19. Server Configuration. Confirms 5432 as the default port for the communication between the primary database and its replicas.