<img src="https://ws.zoominfo.com/pixel/6169bf9791429100154fc0a2" width="1" height="1" style="display: none;">

Curious about how StrongDM works? 🤔 Learn more here!

Search
Close icon
Search bar icon

How to SSH Through Bastion With Key | Part 2 - Tutorial

See StrongDM in action →
Download Your PAM Guide (PDF)
SSH through bastion server with key

Contents

Secure Access Made Simple

Built for Security. Loved by Devs.

  • Free Trial — No Credit Card Needed
  • Full Access to All Features
  • Trusted by the Fortune 100, early startups, and everyone in between

In this post, we will show you how to create an SSH key, which will allow only the systems who have that key to access your bastion host.  We will also look at ways you can streamline the bastion host login process without compromising the security of the key.

The full tutorial is split into three parts:

Part 1: Creating your bastion hosts

  • This post shows you how to create Linux virtual machines in Amazon Web Services, setup virtual networking, and create initial firewall rules to access the hosts.  

Part 2: Managing SSH keys

  • We will show you how to create an SSH key for your bastion host and look at ways you can streamline the bastion host login process without compromising the security of the key.

Part 3: Configuring hosts for logging

  • How to configure our bastion hosts to gather verbose logging data and send it off site to a cloud service.

In the previous section, we walked through installing and configuring a bastion host and guest, and completed some initial network security configurations to lock network access down to only specific IP addresses.  In this post, we will further adjust our bastion hosts to simplify SSH access without weakening the security of the hosts or the key itself.

Configuring ssh-agent

With SSH configuration complete, next we will configure SSH forwarding, which is going to allow us to connect to the bastion host, and then create the subsequent connection to our bastion guest - all without storing our private SSH key on either server.

To configure this on a Mac (see this Amazon knowledge base article for Windows instructions), issue the following command:

ssh-add -K name-of-your-key.pem

Issuing the ssh-add -K commandIf you want to verify the key has been successfully added, issue this command:
ssh-add -L
Verify key has been added

Connecting to the bastion host with ssh-agent

Now you should be able to connect to your bastion host without specifying the .pem file, as it is securely stored on your machine:

ssh -A ubuntu@fully.qualified.domain.name

Connect to bastion host

You should now be fully logged into your bastion host:

Logged into your bastion host

Connecting to the bastion guest

Now that we have ssh-agent working and are fully logged into the bastion host, we should now be able to simply issue an SSH command to connect right to the bastion guest’s internal IP without providing the private key or any credentials. Do this by issuing:

ssh ubuntu@the.internal.ip.address

In our environment, this IP address is 172.31.41.192, so I’ll run:

Issue ssh ubuntu @ IP address

You should see some login banner information and then get dropped to what looks like the same host:

Connecting to bastion guest

However, if you issue the ifconfig command, you should see that we are indeed connected to the private IP corresponding with the bastion guest:

Using ifconfig command, you should see that we are connected to the private IP corresponding with the bastion guest

For now, type exit and Enter to drop your SSH connection back to the bastion host.

At this point we have configured SSH access control to only specific IP addresses, and configured our management system to use the private SSH key as a “forwarder” so we can easily log into both the bastion host and guest systems.  In the third and final part of this series, we will configure our bastion systems to collect verbose log data and then send it to a cloud provider.

To learn more on how StrongDM helps companies with auditing, make sure to check out our Auditing Use Case.

Brian Johnson

About the Author

, Security Engineer / Podcaster, is the president of 7 Minute Security, an information security consultancy in the Minneapolis area. Brian spends most of his days helping companies defend their networks.

Since 2004, Brian has also run the blog/podcast called 7 Minute Security, where he shares what he has learned about information security into short, 7-minute chunks.

💙 this post?
Then get all that StrongDM goodness, right in your inbox.

You May Also Like

Data Breach Response Plan: Your Guide to Leak Prevention
Data Breach Response Plan: Your Guide to Leak Prevention
A breach isn’t a matter of if, it’s when. In 2023 alone, around 97 million accounts were breached in the US, accounting for one in three cases worldwide. Whether it’s a rogue insider, a phishing attack, or a third-party screwup, your best shot at bouncing back fast is having a clear, tested data breach response plan. This guide walks you through what to include: governance roles, incident severity levels, NIST-based response steps, legal obligations (like GDPR, HIPAA, and CCPA), and communication playbooks. It’s not just about recovery, it’s about trust, compliance, and protecting your brand.
Creating Tables in PostgreSQL: Full Guide (with Example)
Creating Tables in PostgreSQL: Full Guide (with Example)
Learn how to create tables in PostgreSQL using psql or pgAdmin. Master data types, constraints, and schema design, and secure access with StrongDM's fine-grained permissions and audit trails.
MySQL SHOW USERS: How to List All Users in a Database
MySQL SHOW USERS: How to List All Users in a Database
Learn how to list MySQL users using SQL queries and GUI tools like Workbench and phpMyAdmin. Discover how to check privileges, manage accounts, and secure access with best practices, and see how StrongDM simplifies MySQL user management.
Hackers Don’t Hack In. They Log In.
Hackers Don’t Hack In. They Log In.
Most breaches don’t begin with hacking—they start with logging in. Discover how compromised credentials fuel modern cyberattacks and why Zero Trust Privileged Access is essential for securing today’s identity-driven environments.
PostgreSQL Default Password: Everything You Need to Know
PostgreSQL Default Password: Everything You Need to Know
PostgreSQL doesn’t come with a default password. And while that might seem like a security feature, leaving it unset can be just as risky. Understanding how Postgres handles authentication—from pg_hba.conf rules to encryption types like MD5 and SCRAM—is essential for keeping your database secure. Missteps in configuration or password management can open the door to unauthorized access.