In secure infrastructure environments, production servers are often placed in private networks and are not directly accessible from the internet. Instead, administrators connect through a designated Jump Box (Bastion Host)<\/strong> that has controlled public access and connectivity to internal servers. This approach improves security by reducing the attack surface while maintaining administrative access. This guide explains how to configure SSH on your local machine to automatically route connections through a jump box, allowing seamless access to private servers without manually logging into the jump box first.<\/p>\n\n\n\n Before proceeding, ensure the following requirements are met:<\/p>\n\n\n\n Scenario\/Use case:<\/strong><\/p>\n Consider we have a jumpbox which has access to all the production machines and we don’t want to expose SSH access to the public. In such a scenario, we can allow only the jumpbox to public access, and through the jumpbox, we can access the remaining machines. But it’s a pain to log in to the jumpbox and do ssh to the production hosts.<\/p>\n \u00a0<\/p>\n Solution:<\/strong><\/p>\n Here comes the easy solution that we can apply from your local machine so we can directly SSH from your local machine.<\/p>\n Assumption:<\/em><\/p>\n On your local machine, open the terminal and open\u00a0.ssh\/config.\u00a0<\/em> This file may\/may not exist. We can create the file and append the following content.<\/p>\n \u00a0<\/p>\n In the above case, when the user(username) tries to log in from their local machine, it will route the traffic through jumpbox.<\/p>\nPrerequisites<\/h2>\n\n\n\n
\n
~\/.ssh\/config<\/code>).<\/li>\n\n\n\nIMPLEMENTATION<\/h2>\n\n\n
\n
<\/code>Host\u00a0*
\nProxyCommand\u00a0 ssh username@jumpbox.domain.tld nc %h %p 2> \/dev\/null<\/code><\/p>\n