<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AWS Lambda on technocracy</title><link>https://www.ericsimmerman.com/tags/aws-lambda/</link><description>Recent content in AWS Lambda on technocracy</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 16 May 2017 00:00:00 +0000</lastBuildDate><atom:link href="https://www.ericsimmerman.com/tags/aws-lambda/index.xml" rel="self" type="application/rss+xml"/><item><title>Knock first firewall for AWS Security Groups</title><link>https://www.ericsimmerman.com/blog/2017/05/16/knock-first-firewall-for-aws-security-groups/</link><pubDate>Tue, 16 May 2017 00:00:00 +0000</pubDate><guid>https://www.ericsimmerman.com/blog/2017/05/16/knock-first-firewall-for-aws-security-groups/</guid><description>&lt;p&gt;I recently &lt;a href="./2017-05-01-setting-up-bastion-host-aws.html" rel=""&gt;setup a Bastion host&lt;/a&gt; to secure a development environment on AWS. The Bastion only exposes port 22 for SSH and I wanted to restrict access to a whitelist of authorized IP addresses rather than leave port 22 open to the internet. Further - I wanted to restrict 443 and 80 inbound to the development environment so that only authorized users/developers could access the pre-release builds deployed there.&lt;/p&gt;</description></item></channel></rss>