<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GenAI Modernization Transform on Adam Divall</title>
    <link>/tags/genai-modernization-transform/</link>
    <description>Recent content in GenAI Modernization Transform on Adam Divall</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 28 Apr 2026 13:59:53 +0100</lastBuildDate>
    <atom:link href="/tags/genai-modernization-transform/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From Analysis to Remediation in Minutes: Using AWS Transform and Kiro to Tackle IaC Technical Debt</title>
      <link>/article/opinion/kiro-transform-analysis-to-remediation/</link>
      <pubDate>Tue, 28 Apr 2026 13:59:53 +0100</pubDate>
      <guid>/article/opinion/kiro-transform-analysis-to-remediation/</guid>
      <description>&lt;p&gt;Infrastructure-as-Code repositories have a habit of quietly accumulating technical debt. A Lambda runtime drifts toward end-of-life, a copy-pasted resource block introduces a subtle bug, IAM policies stay broader than they need to be. These issues rarely surface until something breaks in production — or until an auditor asks uncomfortable questions.&lt;/p&gt;&#xA;&lt;p&gt;In this post, I walk through how I used &lt;strong&gt;AWS Transform&lt;/strong&gt; (ATX) inside &lt;strong&gt;Kiro&lt;/strong&gt; to perform a comprehensive analysis of a real CloudFormation project, surface seven technical debt findings, and remediate six of them — all without leaving the IDE.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
