SSH Config Generator

The SSH config file (~/.ssh/config) lets you define named aliases for SSH connections. Instead of typing 'ssh -i ~/.ssh/key.pem [email protected]', you can define a Host alias and just type 'ssh my-ec2'. It supports all SSH options including port, user, identity file, proxy jump, and more.

Copy the output and paste it into ~/.ssh/config (create the file if it doesn't exist). Then set permissions with 'chmod 600 ~/.ssh/config'. After that, you can connect using just 'ssh <alias>' instead of the full command with flags.

ProxyJump lets you connect to a server that isn't directly accessible from the internet — you route the connection through a bastion or jump host. For example, if your internal server is only reachable from your bastion, set ProxyJump to the bastion host alias. SSH handles the tunneling automatically.

ForwardAgent (yes/no) allows the SSH agent running on your local machine to be forwarded to the remote host. This means the remote host can use your local SSH keys to authenticate to other servers — useful for Git operations on remote servers without copying your private key there. Use with caution on untrusted hosts.

ServerAliveInterval tells SSH to send a keepalive packet every N seconds when the connection is idle. This prevents the connection from being dropped by firewalls or NAT devices that close idle TCP sessions. A common value is 60 seconds.

Yes — the SSH config file contains connection parameters, not credentials. Your private key files (IdentityFile) are separate and protected by file permissions. The config file itself should be owned by your user and have permissions 600 or 644. Never store private keys or passphrases in the config file.