How to Configure Make SSH Credentials
To set up make ssh credentials, you store a private key in your Make account. You then add the matching public key to the remote server. Many teams start by generating a single key pair for all remote tasks. They assign that key to a shared Linux user on the target host. When that shared user holds broad shell rights, one bad task can break production. How make ssh credentials work at the host level Make is a visual automation tool that runs tasks across apps and servers. When a workflow step
Ephemeral Credentials + SSH Access Management: the complete guide
Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.
To set up make ssh credentials, you store a private key in your Make account. You then add the matching public key to the remote server. Many teams start by generating a single key pair for all remote tasks. They assign that key to a shared Linux user on the target host. When that shared user holds broad shell rights, one bad task can break production.
How make ssh credentials work at the host level
Make is a visual automation tool that runs tasks across apps and servers. When a workflow step runs a remote script, Make opens an SSH session. The tool presents the stored key or password to the remote OpenSSH daemon. The remote host checks its authorized key list or local password file. If the key matches, the server starts a shell as that local user.
Static keys often stay on servers for years without rotation. To improve security, some teams use OpenSSH user certificates instead of plain public keys. The OpenSSH key utility can sign a public key with a certificate authority key. A signed certificate holds the public key, an identity string, and valid user principals. It also includes a validity window and optional rules signed by the authority. OpenSSH certificates use a much simpler format than standard TLS certificates. When you use certificates, the server trusts the authority key instead of static files.
Why static keys leave an operational gap
Native SSH setup only decides which user account can log into the server. Once the session starts, the automation tool gets the full rights of that account. Make workflows often need to run one specific script or move one file. Yet the Linux user account can often read other files or run extra commands. If someone edits the workflow in Make, the server will run the new command.
Storing long-lived private keys inside third-party workflow tools also creates rotation work. When an engineer leaves the team, you must replace keys across many hosts. You also have to update every Make scenario that uses that old credential. Standard host logs show that the shared automation user logged into the box. Those logs rarely show which workflow run sent a specific shell command. Nor do they mask sensitive values like emails, phone numbers, or card numbers in output.
Ephemeral Credentials + SSH Access Management: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
Managing command scope for automated workflows
You can limit risk by creating a dedicated Linux user for each workflow. Give that user account rights only to the exact folders it must touch. You can also restrict what commands a specific public key is allowed to run. OpenSSH lets admins bind a forced command to a key or user certificate. When Make logs in with that key, the server runs only that fixed script. It ignores any other shell command that the automation step tries to send.
Teams also pair command restrictions with short validity windows on their user certificates. By default, a signed OpenSSH certificate remains valid forever unless you set a window. Setting a short window forces keys to expire on a regular schedule. Even with these host rules, managing files across dozens of servers takes real effort. Teams still need a central way to inspect commands and protect secret data.
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 use passwords or keys for Make SSH steps?
Always use SSH keys or signed certificates instead of plain text passwords. Keys are much harder to guess and let you set command rules on the host.
How do I limit what a Make workflow can do over SSH?
Create a dedicated Linux user with minimal file rights for the Make task. You can also set a forced command on the key inside the host config.
How often should teams rotate SSH keys used in automation?
Rotate static automation keys at least every ninety days or after staff changes. If you use OpenSSH certificates, set a short validity window when signing them.
Related guides
In this post