2022-03-31 14:54:53 -07:00
|
|
|
|
---
|
|
|
|
|
|
layout: docs
|
2023-06-29 11:20:39 -04:00
|
|
|
|
page_title: Host discovery
|
2022-03-31 14:54:53 -07:00
|
|
|
|
description: |-
|
2023-06-29 11:20:39 -04:00
|
|
|
|
An overview of host discovery in Boundary
|
2022-03-31 14:54:53 -07:00
|
|
|
|
---
|
|
|
|
|
|
|
2023-06-29 11:20:39 -04:00
|
|
|
|
# Host discovery
|
2022-03-31 14:54:53 -07:00
|
|
|
|
|
2023-06-29 11:20:39 -04:00
|
|
|
|
Traditionally, connecting to remote hosts and services requires knowledge of
|
|
|
|
|
|
the endpoint’s connection info (e.g. the IP address and port of the service).
|
2022-03-31 14:54:53 -07:00
|
|
|
|
This creates complexity when managing the onboarding of new resources at scale
|
2023-07-18 12:18:51 -07:00
|
|
|
|
or dealing with dynamic, ephemeral services whose connection info frequently changes.
|
|
|
|
|
|
Furthermore, the increased operational overhead of having to manually manage and update
|
|
|
|
|
|
new or old resources is an inefficient use of time.
|
|
|
|
|
|
Resources should be tagged appropriately so that, depending on their identity, users
|
|
|
|
|
|
automatically have the resources that they are allowed to connect to.
|
2022-03-31 14:54:53 -07:00
|
|
|
|
|
2023-06-29 11:20:39 -04:00
|
|
|
|
**Host discovery** focuses on automating the process of onboarding new or
|
|
|
|
|
|
changed infrastructure resources – and their connection info – to Boundary
|
2022-03-31 14:54:53 -07:00
|
|
|
|
as hosts.
|
|
|
|
|
|
|
2023-07-07 14:42:11 -04:00
|
|
|
|
## Automated host discovery in Boundary
|
2022-03-31 14:54:53 -07:00
|
|
|
|
|
2023-06-29 11:20:39 -04:00
|
|
|
|
Boundary supports target/host discovery in three primary workflows:
|
2022-03-31 14:54:53 -07:00
|
|
|
|
|
2023-06-29 11:20:39 -04:00
|
|
|
|
**[Manual configuration](/boundary/tutorials/oss-administration/oss-manage-targets)**:
|
|
|
|
|
|
Boundary administrators can manually configure static
|
|
|
|
|
|
hosts and targets via the administrator UI and CLI. Manual configuration of
|
|
|
|
|
|
targets with static hosts requires knowledge of the IP address or endpoint used
|
2022-03-31 14:54:53 -07:00
|
|
|
|
to connect to a host.
|
|
|
|
|
|
|
2023-06-29 11:20:39 -04:00
|
|
|
|
**[Host discovery via configuration as code with Terraform](/boundary/tutorials/oss-getting-started/oss-getting-started-config)**:
|
|
|
|
|
|
Boundary is fully programmatically instrumented and the discovery and configuration of new
|
|
|
|
|
|
infrastructure targets can be automated with
|
|
|
|
|
|
[Boundary’s Terraform provider](https://registry.terraform.io/providers/hashicorp/boundary/latest/docs).
|
|
|
|
|
|
This allows for dynamic configuration of a host and target without the need
|
|
|
|
|
|
for prior knowledge of the target’s connection info.
|
|
|
|
|
|
|
2023-11-13 15:04:12 -05:00
|
|
|
|
**[Runtime host discovery via dynamic host catalogs](/boundary/tutorials/host-management/aws-host-catalogs)**:
|
2023-06-29 11:20:39 -04:00
|
|
|
|
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
|
|
|
|
|
|
information maintained in these providers. This removes the need to know
|
|
|
|
|
|
host connection info or reapply infrastructure as code templates to
|
2023-02-22 10:46:52 -08:00
|
|
|
|
configure new or changed resources.
|
2022-03-31 14:54:53 -07:00
|
|
|
|
|
2023-06-29 11:20:39 -04:00
|
|
|
|
## Dynamic host catalogs
|
|
|
|
|
|
Dynamic host catalogs are an agentless workflow for Boundary to
|
|
|
|
|
|
securely query infrastructure providers at runtime to discover and configure
|
2023-07-18 12:18:51 -07:00
|
|
|
|
new services. Boundary administrators can define rules for which
|
2023-06-29 11:20:39 -04:00
|
|
|
|
external resources should be ingested into the catalog by
|
2023-07-18 12:18:51 -07:00
|
|
|
|
[creating a host sets](/boundary/docs/concepts/domain-model/host-sets)
|
|
|
|
|
|
with an attributes filter. These filters specify which discovered hosts
|
|
|
|
|
|
should be members of the host set.
|
2022-03-31 14:54:53 -07:00
|
|
|
|
|
2023-07-18 12:18:51 -07:00
|
|
|
|
Boundary currently supports dynamic host catalog for AWS and
|
2023-06-29 11:20:39 -04:00
|
|
|
|
Azure and we will continue to grow this ecosystem to support additional providers.
|
2022-03-31 14:54:53 -07:00
|
|
|
|
|
2023-07-18 12:18:51 -07:00
|
|
|
|
You can get started with dynamic host catalogs for AWS
|
2023-11-13 15:04:12 -05:00
|
|
|
|
[here](/boundary/tutorials/host-management/aws-host-catalogs)
|
|
|
|
|
|
and for Azure [here](/boundary/tutorials/host-management/azure-host-catalogs).
|