Introduction to Clustering with BeyondTrust Atlas Technology

A graphic displaying a globe.

BeyondTrust Atlas Technology is designed for large scale geographical deployments of BeyondTrust. With Atlas, you use a single BeyondTrust site across multiple appliances. Since the administration is primarily performed on a master appliance, Atlas has minimal administration impact.

This paper describes what comprises BeyondTrust Atlas Technology, how it works at a high level, and the different deployment options for you to consider.

Should you need any assistance, please contact BeyondTrust Technical Support at



The BeyondTrust technology which enables Secure Remote Access Appliances to be deployed in a cluster.


The collective representation of all appliances that are participating in the same BeyondTrust environment.

Primary Master Node

The node where a majority of the configuration takes place, such as creating users, defining public sites, configuring support teams, defining traffic nodes, etc. Essentially, everything that you would typically do in a single appliance BeyondTrust installation /login interface will be done through the designated master node for your clustered environment.

Backup Master Node

This node is in a configured failover relationship with the primary master node. In the event of a system failure on the primary node, the backup node can take over the role as primary master node.

Traffic Node

This node normally handles the bulk of session traffic for the representative console and the customer client. Both the representative console and the customer client bind to a traffic node, as well as the master node, during a session. The traffic node that is chosen will be determined by the various configuration options.

Inter-appliance Communication Pre-shared Key

This is a password that must be set on all of the appliances participating in a cluster. This key must match between appliances in order to replicate information between them and to allow them to participate in the cluster.