CyberArk Privileged Session Manager supports horizontally scaled deployments in which multiple PSM servers operate behind a load balancer. This architecture distributes privileged sessions across available servers and increases service availability.
When implementing a PSM farm with a physical load balancer, each PSM server must independently expose its health status. The PSM Health Check integration provides an application-level mechanism for determining whether the individual PSM instance is operational.
The health-check service should be installed and configured on both PSM servers. The load balancer must query each server's health-check endpoint rather than relying exclusively on network connectivity.
A typical endpoint is /psm/api/health , subject to the deployed PSM Health Check version.
The least-connections algorithm distributes new connections toward the server handling fewer active connections. This is useful because privileged sessions can have substantially different durations.
If a PSM instance becomes unavailable, health monitoring allows the load balancer to exclude it from new session assignments.
A single health-check deployment cannot reliably report the independent application status of both servers. Furthermore, PSM supports external load-balancing solutions and is not restricted to round-robin distribution.
[Reference:CyberArk Privileged Session Manager — Load-Balancing Architecture, PSM Health Check, Application-Level Monitoring and PSM Farm Configuration.]
Submit