/
Add an SSH server to Cronium so your events can execute scripts on remote infrastructure. This guide walks through configuring host access, verifying credentials, and saving the connection in the dashboard.
Ensure the orchestrator host can reach the target server on port 22 (or your custom SSH port).
Prepare an SSH private key or password for a user with execution permissions.
Fill out the server form with information Cronium uses to reach your host.
Pick an authentication method that matches your server policy.
Recommended for long-lived automation accounts
Paste the private key contents (PEM format) into the field.
Optionally supply a passphrase if the key is encrypted. Cronium stores the key encrypted using the platform encryption key.
Suitable for temporary or test environments
Enter the SSH password for the account. Consider switching to key based auth for production usage.
Click Test Connection. Cronium opens an SSH session and checks that the account can create a working directory on the host.
Once the test passes, click Save Server. The server is now available in the event editor under the “Remote execution” options.
Run a simple test event that targets your new server to confirm command output is streaming back to Cronium.
Review server permissions periodically and remove credentials for hosts you no longer need.
Need to manage multiple targets? Tag servers so you can filter them quickly when building workflows.