<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Habib Kaghas</title>
    <description>The latest articles on DEV Community by Habib Kaghas (@habib_kaghas).</description>
    <link>https://dev.to/habib_kaghas</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3918411%2F40727543-3241-4123-bf62-0d95359fd031.png</url>
      <title>DEV Community: Habib Kaghas</title>
      <link>https://dev.to/habib_kaghas</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/habib_kaghas"/>
    <language>en</language>
    <item>
      <title>Map Your Entire AWS Infrastructure in 60 Seconds</title>
      <dc:creator>Habib Kaghas</dc:creator>
      <pubDate>Thu, 07 May 2026 17:23:24 +0000</pubDate>
      <link>https://dev.to/habib_kaghas/map-your-entire-aws-infrastructure-in-60-seconds-5ck5</link>
      <guid>https://dev.to/habib_kaghas/map-your-entire-aws-infrastructure-in-60-seconds-5ck5</guid>
      <description>&lt;p&gt;&lt;strong&gt;If you've ever inherited an AWS account, you know the feeling.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;You open the console, click around a few services, and realise pretty quickly that you have no idea what's actually running. EC2 instances nobody recognises. &lt;/p&gt;

&lt;p&gt;Security groups with ports open that shouldn't be. S3 buckets from three projects ago. RDS instances that might still be in use — or might not.&lt;/p&gt;

&lt;p&gt;It’s nobody’s fault. AWS sprawl happens when a team moves quickly over time.&lt;/p&gt;

&lt;p&gt;The problem is, most of the solutions people reach for don't actually solve it.&lt;/p&gt;




&lt;h2&gt;
  
  
  The usual approaches (and why they fall short)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;📊 Spreadsheets.&lt;/strong&gt; Someone on the team volunteers to document everything &lt;br&gt;
manually. It takes a week, and by the time it's done, it's already out of date. &lt;br&gt;
AWS moves faster than any spreadsheet.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;⚙️ AWS Config.&lt;/strong&gt; Powerful, but complex to set up, expensive at scale, and it gives you raw data — not insight. You still have to do all the interpretation yourself.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;🖱️ Clicking through the console.&lt;/strong&gt; This is what most people actually do. &lt;br&gt;
Service by service, region by region. It works until you have 10+ services and multiple regions, at which point it becomes a full-time job.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;📜 The script someone wrote that one time.&lt;/strong&gt; You know the one. It's in a private repo, untouched for 18 months, and three people have contributed to it without informing each other.&lt;/p&gt;

&lt;p&gt;None of these gives you a complete, accurate, up-to-date picture of your infrastructure. And without that picture, everything else — compliance, security reviews, cost optimisation, incident response — becomes harder than it needs to be.&lt;/p&gt;




&lt;h2&gt;
  
  
  A different approach
&lt;/h2&gt;

&lt;p&gt;Earlier this year, we built &lt;a href="https://app.solidstack.ae" rel="noopener noreferrer"&gt;InfraMind&lt;/a&gt; to solve exactly this problem.&lt;/p&gt;

&lt;p&gt;The idea was simple: connect it to your AWS account, and get a complete map of everything running — automatically, in under a minute, without writing a single line of code.&lt;/p&gt;

&lt;p&gt;Here's what actually happens when you run it:&lt;/p&gt;

&lt;h3&gt;
  
  
  1. 🔍 It crawls your account across 55 AWS services
&lt;/h3&gt;

&lt;p&gt;EC2, RDS, Lambda, S3, VPC, EKS, ECS, IAM, CloudFront, Route53, and 45 more. &lt;br&gt;
Every resource, every region, pulled in one pass.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. 🤖 AI analyses everything it finds
&lt;/h3&gt;

&lt;p&gt;Not just listing resources — actually understanding them. It identifies misconfigurations, unused resources, security gaps, and relationships between services. The kind of analysis that would take a senior engineer hours to do manually.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. 🗺️ You get architecture diagrams across 6 views
&lt;/h3&gt;

&lt;p&gt;Overview, network topology, security, database layer, serverless, and storage. &lt;br&gt;
Auto-generated, always in sync with your actual infrastructure. No Lucidchart. &lt;br&gt;
No draw.io. No manual updates.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. 📦 Terraform HCL export for 42 services
&lt;/h3&gt;

&lt;p&gt;This one is huge if you're trying to get your infra under version control. &lt;br&gt;
InfraMind generates production-ready Terraform for what's already running — so you can start managing existing resources as code without writing it all from scratch.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. ✅ Compliance reports across 8 frameworks
&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;CIS Benchmarks · PCI DSS · HIPAA · SOC 2 · ISO 27001 · GDPR · NIST SP &lt;br&gt;
800-53 · FedRAMP&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;One click, full report, no consultants required.&lt;/p&gt;




&lt;h2&gt;
  
  
  The bit that surprised us most
&lt;/h2&gt;

&lt;p&gt;When we started testing it internally, we thought the Terraform export would be the most-used feature.&lt;/p&gt;

&lt;p&gt;It wasn't. The thing people kept coming back to was the architecture diagram — specifically the moment when they saw their actual infrastructure mapped out visually for the first time.&lt;/p&gt;

&lt;p&gt;For some teams, that was a &lt;em&gt;"oh that's what we have"&lt;/em&gt; moment. For others, it was more like &lt;em&gt;"wait, why is that connected to that?"&lt;/em&gt; Either way, it's information they didn't have before, and it changes how the team talks about the &lt;br&gt;
infrastructure.&lt;/p&gt;




&lt;h2&gt;
  
  
  Change detection
&lt;/h2&gt;

&lt;p&gt;One last thing worth mentioning: InfraMind doesn't just give you a one-time snapshot. It monitors your infrastructure for changes and sends alerts to Slack when something shifts.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Event&lt;/th&gt;
&lt;th&gt;Alert&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;New resource spun up&lt;/td&gt;
&lt;td&gt;✅ Slack and email notifications&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Security group modified&lt;/td&gt;
&lt;td&gt;✅ Slack and email notifications&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Resource deleted&lt;/td&gt;
&lt;td&gt;✅ Slack and email notifications&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Compliance status changed&lt;/td&gt;
&lt;td&gt;✅ Slack and email notifications&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;There's a free plan at &lt;a href="https://app.solidstack.ae" rel="noopener noreferrer"&gt;app.solidstack.ae&lt;/a&gt; — no credit card needed. Connect your AWS account, and you'll have a full map of your infrastructure in under a minute.&lt;/p&gt;

&lt;p&gt;If you're managing AWS at any scale and you've ever felt like you're flying blind, it's worth 60 seconds to find out what's actually there.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Questions or feedback welcome in the comments — especially if you've dealt &lt;br&gt;
with AWS sprawl differently. Always curious how other teams handle it.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>aws</category>
      <category>devops</category>
      <category>terraform</category>
      <category>infrastructure</category>
    </item>
  </channel>
</rss>
