How to Configure Make SSH Permissions
To set up make ssh permissions, create a dedicated Linux user with a scoped SSH key. Then restrict that key on the remote host so your Make workflow only runs approved scripts. Engineering teams often connect cloud workflows to private Linux servers to run jobs or move files. To move fast, admins often paste a shared admin key into the cloud workflow tool. When a workflow uses a broad key, any leaked key gives an attacker full server control. How to set up make ssh permissions on your host Se
SSH Access Management + AI Agent Permissions: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
To set up make ssh permissions, create a dedicated Linux user with a scoped SSH key. Then restrict that key on the remote host so your Make workflow only runs approved scripts. Engineering teams often connect cloud workflows to private Linux servers to run jobs or move files. To move fast, admins often paste a shared admin key into the cloud workflow tool. When a workflow uses a broad key, any leaked key gives an attacker full server control.
How to set up make ssh permissions on your host
Setting up make ssh permissions starts on the target Linux server, not inside the cloud tool. First, you create a dedicated Linux service account on the host for your Make tasks. Next, you generate a fresh SSH key pair dedicated only to this single workflow. You place the public key on the target server and store the private key in Make.
Instead of raw keys, teams can also use OpenSSH certificates for user and host login. A Certification Authority key signs a public key to create an OpenSSH certificate. Each certificate holds a public key, identity info, principal names, and a set of options. OpenSSH certificates use a much simpler format than X.509 certificates, and arrived in OpenSSH 5.4.
On the Linux host, you must limit what the dedicated workflow account can run. Give the service user read or write rights only on the folders it needs. If the workflow needs root rights for one script, scope the local sudo rule tightly. Never grant full root shell rights to an automated cloud task.
What native SSH setup solves and what it misses
A scoped Linux user and a dedicated SSH key stop basic lateral movement across hosts. If a workflow fails or runs a bad script, it cannot touch other system folders. Using OpenSSH certificates also helps teams avoid copying static public keys to every single server.
Still, native SSH setup only checks who logs in at the start of a session. Once the workflow logs in, the host does not inspect individual commands or data in flight. If a remote script dumps a table, sensitive fields return in plain text to the caller. Native SSH permissions cannot mask emails, phone numbers, card numbers, or national IDs in output.
SSH Access Management + AI Agent Permissions: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Static private keys stored in third-party workflow tools also create a long-term rotation burden. If an engineer leaves or a cloud account leaks, you must revoke and replace keys fast. Standard host logs show when a user logged in, but miss full command output details.
Best practices for securing automated remote workflows
Break large automation scripts into small, single-purpose jobs on the remote Linux server. Instead of letting the cloud tool send arbitrary shell strings, trigger a fixed local script. Keep the script owned by root so the workflow user can run it but not edit it.
Place a bastion or jump host between external cloud runners and your internal server network. This setup keeps private hosts off the public internet while allowing inbound workflow runs. Review your authorized key files and CA signing logs every month to remove unused workflow access.
Add command and file guardrails to SSH access
Host firewalls and certificate principals control who opens an SSH session. Yet an allowed user or agent can still run a bad one-shot command or pull sensitive files over sftp. In practice, hoop.dev provides an open-source SSH server with guardrails on the host that uses OpenSSH certificates.
Using hoop.dev SSH controls, guardrails check one-shot commands, env variable names, and sftp or scp paths before they run. Port forwards default to deny unless the target is listed. Because interactive shells have no statement boundary and carry no guardrails, teams can turn them off so every command is checked and logged. Check out the MIT-licensed project on GitHub.
Frequently asked questions
Should I share one SSH key across multiple Make workflows?
No, you should create a unique SSH key pair for each workflow or service role. Separate keys let you revoke one workflow without breaking every other automated job.
How do OpenSSH certificates improve on static SSH keys?
A Certification Authority key signs a user public key with an identity, principals, and options. Hosts trust the CA key instead of managing long lists of static public keys.
Why is restricting the Linux user not enough for compliance?
Linux file permissions only control which files a user can read, write, or execute. They do not log full session output or rewrite sensitive fields like emails or card numbers.
Related guides
In this post