Files
threshold/website/content/docs/deploy/self-managed/install.mdx
T

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

199 lines
5.4 KiB
Plaintext
Raw Normal View History

2023-06-13 08:53:27 +02:00
---
layout: docs
2025-09-03 15:45:38 -04:00
page_title: Install Boundary
2024-11-14 13:48:59 -05:00
description: >-
2024-11-20 15:54:52 -07:00
Deploy a self-managed version of Boundary Enterprise or Community Edition on Ubuntu/Debian, CentOS/RHEL, or Amazon Linux by installing the binary file.
2023-06-13 08:53:27 +02:00
---
2025-11-04 10:22:10 -05:00
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
> [!IMPORTANT]
> **Documentation Update:** Product documentation previously located in `/website` has moved to the [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs) repository, where all product documentation is now centralized. Please make contributions directly to `web-unified-docs`, since changes to `/website` in this repository will not appear on developer.hashicorp.com.
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
2025-09-03 15:45:38 -04:00
# Install Boundary
Pre-built Boundary packages are available from the [HashiCorp Linux
Repository](https://www.hashicorp.com/blog/announcing-the-hashicorp-linux-repository).
In addition to installing the Boundary binary, the official package also
provides a systemd service unit, and a local `boundary` user account under which
the service runs.
2024-11-20 15:54:52 -07:00
<Note>
You must complete the following steps for each Boundary controller and worker
node that you want to deploy. The binary operates as either a worker or
2024-11-20 15:54:52 -07:00
controller, depending on the configuration that you generate for the
Boundary binary.
2023-06-13 08:53:27 +02:00
2024-11-20 15:54:52 -07:00
</Note>
The steps vary by Linux distribution.
2023-06-13 08:53:27 +02:00
Select your distribution of Boundary, and complete the steps to install the
binary:
2023-06-13 08:53:27 +02:00
<Tabs>
<Tab heading="Enterprise">
2024-11-20 15:54:52 -07:00
<Tabs>
<Tab heading="Ubuntu/Debian">
2023-06-13 08:53:27 +02:00
1. Use the following command to add the HashiCorp GPC key as a trusted
package-signing key:
```shell-session
$ curl -fsSL https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
```
1. Add the official HashiCorp Linux repository:
```shell-session
$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
```
1. Update the package index:
```shell-session
$ sudo apt update
```
1. Install Boundary Enterprise:
```shell-session
$ sudo apt install boundary-enterprise
```
</Tab>
<Tab heading="CentOS/RHEL">
1. Use the following command to install `yum-config-manager` to manage your
repositories:
```shell-session
$ sudo yum install -y yum-utils
```
2. Add the official HashiCorp Linux repository:
2023-06-13 08:53:27 +02:00
```shell-session
$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
```
3. Install Boundary Enterprise:
```shell-session
$ sudo yum -y install boundary-enterprise
```
</Tab>
<Tab heading="Amazon Linux">
1. Use the following command to install `yum-config-manager` to manage your
repositories:
```shell-session
$ sudo yum install -y yum-utils shadow-utils
```
2. Add the official HashiCorp Linux repository:
```shell-session
$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
```
3. Install Boundary Enterprise:
```shell-session
$ sudo yum -y install boundary-enterprise
```
</Tab>
</Tabs>
</Tab>
<Tab heading="Community Edition">
2023-06-13 08:53:27 +02:00
<Tabs>
<Tab heading="Ubuntu/Debian">
1. Use the following command to add the HashiCorp GPC key as a trusted
package-signing key:
2023-06-13 08:53:27 +02:00
```shell-session
$ curl -fsSL https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
2023-06-13 08:53:27 +02:00
```
1. Add the official HashiCorp Linux repository:
```shell-session
$ echo "deb [signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
2023-06-13 08:53:27 +02:00
```
1. Update the package index:
```shell-session
$ sudo apt update
```
1. Install Boundary Community Edition:
2023-06-13 08:53:27 +02:00
```shell-session
$ sudo apt install boundary
```
</Tab>
<Tab heading="CentOS/RHEL">
1. Use the following command to install `yum-config-manager` to manage your
repositories:
2023-06-13 08:53:27 +02:00
```shell-session
$ sudo yum install -y yum-utils
```
2. Add the official HashiCorp Linux repository:
```shell-session
$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
```
3. Install Boundary Community Edition:
2023-06-13 08:53:27 +02:00
```shell-session
$ sudo yum -y install boundary
2023-06-13 08:53:27 +02:00
```
</Tab>
<Tab heading="Amazon Linux">
1. Use the following command to install `yum-config-manager` to manage your
repositories:
```shell-session
$ sudo yum install -y yum-utils shadow-utils
```
2. Add the official HashiCorp Linux repository:
```shell-session
$ sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/AmazonLinux/hashicorp.repo
```
3. Install Boundary Community Edition:
```shell-session
$ sudo yum -y install boundary
```
</Tab>
</Tabs>
</Tab>
2024-11-20 15:54:52 -07:00
</Tabs>
2025-09-03 15:45:38 -04:00
You should install the binary on the controller and worker instances you configure to run in your Boundary environments.
## Next steps
2024-11-20 15:54:52 -07:00
2025-09-03 15:45:38 -04:00
After you install the binary, you should:
2024-11-20 15:54:52 -07:00
2025-09-03 15:45:38 -04:00
1. [Configure controllers](/boundary/docs/deploy/self-managed/configure-controllers)
1. [Deploy workers](/boundary/docs/deploy/self-managed/deploy-workers)
1. [Initialize Boundary](/boundary/docs/deploy/self-managed/initialize)
1. [Install the Boundary Clients](/boundary/docs/deploy/self-managed/install-clients)