The Quick setup wizard creates a default `tcp` target with the port `22` (the default SSH port using TCP).
The wizard creates the target with the address `127.0.0.1`.
The Quick setup wizard creates a default `tcp` target with the address `127.0.0.1` and the port `22` (the default SSH port using TCP).
When you execute `boundary connect` against this target, Boundary establishes a local, authenticated proxy to the address on the target's default port (`127.0.0.1:22`.)
@ -39,7 +38,6 @@ To connect to the initial EC2 Instances target:
```
The output displays the address and port that your SSH client must use.
In the next section uses the `ssh` connect helper to make it easier to connect to the target with a client.
The `boundary connect` command has a number of notable options, such as
`-listen-port` to choose the port on which the connect command will listen for
@ -48,25 +46,24 @@ applications that allow you to select the connection address, but not the port.
For some applications there are still some extra hurdles that can exist, which
is why connect helpers can be useful.
The dev-mode default target allows you to make as connections as you want
The dev-mode default target allows you to make as many connections as you want
within the authorized session. When you finish making connections, a
`Ctrl-C/Command-C` to the `boundary connect` process will shut down the session.
`Ctrl-C/Command-C` to the `boundary connect` process shuts down the session.
## Select targets
When using `boundary connect` you must identify the target used for connecting.
Convention in this documentation is to use the target ID because it refers to a
single explicit value.
When you use `boundary connect`, you must identify the target used for connecting.
The convention in this documentation is to use the target ID because it refers to a
single explicit value.
Other flags supported:
Other supported flags include:
- `target-name`: The name of the target
- `target-scope-id`: The ID of the scope in which the target lives
- `target-scope-name`: The name of the scope in which the target lives
Note however that these are not uniquely identifying, as you may reuse names
across scopes. You must use the target's name in conjunction with the scope name or scope ID
so that Boundary can identify the correct target.
Note however that these other flags are not uniquely identifying, as you may reuse names
across scopes. Therefore, if you don't use the target ID, you must use the target's name in conjunction with the scope name or scope ID so that Boundary can identify the correct target.
Dan Heath
1 year ago