System requirements for Conjur Server

This topic describes the system requirements for a Conjur Server Docker Image.

Hardware requirements

  • Proof-of-concept (POC) deployments using auto-failover must use the production requirements. The development requirements are sufficient for tests of the API and Conjur CLI.

  • We recommend using the Conjur Inspect tool to ensure that the deployed infrastructure meets the following recommended system requirements.

The following table describes the recommendations for the Conjur Server host machine (Leader, Standbys, and Followers):

Conjur server hardware requirements

Deployment model

Environment

Leader and Standby

Follower and DR

On-premises

 

Production

4 core x86/x64 processors

16 GB RAM

50 GB disk space

For auto failover, a local high-performance SSD is required

4 core x86/x64 processors

16 GB RAM

50 GB disk space

Development

2 core x86/x64 processors

4 GB RAM

20 GB disk space

For auto failover, a local high-performance SSD is required

2 core x86/x64 processors

4 GB RAM

20 GB disk space

Cloud

 

Production

M5.xl using gp3 EBS storage

For auto failover, use M5d.4xl using local SSD storage

M5.xl using gp3 EBS storage

Development

M5.large using gp3 EBS storage

For auto failover, use M5d.2xl using local SSD storage

M5.large using gp3 EBS storage

The recommendations for the cloud deployment model are for AWS environments. We recommend similar instance types for other cloud providers.

Supported container platforms

Platform Version

Docker/Mirantis Container Runtime (MCR)

Supports Leader, Standbys, and Followers

Version 20.10 or later on RHEL 8.x and RHEL 9.x

For more information about Conjur requirements for Docker, see Docker container requirements.

For platform installation instructions, see the Docker documentation.

Kubernetes and OpenShift

Supports Followers only. For details about which container platform versions are supported, see Supported Kubernetes-based environments.

Podman

Supports Leader, Standbys, and Followers

Version 4.x on RHEL 8.x and RHEL 9.x

See the Podman installation documentation for more information.

We recommend using the latest stable version.

  • Although it is provided as a Docker container, the Conjur Server cannot be deployed as a Leader or a Standby on container orchestration platforms such as Kubernetes.

  • Podman is CLI-compatible with the Docker CLI. You can configure alias docker=podman for the shell that sets up the Conjur Server. This way, all the docker commands can be used when working with Podman.

    Alternatively, you can manually replace docker in each command with podman.

    All references to Docker in this document apply to Podman as well.