Boundary
targets create
Command: targets create
The targets create command lets you create a new target.
Example
This example creates a TCP target with the name prodops and the description For ProdOps usage:
$ boundary targets create tcp -name prodops -description "For ProdOps usage"
Usage
$ boundary targets create [type] [sub command] [options] [args]
Please see the typed subcommand help for detailed usage information.
Subcommands:
rdp Create an rdp-type target (HCP & Boundary Enterprise only)
ssh Create a ssh-type target (HCP & Boundary Enterprise only)
tcp Create a tcp-type target
Usages by type
You can create RDP, SSH, or TCP targets.
The targets create rdp command lets you create RDP targets.
Example
This example creates an RDP target with the name admindc and the description RDP target for Admin Domain Controller:
$ boundary targets create rdp -name admindc -description "RDP target for Admin Domain Controller"
Usage
$ boundary targets create rdp [options] [args]
RDP target options
-address=<string>- An optional valid network address for the target to connect to. You cannot use an address alongside host sources.If you set a target address for RDP targets that use Kerberos authentication, use the target's hostname and append the domain to it, for example
target-hostname.mydomain.com. For RDP targets that use NTLM authentication, set the target address to the target's IP address.-default-client-port=<string>- The default client port on the target.-default-port=<string>- The default port on the target. Due to a port conflict on modern Windows operating systems (Windows 11+, Windows Server 2025), transparent sessions cannot use the default RDP port3389. You must configure a custom port to use transparent sessions with RDP targets.Refer to Using transparent sessions with RDP on Windows for more information about configuring a custom port for transparent sessions.
-egress-worker-filter=<string>- A Boolean expression that filters which egress workers can process sessions for the target.-ingress-worker-filter=<string>- A Boolean expression that filters which ingress workers can process sessions for the target.-session-connection-limit=<string>- The maximum number of connections allowed for a session. A value of-1means the connections are unlimited.-session-max-seconds=<string>- The maximum lifetime of the session, including all connections. You can specify an integer number of seconds or a duration string. If you do not specfiy a maximum duration, Boundary uses the default value of 8 hours (28800 seconds).-with-alias-authorize-session-host-id=<string>- The host ID that an alias uses to authorize sessions for the target.-with-alias-scope-id=<string>- The scope ID that you want to create the target and alias in. The default isglobal. At this time, aliases are only supported for the global scope.-with-alias-value=<string>- The value of the alias that you want to use to represent the target. Use this parameter to create the alias and target, and associate them with each other, at the same time.
CLI options
In addition to the command specific options, there are options common to all CLI commands and subcommands: