About Enterprise Chef 11.1

Chef is a systems and cloud infrastructure automation framework that makes it easy to deploy servers and applications to any physical, virtual, or cloud location, no matter the size of the infrastructure. Each organization is comprised of one (or more) workstations, a single server, and every node that will be configured and maintained by the chef-client. Cookbooks (and recipes) are used to tell the chef-client how each node in your organization should be configured. The chef-client (which is installed on every node) does the actual configuration.

The Enterprise Chef is a centralized location where all of the objects needed by Chef are stored, including data that has been uploaded from the chef-repo, data that is needed by the chef-client while it configures nodes, and data that is uploaded to the Chef server by the chef-client at the conclusion of every chef-client run.


This set of topics is only about the Enterprise Chef server, version 11.1. For information about the chef-client, Ohai, cookbooks, and so on, see https://docs.chef.io/.

View the release notes for Enterprise Chef 11.1.

Server Essentials

The server acts as a hub for all of the data needed by the chef-client while it configures a node:

  • A node object exists for each node that is being managed by the chef-client
  • Each node object consists of a run-list and a collection of attributes
  • Cookbooks are the fundamental unit of configuration and policy distribution and include: attribute files , definitions , files, , libraries , metadata , recipes , resources , templates , and versions
  • All data that is stored on the Chef server—including everything uploaded to the server from the chef-repo and by the chef-client—is searchable from both recipes in the Recipe DSL) and the workstation (using the knife search <knife_search> subcommand). The chef-client does the actual configuration on the nodes . The chef-client receives its instructions from cookbooks (recipes , mostly). The process of configuring a node is called the chef-client run . At the beginning of each run, the chef-client validates to the server , collects important data about that node , and then configures the node. At the end of each run, the chef-client reports the successes and failures that may have occurred
  • The Chef server can apply global policy settings to all nodes across the organization, including for data bags , environments , and roles
  • The authentication process ensures that requests can only be made to the Chef server by authorized users
  • Users, once authorized can only perform certain actions

Server Components

The Enterprise Chef acts as a hub for configuration data. The components that make up the server work together to store cookbooks, provide a management layer, and databases that store cookbook and node data.

Deployment Scenarios

There are several configuration options for the Chef server: hosted by Chef, all on a single machine (standalone), multiple machines and a scaled front end, multiple machines and a scaled back end, or multiple machines with both scaled front and back ends.

The following sections discuss these deployment configuration options in greater detail:

Standalone Scaled Back End Scaled Front End Scaled Front and Back Ends


For more information about signing up for hosted Enterprise Chef, see https://manage.chef.io/signup.

Manage Enterprise Chef

The Chef server can be managed in the following ways:

Backup and Restore Firewalls and Ports High Availability LDAP and Active Directory Logs Monitor Server Tuning Security Services Users

Settings and Tools

The following settings files are used to configure behavior for the Chef server:


The following command-line tools can be run on the Chef server:

orgmapper private-chef-ctl (executable)


The following APIs can be used to access data on the Chef server:

Chef Server API