Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Backport of docs: Fix broken link into stable-website" #4038

Closed
wants to merge 1 commit into from
Closed

Revert "Backport of docs: Fix broken link into stable-website" #4038

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions website/content/docs/concepts/host-discovery/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ infrastructure targets can be automated with
This allows for dynamic configuration of a host and target without the need
for prior knowledge of the target’s connection info.

**[Runtime host discovery via dynamic host catalogs](/boundary/tutorials/host-management/aws-host-catalogs)**:
**[Runtime host discovery via dynamic host catalogs](/boundary/tutorials/access-management/aws-host-catalogs)**:
Boundary dynamic host catalogs automate the ingestion of resources from
infrastructure providers into Boundary. Boundary hosts are automatically
created, updated and added to host sets in order to reflect the connection
Expand All @@ -58,5 +58,5 @@ Boundary currently supports dynamic host catalog for AWS and
Azure and we will continue to grow this ecosystem to support additional providers.

You can get started with dynamic host catalogs for AWS
[here](/boundary/tutorials/host-management/aws-host-catalogs)
and for Azure [here](/boundary/tutorials/host-management/azure-host-catalogs).
[here](/boundary/tutorials/access-management/aws-host-catalogs)
and for Azure [here](/boundary/tutorials/access-management/azure-host-catalogs).
2 changes: 0 additions & 2 deletions website/content/docs/operations/session-recordings/validate-session-recordings.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,6 @@ description: |-

<EnterpriseAlert product="boundary">This feature requires <a href="https://www.hashicorp.com/products/boundary">HCP Boundary or Boundary Enterprise</a></EnterpriseAlert>

<EnterpriseAlert product="boundary">This feature requires <a href="https://www.hashicorp.com/products/boundary">HCP Boundary or Boundary Enterprise</a></EnterpriseAlert>

BSR directories are validated based on the contents in the directory.
Boundary cryptographically verifies each individual Boundary Session Recording (BSR) file.
The keys used for verifying all Boundary Session Recording files are written to storage and wrapped by the KMS you configured.
Expand Down