PE Bolt server configuration
The PEBolt server provides an API for running tasks over SSH and
WinRM using Bolt, which is the technology underlying PE tasks. You do not need to have Bolt installed to
configure the Bolt server or run tasks in PE. The API server for tasks is available as pe-bolt-server.
Bolt vs ACE: Orchestrator uses both ACE and Bolt to run tasks and plans. While both can act on
agentless targets, the primary difference is that Bolt server works with agentless nodes over WinRM or SSH, whereas ACE works with
agentless devices, like network switches and firewalls, over other
transports.
The PEBolt server is a Puma application that runs as a standalone service.
The server is configured in /etc/puppetlabs/bolt-server/conf.d/bolt-server.conf,
managed by the puppet_enterprise::profile::bolt_server class, which
includes the parameters described in the following table:
| Setting | Type | Description | Default |
|---|---|---|---|
bolt_server_loglevel
|
String | Bolt log level. Acceptable values
are debug, info,
notice, warn, or
error. |
notice
|
concurrency
|
Integer | Maximum number of server threads. | 100
|
master_host
|
String | URI of the primary server where Bolt can download tasks. | $puppet_enterprise::puppet_master_host
|
master_port
|
Integer | Port the Bolt server can access the primary server on. | $puppet_enterprise::puppet_master_port
|
ssl_cipher_suites
|
Array of strings | TLS cipher suites in order of preference. | $puppet_enterprise::params::secure_ciphers
|
ssl_listen_port
|
Integer | Port the Bolt server runs on. | 62658 ( |
allowlist
|
Array of strings | List of hosts that can connect to pe-bolt-server. |
[$certname]
|
