<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>aws on Security Addict</title><link>https://blog.medarkus.net/tags/aws/</link><description>Recent content in aws on Security Addict</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>me@darkus.dev (DeMarcus Williams)</managingEditor><webMaster>me@darkus.dev (DeMarcus Williams)</webMaster><lastBuildDate>Sun, 18 Dec 2022 19:17:59 -0500</lastBuildDate><atom:link href="https://blog.medarkus.net/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>Stop Opening Port 22❗️ (An AWS Tip)</title><link>https://blog.medarkus.net/posts/stop-opening-port-22/</link><pubDate>Sun, 18 Dec 2022 19:17:59 -0500</pubDate><author>me@darkus.dev (DeMarcus Williams)</author><guid>https://blog.medarkus.net/posts/stop-opening-port-22/</guid><description>Overview If you&amp;rsquo;re familiar with AWS and EC2 instances you&amp;rsquo;ve probably had to configure a security group1 or two before, if for no other reason than to allow traffic to port 22 of your EC2 instances. Well today I hope to teach you a new way to connect to port 22, or any port for that matter, without needing to expose it to the internet.
The rest of this tutorial assumes you&amp;rsquo;re familiar with/have configured the AWS CLI.</description></item></channel></rss>