How to Configure Make SSH Connect

Published
Length
3 min read

Luis Felipe Dias

All posts

To set up a make ssh connect workflow, add your SSH key to the remote server. Then point your Make automation task to the host address and Linux user account. Teams often share one static private key across many automated Make workflows. This shared key gives every automated job full shell access to the host. If one workflow fails or leaks a key, every remote server is at risk. Broad Linux user permissions also let simple tasks run dangerous commands by mistake. How a native make ssh connect s

SSH Access Management + End-to-End Encryption: the complete guide

Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.

Free white paper. No spam. Unsubscribe anytime.

To set up a make ssh connect workflow, add your SSH key to the remote server. Then point your Make automation task to the host address and Linux user account. Teams often share one static private key across many automated Make workflows. This shared key gives every automated job full shell access to the host. If one workflow fails or leaks a key, every remote server is at risk. Broad Linux user permissions also let simple tasks run dangerous commands by mistake.

How a native make ssh connect setup works

In a standard setup, Make runs an SSH client module during a scenario. The module opens an encrypted tunnel to a remote Linux host or bastion. To log in, the Make platform needs a username and a credential. Most teams use an SSH key pair instead of a password. You place the public key on the target server in the user folder. You store the private key inside the Make credential store.

When the Make scenario runs, it presents the private key to the server. The server checks the key and starts a shell session for that Linux user. For larger setups, teams use OpenSSH certificates instead of raw public keys. Certificate support for users and hosts arrived in OpenSSH 5.4. In this model, a key tool signs a public key with a central authority key. The resulting certificate holds the public key, identity data, principals, and options. OpenSSH certificates use a much simpler format than TLS certificates. The target server trusts the central authority key instead of tracking individual public keys.

Where native SSH key setups fall short

Static keys and OpenSSH certificates solve the login step well. They verify who can open a tunnel to the target host. Still, native SSH credentials only check identity at the start of the session. Once the Make task logs in, it gets the full rights of that Linux account. A key signed without a time limit stays valid forever by default. Even if you set a time window, the certificate cannot inspect active commands.

Native OpenSSH does let you restrict a certificate or key to one forced command. Yet this rule is rigid and hard to manage across dozens of Make scenarios. If a Make workflow needs to run three different scripts, a single forced command fails. Teams often fall back to giving the automation user broad shell permissions. Standard system logs only show that the automation user logged in from an IP address. They do not link individual shell commands back to the specific Make task or owner. Also, if a script queries sensitive data, native SSH cannot rewrite emails or card numbers. The raw output flows straight back into the automation logs.

SSH Access Management + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

How to tighten automated remote command workflows

To reduce risk, separate each Make workflow into its own least-privilege role. Never reuse root or admin Linux accounts for routine automation tasks. Create dedicated Linux users that only own the exact files the script needs. When you sign OpenSSH user certificates, always set a short validity window. List only the exact principal names required for that specific job.

You should also place a jump host in front of private servers. This step keeps your internal hosts off the public internet. Still, network controls and key rules only guard the front door. Real security requires checking every command and masking sensitive fields like phone numbers in flight.

Check SSH commands and file transfers on the host

OpenSSH keys and certificates decide who can log into a Linux host. They do not check what a one-shot command or file transfer does once the session starts. With hoop.dev, you run an open-source SSH server with guardrails on the host. It checks callers with OpenSSH certificates and works with ssh, sftp, scp, and rsync clients.

When a caller runs a one-shot command or moves a file, hoop.dev guardrails check the command or path before it runs. Then hoop.dev data masking masks matched sensitive patterns in downloads and output. Interactive shells carry no guardrails because keystrokes have no statement boundary. Teams can turn interactive shells off and allow only commands and file tasks. The audit trail logs who connected and what was allowed or refused, without storing keystrokes or file bytes. See the source on GitHub.

Frequently asked questions

Should I use a password or an SSH key for Make tasks?

Always use an SSH key or an OpenSSH certificate instead of a password. Keys resist guessing attacks and let you rotate credentials without changing Linux user passwords.

How do OpenSSH certificates help with automated workflows?

OpenSSH certificates let you sign a public key with a central authority key. You can embed principal names, identity info, and expiration times without editing server key files.

Why is a dedicated Linux user important for Make automation?

SSH grants the session all permissions held by the target Linux user. A dedicated user with limited file rights stops a broken Make task from deleting system files.

Save the open-source gateway.

hoop is MIT-licensed infrastructure for controlling how AI agents reach production data. Star hoophq/hoop so you can inspect it, deploy it, or share it when your team starts governing agent access.