Configuring Puppet Enterprise Tuning infrastructure nodesUse these guidelines to configure your installation to maximize its use of available system (CPU and RAM) resources. Methods for configuring PEAfter you've installed Puppet Enterprise (PE), optimize it for your environment by configuring and tuning settings as needed. For example, you might want to add your certificate to the allowlist, increase the max-threads setting for http and https requests, or configure the number of JRuby instances. Configuring Puppet ServerAfter you've installed Puppet Enterprise, optimize it for your environment by configuring Puppet Server settings as needed. Configuring PuppetDBAfter you've installed Puppet Enterprise, optimize it for your environment by configuring PuppetDB as needed. Configuring security settingsEnsure your PE environment is secure by configuring security settings. Configuring proxiesYou can work around limited internet access by configuring proxies at various points in your infrastructure, depending on your connectivity limitations. Configuring the consoleAfter installing Puppet Enterprise, you can change product settings to customize the console's behavior. Many settings can be configured in the console itself. Configuring orchestrationAfter installing PE, you can change some default settings to further configure the orchestrator and pe-orchestration-services. Configuring ulimitAs your infrastructure grows and you bring more agents under management, you might need to increase the number allowed file handles per client. Writing configuration files Puppet supports two formats for configuration files that configure settings: valid JSON and Human-Optimized Config Object Notation (HOCON), a JSON superset. Analytics data collectionSome components automatically collect data about how you use Puppet Enterprise. If you want to opt out of providing this data, you can do so, either during or after installing. Static catalogsA catalog is a document that describes the desired state for each resource that Puppet manages on a node. A primary server typically compiles a catalog from manifests of Puppet code. A static catalog is a specific type of Puppet catalog that includes metadata that specifies the desired state of any file resources containing source attributes pointing to puppet:/// locations on a node.