SSH Server - Duvo

The SSH Server connection lets your agents connect to remote Linux or Unix servers and execute shell commands over SSH. Provide your server credentials, and Duvo handles the connection so agents can retrieve data, run scripts, and check system health without manual logins.

Setup

Confirm prerequisites

An SSH-accessible server (Linux, Unix, or any host running an SSH daemon).

A user account on the target server with the permissions your agent needs.

Either a password or a PEM-encoded private key for authentication.

If connecting through a bastion host, credentials for the jump server (these can differ from the target server’s credentials).

Grant the required permissions

The SSH user account must have shell access on the target server.
Grant only the minimum permissions the agent needs. Avoid using root or highly privileged accounts unless the workflow specifically requires it.
If using key-based authentication, the public key must be added to the user’s authorized_keys file on the server.

The SSH user determines exactly what the agent can do on the server. Scope it to the minimum permissions the workflow needs, and avoid root or highly privileged accounts unless they are specifically required.

Add the connection in Duvo

On the Connections page, open SSH Server and fill in these fields:

Host

string

required

Hostname or IP address of the target server.

Username

string

required

SSH user account to authenticate with.

Port

number

SSH port on the target server (defaults to 22).

Password

string

Password for the user account (provide either password or private key).

Private Key

PEM

PEM-encoded private key (provide either password or private key).

Private Key Passphrase

string

Passphrase to decrypt an encrypted private key.

Jump Host

string

Hostname or IP of a bastion/jump server for two-hop connections.

Jump Port

number

SSH port on the jump host (defaults to 22).

Jump Username

string

User account on the jump host (required when a jump host is set).

Jump Password

string

Password for the jump host (provide either password or private key).

Jump Private Key

PEM

PEM-encoded private key for the jump host.

Jump Private Key Passphrase

string

Passphrase to decrypt the jump host private key.

Capabilities

Execute shell commands — Run any shell command on the remote server and capture stdout, stderr, and exit codes.
Read server data — Retrieve logs, configuration files, and system status information directly from the source.
Trigger remote processes — Start scripts, batch jobs, or server-side operations as part of an end-to-end workflow.
Check system state — Query running processes, disk usage, service availability, or any other system metric.
Connect through bastion hosts — Reach servers behind firewalls by routing through a jump host with two-hop SSH tunneling.

Key Benefits

Replace manual SSH sessions — Governed, repeatable automation instead of ad-hoc terminal logins.
Access data at the source — Pull logs, configs, and system metrics directly from servers without intermediate exports.
Flexible server coverage — Works with any server that exposes an SSH endpoint, regardless of operating system or cloud provider.
Secure credential handling — Supports both password and key-based authentication, with optional passphrase protection for private keys.
Bastion host support — Reach servers in private networks through jump hosts without exposing them directly.