unix listener

출처: HashiCorp Boundary docs

The unix listener configures Boundary to listen on a Unix domain socket.

It is only available for listeners for api and cluster purpose. Unix sockets cannot currently be used for "proxy" purpose on a worker. Refer to TCP listener configuration for the alternative listener type.

listener "unix" {
  purpose = "api"
  address = "/var/run/boundary-api.sock"
}

The listener stanza may be specified more than once to make Boundary listen on multiple interfaces; however, only one listener marked for cluster purpose is allowed.

unix listener parameters

Refer to the following sections for the supported unix listener parameters.

General parameters

TLS

The tls parameters are valid for api and ops listeners. cluster and proxy connections use their own ephemeral TLS stacks. For more information, refer to TLS in Boundary.

unix listener examples

Refer to the following sections for examples of unix listeners.

Configure TLS

This example shows enabling a TLS listener.

listener "unix" {
  purpose = "api"
  address = "/var/run/boundary-api.sock"
  tls_cert_file = "/etc/certs/Boundary.crt"
  tls_key_file  = "/etc/certs/Boundary.key"
}

Listen on multiple interfaces

This example shows Boundary listening on a private interface, as well as localhost.

listener "tcp" {
  purpose = "api"
  address = "/var/run/boundary-api.sock"
}

listener "tcp" {
  purpose = "cluster"
  address = "/var/run/boundary-cluster.sock"
}

Edit this page on GitHub