<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Elijah Udom | Infrastructure &amp; Cloud Engineer (elijahu)</title><link>https://dev.elijahu.me/portfolio/tags/cli/</link><description>Infrastructure &amp; Cloud Engineering portfolio by Elijah Udom (elijahu) — AWS, Kubernetes, eBPF Security, AI/ML Infrastructure, and Platform Engineering projects.</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 06 Mar 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://dev.elijahu.me/portfolio/tags/cli/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an AWS Security Group Auditor That Actually Works in Production</title><link>https://dev.elijahu.me/portfolio/projects/aws-security-auditor/</link><pubDate>Thu, 06 Mar 2025 00:00:00 +0000</pubDate><guid>https://dev.elijahu.me/portfolio/projects/aws-security-auditor/</guid><description>&amp;ldquo;Manually checking security groups across multiple AWS accounts is how breaches happen. You miss things. You always miss things.&amp;rdquo;
Manual security group reviews feel fine at one account. At ten, you&amp;rsquo;re genuinely flying blind — too many rules, too much context to hold in your head, no audit trail. I built this CLI tool to close that gap. This is the breakdown: what I built, the failure modes I hit, and what the production version actually looks like.</description></item></channel></rss>