* docs: IA reorganization * docs: Updates * docs: Updates * docs: Fix links * docs: Updates * docs: Fix a typo * docs: Fix client agent topic * docs: Update Client Agent nav * docs: Fix conflict * docs: Fix a typo in Client Agent docs (#5853) * docs: Fix client agent topic * docs: Updates * docs: Updates * docs: Updates * docs: Updates * docs: Fixes get started and operations links * docs: Update nav * docs: Partials * docs: Unix partials * docs: Worker partials * docs: Updates * docs: Update workers and targets * docs: Updates * docs: Updates * docs: Fixes link * docs: Updates after sync review * docs: Updates from review feedback * docs: Move worker filter examples * docs: Fix links * docs: Updates for filters based on working session * docs: Fixes broken links * docs: Add links to other filter topics * docs: Update list intro * docs: Adds link * docs: Fixes redirects * docs: Fixes redirects * docs: Deleted mysql page from TOC * docs: Add versioned redirect * docs: Adds versioned redirects * docs: Adds versioned redirects * docs: Update redirects * docs: Update redirects * docs: Redirect fixes * docs: Update redirect format * docs: Fix a typo * docs: Fixes redirects * docs: Fixes redirect * docs: Adds links out to client agent troubleshooting * uses /etc/boundary.d/ as recommended installation directory (#6003) * docs: Updates legacy io links * docs: Fixes redirects * docs: Fix redirect * docs: Restoring deleted file --------- Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>
31 lines
1.2 KiB
Plaintext
31 lines
1.2 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Create multi-hop sessions for Boundary Enterprise
|
|
description: >-
|
|
Configure multi-hop sessions for Boundary Enterprise. Chain together two or more workers across multiple networks to reach a target without exposing private networks.
|
|
---
|
|
|
|
# Configure multi-hop sessions for Boundary Enterprise
|
|
|
|
<EnterpriseAlert product="boundary">This feature requires <a href="https://www.hashicorp.com/products/boundary">HCP Boundary or Boundary Enterprise</a></EnterpriseAlert>
|
|
|
|
For Boundary Enterprise, you can configure ingress, intermediary, and egress workers to take advantage of multi-hop worker capabilities.
|
|
|
|
Note that "ingress," "intermediary," and "egress" are general ways to describe how the respective worker interacts with resources.
|
|
A worker can serve more than one of those roles at a time.
|
|
Refer to [Multi-hop sessions](/boundary/docs/workers/multi-hop) for more information.
|
|
|
|
Complete the steps below to configure ingress, intermediate, and egress workers for Boundary Enterprise.
|
|
|
|
## Ingress worker configuration
|
|
|
|
@include '/workers/ingress-worker-config.mdx'
|
|
|
|
## Intermediate worker configuration
|
|
|
|
@include '/workers/intermediate-worker-config.mdx'
|
|
|
|
## Egress worker configuration
|
|
|
|
@include '/workers/egress-worker-config.mdx'
|