<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jumphost on technocracy</title><link>https://www.ericsimmerman.com/tags/jumphost/</link><description>Recent content in Jumphost on technocracy</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 18 May 2017 00:00:00 +0000</lastBuildDate><atom:link href="https://www.ericsimmerman.com/tags/jumphost/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting up a Bastion host on AWS</title><link>https://www.ericsimmerman.com/blog/2017/05/18/setting-up-a-bastion-host-on-aws/</link><pubDate>Thu, 18 May 2017 00:00:00 +0000</pubDate><guid>https://www.ericsimmerman.com/blog/2017/05/18/setting-up-a-bastion-host-on-aws/</guid><description>&lt;p&gt;When setting up my latest development environment at AWS, I wanted to deploy all EC2 services on a private VPC and simply route all traffic to them through a Bastion host (aka jump host). AWS maintains a an &lt;a href="http://docs.aws.amazon.com/quickstart/latest/linux-bastion/welcome.html" target="_blank" rel="noopener noreffer "&gt;excellent CloudFormation quickstart guide &amp;amp; template here&lt;/a&gt; and it&amp;rsquo;s what I used to get started. After completing that guide I put a new entry for the Bastion host in my ssh config like so:&lt;/p&gt;</description></item></channel></rss>