CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Update multi-hop docs (#2806)

Browse Source 
* docs: Update multi-hop docs

* Apply batch of suggestions from code review

Co-authored-by: Kendall Strautman <36613477+kendallstrautman@users.noreply.github.com>
Co-authored-by: Irena Rindos <irenarindos@users.noreply.github.com>

* docs: Fix spelling

Co-authored-by: Kendall Strautman <36613477+kendallstrautman@users.noreply.github.com>
Co-authored-by: Irena Rindos <irenarindos@users.noreply.github.com>
This commit is contained in:
Dan HeathKendall StrautmanIrena Rindos
 authored and GitHub committed 2023-01-24 09:15:52 -05:00
1 parent 4b7f40c356
commit d41ef25a27
2 files changed
+13 -1
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

website/content/docs/concepts/domain-model/targets.mdx
+12
View File
@@ -54,10 +54,16 @@ TCP targets have the following additional attributes:
- `egress_worker_filter` - (optional)
A boolean expression to [filter][] which egress workers can handle sessions
for this target.
Egress worker filters determine which workers are used to access targets.
You can configure an egress filter to enable [multi-hop](/boundary/docs/configuration/worker/pki-worker#multi-hop-workershcp-only) connections.
If you do not configure an egress filter, then Boundary uses a single worker to connect to the controller.
- `ingress_worker_filter` - (optional) <sup>HCP Only</sup>
A boolean expression to [filter][] which ingress workers can handle sessions
for this target.
Ingress worker filters determine which workers you connect with to initiate a session.
If you do not configure an ingress filter, Boundary selects a front line worker for the session.
A front line worker is any worker directly connected to the control plane; for HCP Boundary this will be an HCP worker.
- `session_connection_limit` - (required)
The cumulative number of TCP connections allowed during a session.
@@ -91,10 +97,16 @@ SSH targets have the following additional attributes:
- `egress_worker_filter` - (optional)
A boolean expression to [filter][] which egress workers can handle sessions
for this target.
Egress worker filters determine which workers are used to access targets.
You can configure an egress filter to enable [multi-hop](/boundary/docs/configuration/worker/pki-worker#multi-hop-workershcp-only) connections.
If you do not configure an egress filter, then Boundary uses a single worker to connect to the controller.
- `ingress_worker_filter` - (optional) <sup>HCP Only</sup>
A boolean expression to [filter][] which ingress workers can handle sessions
for this target.
Ingress worker filters determine which workers you connect with to initiate a session.
If you do not configure an ingress filter, Boundary selects a front line worker for the session.
A front line worker is any worker directly connected to the control plane; for HCP Boundary this will be an HCP worker.
- `session_connection_limit` - (required)
The cumulative number of TCP connections allowed during a session.
website/content/docs/configuration/worker/pki-worker.mdx
+1 -1
View File
@@ -142,7 +142,7 @@ kms "aead" {
```
[kms workers]: /boundary/docs/configuration/worker/kms-worker
[target]: /boundary/docs/concepts/domain-model/targets
[target worker filters]: /boundary/docs/concepts/filtering/worker-tags
[target worker filters]: /boundary/docs/concepts/filtering/worker-tags#target-worker-filtering
## Tutorial