<?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: Curtis</title>
    <description>The latest articles on DEV Community by Curtis (@castrapel).</description>
    <link>https://dev.to/castrapel</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%2F1081576%2F6d8219fe-b9e4-41a4-bbff-8488bac2bd37.jpeg</url>
      <title>DEV Community: Curtis</title>
      <link>https://dev.to/castrapel</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/castrapel"/>
    <language>en</language>
    <item>
      <title>Track AWS IAM changes in Git</title>
      <dc:creator>Curtis</dc:creator>
      <pubDate>Tue, 22 Aug 2023 13:38:01 +0000</pubDate>
      <link>https://dev.to/castrapel/track-aws-iam-changes-in-git-1mn5</link>
      <guid>https://dev.to/castrapel/track-aws-iam-changes-in-git-1mn5</guid>
      <description>&lt;p&gt;For DevOps/CloudSec professionals navigating the complexities of AWS IAM configurations, our recent blog post shines a light on how IAMbic keeps track of all IAM changes within version control, now with CloudTrail attribution. From Terraform to direct AWS Console adjustments, every change is documented in your Git history regardless of how the change was made. Full details in our latest blog post!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.noq.dev/blog/iambic-bridging-the-gap-between-iam-changes-and-version-control"&gt;https://www.noq.dev/blog/iambic-bridging-the-gap-between-iam-changes-and-version-control&lt;/a&gt; &lt;/p&gt;

</description>
      <category>aws</category>
      <category>iam</category>
      <category>security</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
