Deploy Boundary in a self-managed environment

To deploy a self-managed Boundary environment you should:

1. Install the Boundary binary
2. Deploy and configure Boundary controllers and workers
3. Install end-user clients

Deploying a self-managed Boundary cluster means installing the binary, configuring controllers and workers, and initializing the database, as defined in the Recommended architecture topic. It assumes you install Boundary on virtual machines (VMs) or bare-metal servers running a Debian or Red Hat-based Linux distribution.

To deploy HCP (HashiCorp Cloud Platform) Boundary instead, refer to Deploy and log in in the HCP Boundary Get started documentation.

This document includes general guidance as well as specific recommendations for popular cloud infrastructure platforms. These recommendations have also been encoded into official Terraform reference architectures for AWS, Azure, and GCP.

Boundary architecture and system requirements

Before you begin, you may want to review the following information about Boundary's architecture and system requirements:

• System requirements
• Recommended architecture
• Fault tolerance
• High availability

Next steps

Refer to the following topics to deploy your self-managed environment:

1. Install Boundary
2. Configure controllers
3. Deploy workers
4. Initialize Boundary
5. Install Boundary clients

To configure Boundary resources using Terraform, refer to Terraform patterns.