Skip to main content

High Availability Overview


We are currently working on making the setup and upgrade process to Automate HA a seamless experience. If you are already using Chef Automate HA, or are planning to use it, please contact your customer success manager or account manager for more information.

High availability (HA) refers to a system or application that offers a high level of operational availability. This means that the entire site or application will not be down if one server goes down due to traffic overload or other issues. HA represents the application remains available with no interruption. We achieve high availability when an application continues to operate even when one or more underlying components fail.

Thus, HA is designed to avoid loss of service by reducing or managing failures and minimizing unscheduled downtime (when your system or network is not available for use or is unresponsive) that happens due to power outages or failure of a component.

Chef Automate High Availability (HA)

The Chef Automate HA equates to reliability, efficiency, and productivity, built on Redundancy and Failover. It aids in addressing significant issues like service failure and zone failure.

Chef Automate HA Architecture

HA architecture includes the cluster of the Chef Automate, Chef Server, Postgres, and OpenSearch.

Chef Automate HA Architecture for OnPremise / AWS Non-Managed

High Availability Architecture

Chef Automate HA Architecture for AWS Managed

High Availability Architecture


Chef Automate HA for Managed Services has default port 7392 for Managed Postgresql and 9200 for Managed Opensearch. You can also change to your custom port.

Chef Automate HA Architecture for AWS OnPremise / AWS Non-Managed Minimum Node Cluster

High Availability Architecture

Chef Automate HA Topology

The Chef Automate HA Architecture involves the following clusters as part of the main cluster:

  • Backend Cluster (Persistent Services)

    • Postgres: Database requires a minimum of three nodes. Postgres database uses the Leader-Follower strategy, where one becomes a leader, and the other two are the followers.

    • OpenSearch: Database requires a minimum of three nodes. OpenSearch database manages the cluster internally.

  • Frontend Cluster (Application Services)

Deployment Methods

Chef Automate High Availability (HA) supports two types of deployment:

On-premise Deployment (Existing Node/Bare Infrastructure)

In this, we expect VM (Virtual machine) or Bare Metal machines (Physical machine) that are already created and have initial Operating System (OS) setup done. Including Ports and Security policies changed according to requirements.

After this, installation steps will Deploy Chef Automate, Chef Infra Server, Postgresql DB, and OpenSearch DB to the relevant VMs or Physical Machines as provided in Config.

Cloud Deployment using Amazon Web Services (AWS)

The two-step deployment process is as shown below:

  • Provisioning Infrastructure. (Optional, if already manually done)
  • Deployment of services on the provisioned infrastructure.
    • Installation of PostgreSQL, OpenSearch, Chef Automate, and Chef Infra Server will be done in this step.
Edit this page on GitHub.

Thank you for your feedback!


Search Results