<?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: Vedas Kudalkar</title>
    <description>The latest articles on DEV Community by Vedas Kudalkar (@axololtos_30).</description>
    <link>https://dev.to/axololtos_30</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1956592%2Fd53bd446-1df5-4fdd-a48c-d65b0fb19603.jpg</url>
      <title>DEV Community: Vedas Kudalkar</title>
      <link>https://dev.to/axololtos_30</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/axololtos_30"/>
    <language>en</language>
    <item>
      <title>I just wrote a boto3 scanner that finds and fixes S3 and IAM misconfigurations on Floci, a local AWS emulator, then wired a drift alert and rebuilt the same setup in Terraform. Want to check out? read here</title>
      <dc:creator>Vedas Kudalkar</dc:creator>
      <pubDate>Fri, 20 Nov 2026 11:27:23 +0000</pubDate>
      <link>https://dev.to/axololtos_30/i-just-wrote-a-boto3-scanner-that-finds-and-fixes-s3-and-iam-misconfigurations-on-floci-a-local-jio</link>
      <guid>https://dev.to/axololtos_30/i-just-wrote-a-boto3-scanner-that-finds-and-fixes-s3-and-iam-misconfigurations-on-floci-a-local-jio</guid>
      <description>&lt;div class="ltag__link--embedded"&gt;
  &lt;div class="crayons-story "&gt;
  &lt;a href="https://dev.to/axololtos_30/build-a-cloud-security-scanner-without-touching-a-real-aws-account-532p" class="crayons-story__hidden-navigation-link"&gt;Build a cloud security scanner without touching a real AWS account&lt;/a&gt;


  &lt;div class="crayons-story__body crayons-story__body-full_post"&gt;
    &lt;div class="crayons-story__top"&gt;
      &lt;div class="crayons-story__meta"&gt;
        &lt;div class="crayons-story__author-pic"&gt;

          &lt;a href="/axololtos_30" class="crayons-avatar  crayons-avatar--l  "&gt;
            &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1956592%2Fd53bd446-1df5-4fdd-a48c-d65b0fb19603.jpg" alt="axololtos_30 profile" class="crayons-avatar__image" width="564" height="564"&gt;
          &lt;/a&gt;
        &lt;/div&gt;
        &lt;div&gt;
          &lt;div&gt;
            &lt;a href="/axololtos_30" class="crayons-story__secondary fw-medium m:hidden"&gt;
              Vedas Kudalkar
            &lt;/a&gt;
            &lt;div class="profile-preview-card relative mb-4 s:mb-0 fw-medium hidden m:inline-block"&gt;
              
                Vedas Kudalkar
                
                
              
              &lt;div id="story-author-preview-content-5080939" class="profile-preview-card__content crayons-dropdown branded-7 p-4 pt-0"&gt;
                &lt;div class="gap-4 grid"&gt;
                  &lt;div class="-mt-4"&gt;
                    &lt;a href="/axololtos_30" class="flex"&gt;
                      &lt;span class="crayons-avatar crayons-avatar--xl mr-2 shrink-0"&gt;
                        &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1956592%2Fd53bd446-1df5-4fdd-a48c-d65b0fb19603.jpg" class="crayons-avatar__image" alt="" width="564" height="564"&gt;
                      &lt;/span&gt;
                      &lt;span class="crayons-link crayons-subtitle-2 mt-5"&gt;Vedas Kudalkar&lt;/span&gt;
                    &lt;/a&gt;
                  &lt;/div&gt;
                  &lt;div class="print-hidden"&gt;
                    
                      Follow
                    
                  &lt;/div&gt;
                  &lt;div class="author-preview-metadata-container"&gt;&lt;/div&gt;
                &lt;/div&gt;
              &lt;/div&gt;
            &lt;/div&gt;

          &lt;/div&gt;
          &lt;a href="https://dev.to/axololtos_30/build-a-cloud-security-scanner-without-touching-a-real-aws-account-532p" class="crayons-story__tertiary fs-xs"&gt;&lt;time&gt;Nov 20&lt;/time&gt;&lt;span class="time-ago-indicator-initial-placeholder"&gt;&lt;/span&gt;&lt;/a&gt;
        &lt;/div&gt;
      &lt;/div&gt;

    &lt;/div&gt;

    &lt;div class="crayons-story__indention"&gt;
      &lt;h2 class="crayons-story__title crayons-story__title-full_post"&gt;
        &lt;a href="https://dev.to/axololtos_30/build-a-cloud-security-scanner-without-touching-a-real-aws-account-532p" id="article-link-5080939"&gt;
          Build a cloud security scanner without touching a real AWS account
        &lt;/a&gt;
      &lt;/h2&gt;
        &lt;div class="crayons-story__tags"&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/aws"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;aws&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/security"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;security&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/terraform"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;terraform&lt;/a&gt;
            &lt;a class="crayons-tag  crayons-tag--monochrome " href="/t/python"&gt;&lt;span class="crayons-tag__prefix"&gt;#&lt;/span&gt;python&lt;/a&gt;
        &lt;/div&gt;
      &lt;div class="crayons-story__bottom"&gt;
        &lt;div class="crayons-story__details"&gt;
          &lt;a href="https://dev.to/axololtos_30/build-a-cloud-security-scanner-without-touching-a-real-aws-account-532p" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left"&gt;
            &lt;div class="multiple_reactions_aggregate"&gt;
              &lt;span class="multiple_reactions_icons_container"&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/fire-f60e7a582391810302117f987b22a8ef04a2fe0df7e3258a5f49332df1cec71e.svg" width="24" height="24"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/raised-hands-74b2099fd66a39f2d7eed9305ee0f4553df0eb7b4f11b01b6b1b499973048fe5.svg" width="24" height="24"&gt;
                  &lt;/span&gt;
                  &lt;span class="crayons_icon_container"&gt;
                    &lt;img src="https://assets.dev.to/assets/sparkle-heart-5f9bee3767e18deb1bb725290cb151c25234768a0e9a2bd39370c382d02920cf.svg" width="24" height="24"&gt;
                  &lt;/span&gt;
              &lt;/span&gt;
              &lt;span class="aggregate_reactions_counter"&gt;3&lt;span class="hidden s:inline"&gt;&amp;nbsp;reactions&lt;/span&gt;&lt;/span&gt;
            &lt;/div&gt;
          &lt;/a&gt;
            &lt;a href="https://dev.to/axololtos_30/build-a-cloud-security-scanner-without-touching-a-real-aws-account-532p#comments" class="crayons-btn crayons-btn--s crayons-btn--ghost crayons-btn--icon-left flex items-center"&gt;
              

              &lt;span class="hidden s:inline"&gt;Add&amp;nbsp;Comment&lt;/span&gt;
            &lt;/a&gt;
        &lt;/div&gt;
        &lt;div class="crayons-story__save"&gt;
          &lt;small class="crayons-story__tertiary fs-xs mr-2"&gt;
            8 min read
          &lt;/small&gt;
          
          &lt;div class="only-sidebar-menu-item trusted-visible-block print-hidden align-center"&gt;
                
                    
                
          &lt;/div&gt;

        &lt;/div&gt;
      &lt;/div&gt;
    &lt;/div&gt;
  &lt;/div&gt;
&lt;/div&gt;


&lt;/div&gt;


</description>
      <category>aws</category>
      <category>python</category>
      <category>security</category>
      <category>terraform</category>
    </item>
    <item>
      <title>Build a cloud security scanner without touching a real AWS account</title>
      <dc:creator>Vedas Kudalkar</dc:creator>
      <pubDate>Fri, 20 Nov 2026 10:29:47 +0000</pubDate>
      <link>https://dev.to/axololtos_30/build-a-cloud-security-scanner-without-touching-a-real-aws-account-532p</link>
      <guid>https://dev.to/axololtos_30/build-a-cloud-security-scanner-without-touching-a-real-aws-account-532p</guid>
      <description>&lt;p&gt;&lt;em&gt;A deliberately broken S3 bucket and IAM role, a scanner that fixes them, a drift alarm, and a Terraform rebuild that scans clean. Floci in Docker. No AWS account.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;To practice cloud security without an AWS account, I built a boto3 scanner and pointed it at Floci, a local AWS emulator on port 4566. It finds 5 misconfigurations in a bucket and a role I broke on purpose, fixes them, and exits clean. When I break the bucket again, an alarm fires and a message lands in an SQS inbox. Then I rebuild the same environment in Terraform and the scanner finds nothing.&lt;/p&gt;

&lt;p&gt;Most of it worked as written. A few parts needed workarounds: Floci has no &lt;code&gt;GetBucketPolicyStatus&lt;/code&gt;, S3 encryption is always on so "is it encrypted" is the wrong question, and the alarm lags its own alert by about a minute. This post covers the scanner, the alerting chain, and those three.&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/axololtos/local-cloud-security-lab" rel="noopener noreferrer"&gt;axololtos/local-cloud-security-lab&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why emulate it
&lt;/h2&gt;

&lt;p&gt;Posture tools like Prowler, AWS Config and Security Hub are built for real accounts. I wanted to see what a public bucket finding looks like, and test auto-remediation, without making a public bucket anywhere I care about. A local emulator removes that risk. &lt;code&gt;08-cleanup.ps1&lt;/code&gt; tears the lab down and the scripts rebuild it.&lt;/p&gt;

&lt;p&gt;The trade-off is fidelity. Floci implements the API surface, not every behavior behind it. Access enforcement is off by default, so my "public" bucket is public in configuration only. The lab shows detection and remediation, not exploitation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Architecture
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffjh0id2vuwk6u17muef5.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffjh0id2vuwk6u17muef5.png" alt="Architecture of the lab" width="800" height="477"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Stack:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Floci&lt;/strong&gt; (&lt;code&gt;floci/floci:latest&lt;/code&gt;) as the AWS emulator.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scanner:&lt;/strong&gt; Python 3 with boto3.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Alerting:&lt;/strong&gt; CloudWatch Logs, a metric filter, a CloudWatch alarm, SNS and SQS.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;IaC:&lt;/strong&gt; Terraform with the AWS provider.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Glue:&lt;/strong&gt; PowerShell scripts, &lt;code&gt;01-start-floci.ps1&lt;/code&gt; through &lt;code&gt;08-cleanup.ps1&lt;/code&gt;, plus a shared &lt;code&gt;env.ps1&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Pointing the CLI at Floci
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;env.ps1&lt;/code&gt; is the only AWS configuration in the project. Fake credentials and one endpoint:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="no"&gt;AWS_ENDPOINT_URL&lt;/span&gt;      &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"http://localhost:4566"&lt;/span&gt;
&lt;span class="nv"&gt;$env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="no"&gt;AWS_DEFAULT_REGION&lt;/span&gt;    &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"us-east-1"&lt;/span&gt;
&lt;span class="nv"&gt;$env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="no"&gt;AWS_ACCESS_KEY_ID&lt;/span&gt;     &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"test"&lt;/span&gt;
&lt;span class="nv"&gt;$env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="no"&gt;AWS_SECRET_ACCESS_KEY&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"test"&lt;/span&gt;
&lt;span class="nv"&gt;$env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="no"&gt;AWS_PAGER&lt;/span&gt;             &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt;     &lt;span class="c1"&gt;# stop the CLI pausing at "-- More --"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;AWS_ENDPOINT_URL&lt;/code&gt; is the global endpoint override in recent CLI v2 builds, so no &lt;code&gt;--endpoint-url&lt;/code&gt; flag is needed. The scanner reads the same variable, so boto3 and the CLI hit the same place. &lt;code&gt;aws sts get-caller-identity&lt;/code&gt; returns account &lt;code&gt;000000000000&lt;/code&gt;, which confirms the CLI is talking to Floci.&lt;/p&gt;

&lt;p&gt;Visual instruction: Capture the top of &lt;code&gt;env.ps1&lt;/code&gt; in VS Code using the OneDark-Pro theme. Use a readable font size and crop unnecessary editor UI.&lt;/p&gt;

&lt;h2&gt;
  
  
  The broken baseline
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;02-baseline.ps1&lt;/code&gt; creates four misconfigurations on a bucket named &lt;code&gt;sec-lab-data&lt;/code&gt; and a role named &lt;code&gt;sec-lab-app-role&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;aws&lt;/span&gt; &lt;span class="n"&gt;s3api&lt;/span&gt; &lt;span class="n"&gt;delete&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;public&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;access&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;block&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;bucket&lt;/span&gt; &lt;span class="nv"&gt;$Bucket&lt;/span&gt;

&lt;span class="nv"&gt;$policy&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'{"Version":"2012-10-17","Statement":[{"Sid":"PublicRead","Effect":"Allow","Principal":"*","Action":"s3:GetObject","Resource":"arn:aws:s3:::'&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="nv"&gt;$Bucket&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="s1"&gt;'/*"}]}'&lt;/span&gt;
&lt;span class="n"&gt;aws&lt;/span&gt; &lt;span class="n"&gt;s3api&lt;/span&gt; &lt;span class="n"&gt;put&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;bucket&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;policy&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;bucket&lt;/span&gt; &lt;span class="nv"&gt;$Bucket&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;policy&lt;/span&gt; &lt;span class="s2"&gt;"file://$pf"&lt;/span&gt;

&lt;span class="nv"&gt;$wild&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'{"Version":"2012-10-17","Statement":[{"Effect":"Allow","Action":"*","Resource":"*"}]}'&lt;/span&gt;
&lt;span class="n"&gt;aws&lt;/span&gt; &lt;span class="n"&gt;iam&lt;/span&gt; &lt;span class="n"&gt;put&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;role&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;policy&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;role&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="nv"&gt;$Role&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;policy&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="n"&gt;allow&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;everything&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;policy&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;document&lt;/span&gt; &lt;span class="s2"&gt;"file://$wf"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The bucket also has no versioning, SSE-S3 only, and holds a fake &lt;code&gt;secret-information.txt&lt;/code&gt; containing &lt;code&gt;FAKE-DEMO-SECRET: db_password=not-a-real-password&lt;/code&gt;. Nothing real is in the lab.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fri5793vhfvbrrnwki84a.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fri5793vhfvbrrnwki84a.png" alt="Floci identity check and baseline output" width="800" height="422"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn1u7y46ip02cn1xh1ylv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fn1u7y46ip02cn1xh1ylv.png" alt="Floci UI: sec-lab-app-role and sec-lab-tf-app-role" width="799" height="227"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The scanner
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;scanner/scanner.py&lt;/code&gt; is one file. The design choice that shaped everything: each finding carries its own fix as a function.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;finding&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;fid&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;sev&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;resource&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;detail&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;fix&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="s2"&gt;"id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;fid&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"severity"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;sev&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"resource"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;resource&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"detail"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;detail&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"fix"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;fix&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A scan builds a list of these. With &lt;code&gt;--fix&lt;/code&gt; it calls each &lt;code&gt;fix&lt;/code&gt;, then scans again. Detection and remediation sit next to each other, so they cannot disagree about what "broken" means.&lt;/p&gt;

&lt;p&gt;Boto3 raises &lt;code&gt;ClientError&lt;/code&gt; for things that are simply not configured, such as &lt;code&gt;NoSuchBucketPolicy&lt;/code&gt;. A small helper turns the expected codes into &lt;code&gt;None&lt;/code&gt; and re-raises the rest:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;call_or_none&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;fn&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="n"&gt;ok_codes&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kw&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="k"&gt;try&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nf"&gt;fn&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;kw&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;except&lt;/span&gt; &lt;span class="nc"&gt;ClientError&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;e&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="nf"&gt;err_code&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;e&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="n"&gt;ok_codes&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="kc"&gt;None&lt;/span&gt;
        &lt;span class="k"&gt;raise&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The rules:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;ID&lt;/th&gt;
&lt;th&gt;Severity&lt;/th&gt;
&lt;th&gt;Remediation&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;S3-PUBLIC-POLICY&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;HIGH&lt;/td&gt;
&lt;td&gt;Delete the policy&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;S3-PUBLIC-ACL&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;HIGH&lt;/td&gt;
&lt;td&gt;Set ACL to private&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;S3-NO-PUBLIC-ACCESS-BLOCK&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;HIGH&lt;/td&gt;
&lt;td&gt;Enable all 4 flags&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;S3-NO-KMS-ENCRYPTION&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;MEDIUM&lt;/td&gt;
&lt;td&gt;Set KMS default encryption&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;S3-NO-VERSIONING&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;LOW&lt;/td&gt;
&lt;td&gt;Enable versioning&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;IAM-WILDCARD-ACTION&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;HIGH&lt;/td&gt;
&lt;td&gt;Delete that inline policy&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;IAM-ADMIN-ATTACHED&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;HIGH&lt;/td&gt;
&lt;td&gt;Detach it&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The scanner only touches buckets and roles whose names start with &lt;code&gt;--prefix&lt;/code&gt; (default &lt;code&gt;sec-lab&lt;/code&gt;), and it refuses an empty one:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="n"&gt;a&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;prefix&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;sys&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;exit&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"--prefix must not be empty (it protects other resources on the emulator)"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A tool that can delete policies should not be one typo away from acting on everything on a shared emulator.&lt;/p&gt;

&lt;h3&gt;
  
  
  Problem 1: no GetBucketPolicyStatus
&lt;/h3&gt;

&lt;p&gt;On real AWS you can ask whether a bucket policy is public. Floci does not implement &lt;code&gt;GetBucketPolicyStatus&lt;/code&gt;, so the scanner parses the policy itself. The check is deliberately small:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;is_public_statement&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;st&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;st&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Effect"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="s2"&gt;"Allow"&lt;/span&gt; &lt;span class="ow"&gt;or&lt;/span&gt; &lt;span class="n"&gt;st&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Condition"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="kc"&gt;False&lt;/span&gt;  &lt;span class="c1"&gt;# conditioned statements may be narrowed; heuristic skips them (limitation)&lt;/span&gt;
    &lt;span class="n"&gt;p&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;st&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Principal"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="s2"&gt;"*"&lt;/span&gt; &lt;span class="ow"&gt;or&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;isinstance&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="kt"&gt;dict&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="ow"&gt;and&lt;/span&gt; &lt;span class="s2"&gt;"*"&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="nf"&gt;as_list&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"AWS"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;An &lt;code&gt;Allow&lt;/code&gt; to a wildcard principal with no &lt;code&gt;Condition&lt;/code&gt; counts as public. It misses &lt;code&gt;NotPrincipal&lt;/code&gt;, conditioned statements, access points and account-level Block Public Access. Those gaps are in the README.&lt;/p&gt;

&lt;p&gt;Visual instruction: Capture this exact code section in VS Code using the OneDark-Pro theme. Use a readable font size and crop unnecessary editor UI.&lt;/p&gt;

&lt;h3&gt;
  
  
  Problem 2: encryption is always on
&lt;/h3&gt;

&lt;p&gt;New S3 buckets are SSE-S3 encrypted by default, so a check for "is it encrypted" never fires. The useful question is whether the bucket uses a key you control, so the rule looks for &lt;code&gt;aws:kms&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="s2"&gt;"aws:kms"&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="n"&gt;algos&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;
    &lt;span class="n"&gt;out&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;finding&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"S3-NO-KMS-ENCRYPTION"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"MEDIUM"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;res&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
                       &lt;span class="s2"&gt;"default encryption is not a customer-managed KMS key (SSE-S3 only)"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;fix_enc&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The fix needs a key, so &lt;code&gt;fix_enc&lt;/code&gt; raises &lt;code&gt;needs --kms-key-id&lt;/code&gt; if you forget one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Scan, fix, re-scan
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;cd&lt;/span&gt; &lt;span class="n"&gt;cmd&lt;/span&gt;\&lt;span class="n"&gt;scripts&lt;/span&gt;
&lt;span class="nc"&gt;Set&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;ExecutionPolicy&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Scope&lt;/span&gt; &lt;span class="k"&gt;Process&lt;/span&gt; &lt;span class="nc"&gt;Bypass&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;01&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;start&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;floci&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;02&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;baseline&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;03&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;scan&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;   &lt;span class="c1"&gt;# BEFORE: 5 finding(s)&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;04&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;fix&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;    &lt;span class="c1"&gt;# AFTER: 0 finding(s)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Step 01 reuses whatever already serves port 4566, or starts Floci from &lt;code&gt;compose.yaml&lt;/code&gt;. Step 03 is read-only and writes &lt;code&gt;work\report-before.json&lt;/code&gt;. Step 04 creates a KMS key with alias &lt;code&gt;alias/sec-lab&lt;/code&gt; if it does not exist, then runs:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="o"&gt;&amp;amp;&lt;/span&gt; &lt;span class="nv"&gt;$Py&lt;/span&gt; &lt;span class="s2"&gt;"$Root\scanner\scanner.py"&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;prefix&lt;/span&gt; &lt;span class="nv"&gt;$Prefix&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;fix&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;kms&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;key&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;id&lt;/span&gt; &lt;span class="n"&gt;alias&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;sec&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;lab&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;report&lt;/span&gt; &lt;span class="s2"&gt;"$Work\report-after.json"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The scanner exits &lt;code&gt;1&lt;/code&gt; when findings remain and &lt;code&gt;0&lt;/code&gt; when clean, so the same command can gate a pipeline.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftcbxxshh7tm3x3615hd9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ftcbxxshh7tm3x3615hd9.png" alt="report-before.json with 5 findings next to report-after.json" width="800" height="498"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The IAM fix is blunt on purpose. It deletes the offending inline policy and writes no replacement, which leaves the role deny-by-default. A good replacement needs real usage data, and a scanner should not guess it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Alerting
&lt;/h2&gt;

&lt;p&gt;A scanner you run by hand helps once. Step 05 builds the chain that tells you when something comes back:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;aws&lt;/span&gt; &lt;span class="n"&gt;logs&lt;/span&gt; &lt;span class="n"&gt;put&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;metric&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="k"&gt;filter&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;group&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="nv"&gt;$LogGroup&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="k"&gt;filter&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="n"&gt;high&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;findings&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="k"&gt;filter&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;pattern&lt;/span&gt; &lt;span class="no"&gt;SECFINDING_HIGH&lt;/span&gt; &lt;span class="sb"&gt;`
    --metric-transformations "metricName=HighFindings,metricNamespace=SecLab,metricValue=1"

aws cloudwatch put-metric-alarm --alarm-name $Alarm --namespace SecLab --metric-name HighFindings --statistic Sum `&lt;/span&gt;
    &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;period&lt;/span&gt; &lt;span class="mi"&gt;60&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;evaluation&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;periods&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;threshold&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;comparison&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;operator&lt;/span&gt; &lt;span class="nc"&gt;GreaterThanOrEqualToThreshold&lt;/span&gt; &lt;span class="sb"&gt;`
    --treat-missing-data notBreaching --alarm-actions $tArn
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The scanner writes one &lt;code&gt;SECFINDING_&amp;lt;SEVERITY&amp;gt; id=... resource=... detail=...&lt;/code&gt; line per finding to CloudWatch Logs, and publishes a summary to the SNS topic. The metric filter counts &lt;code&gt;SECFINDING_HIGH&lt;/code&gt; lines, the alarm fires at &lt;code&gt;Sum &amp;gt;= 1&lt;/code&gt; per 60 seconds, and the topic delivers to an SQS queue that stands in for email. A single greppable prefix drives the whole alarm, so the scanner needs no custom metric code.&lt;/p&gt;

&lt;h3&gt;
  
  
  Drift
&lt;/h3&gt;

&lt;p&gt;Step 06 re-runs the baseline to re-open the bucket and bring back the wildcard role, then scans with alerting on. The scan reports 3 findings, not 5, because KMS encryption and versioning from the fix stay on.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F08xih1rxy5ffnzkyy2bu.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F08xih1rxy5ffnzkyy2bu.png" alt="Steps 05 and 06 output: alerting wired, drift detected with 3 findings" width="800" height="460"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmeu04yskxijauwh974ty.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmeu04yskxijauwh974ty.png" alt="Alert message waiting in the SQS inbox" width="799" height="248"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fps6utmaspb459za7hhhg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fps6utmaspb459za7hhhg.png" alt="Alarm sec-lab-high-findings on SecLab/HighFindings" width="800" height="277"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Problem 3: the alarm lags the alert
&lt;/h3&gt;

&lt;p&gt;The alarm evaluates on a 60 second period, so right after step 06 its state can read &lt;code&gt;OK&lt;/code&gt; or &lt;code&gt;INSUFFICIENT_DATA&lt;/code&gt; even though the message is already in the inbox. Re-run &lt;code&gt;describe-alarms&lt;/code&gt; after a minute and it catches up.&lt;/p&gt;

&lt;h2&gt;
  
  
  Rebuild it in Terraform
&lt;/h2&gt;

&lt;p&gt;Fixing a broken bucket is the reactive half. &lt;code&gt;terraform/main.tf&lt;/code&gt; is the proactive half: the same environment, secure from the first apply. All four Block Public Access flags, a KMS key with &lt;code&gt;aws:kms&lt;/code&gt; default encryption, versioning, and a role limited to reading objects from one bucket:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight hcl"&gt;&lt;code&gt;&lt;span class="n"&gt;resource&lt;/span&gt; &lt;span class="s2"&gt;"aws_iam_role_policy"&lt;/span&gt; &lt;span class="s2"&gt;"app_read"&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"read-data-bucket"&lt;/span&gt;
  &lt;span class="n"&gt;role&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;aws_iam_role&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;app&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;id&lt;/span&gt;
  &lt;span class="n"&gt;policy&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;jsonencode&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nc"&gt;Version&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"2012-10-17"&lt;/span&gt;
    &lt;span class="nc"&gt;Statement&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nc"&gt;Effect&lt;/span&gt;   &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"Allow"&lt;/span&gt;
      &lt;span class="nc"&gt;Action&lt;/span&gt;   &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"s3:GetObject"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
      &lt;span class="nc"&gt;Resource&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"${aws_s3_bucket.data.arn}/*"&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The provider block follows Floci's own compatibility tests: skip the credential and metadata checks, use path-style S3, and override the endpoints for S3, IAM, STS and KMS.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight hcl"&gt;&lt;code&gt;&lt;span class="n"&gt;provider&lt;/span&gt; &lt;span class="s2"&gt;"aws"&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;region&lt;/span&gt;     &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"us-east-1"&lt;/span&gt;
  &lt;span class="n"&gt;access_key&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"test"&lt;/span&gt;
  &lt;span class="n"&gt;secret_key&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"test"&lt;/span&gt;

  &lt;span class="n"&gt;skip_credentials_validation&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
  &lt;span class="n"&gt;skip_metadata_api_check&lt;/span&gt;     &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
  &lt;span class="n"&gt;skip_requesting_account_id&lt;/span&gt;  &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
  &lt;span class="n"&gt;s3_use_path_style&lt;/span&gt;           &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
  &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;07-terraform.ps1&lt;/code&gt; runs &lt;code&gt;terraform init&lt;/code&gt; and &lt;code&gt;apply&lt;/code&gt;, then scans only the Terraform resources with prefix &lt;code&gt;sec-lab-tf&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="o"&gt;&amp;amp;&lt;/span&gt; &lt;span class="nv"&gt;$Py&lt;/span&gt; &lt;span class="s2"&gt;"$Root\scanner\scanner.py"&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;prefix&lt;/span&gt; &lt;span class="s2"&gt;"sec-lab-tf"&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;report&lt;/span&gt; &lt;span class="s2"&gt;"$Work\report-terraform.json"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;report-terraform.json&lt;/code&gt; comes back with &lt;code&gt;"before": []&lt;/code&gt; and &lt;code&gt;"after": []&lt;/code&gt;. That makes the scanner a test for the Terraform code.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv5oc6oq8ego5eiw61oq7.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv5oc6oq8ego5eiw61oq7.png" alt="Terraform plan for the secure rebuild" width="800" height="478"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe15cual9sihj4ahtr0g5.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe15cual9sihj4ahtr0g5.png" alt="Reports and policy files: report-drift.json, report-terraform.json, wildcard-policy.json, public-policy.json" width="800" height="501"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does not prove
&lt;/h2&gt;

&lt;p&gt;This part matters more than the green output:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Floci is not AWS.&lt;/strong&gt; I checked behavior against Floci's docs and my own runs, not against real AWS, and it can differ.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Nothing is enforced.&lt;/strong&gt; IAM enforcement and S3 auth are off by default, so the wildcard role does not actually grant anything. A permissions bug would be invisible here.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GuardDuty is management-plane only.&lt;/strong&gt; There are no real threat findings. Every alert in the lab comes from my scanner.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The IAM coverage is narrow.&lt;/strong&gt; Role inline policies and &lt;code&gt;AdministratorAccess&lt;/code&gt; only. No users, groups, customer-managed policies, trust policies or permission boundaries.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Existing objects are not re-encrypted&lt;/strong&gt; by the KMS fix.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Floci is in-memory.&lt;/strong&gt; Restarting it wipes every resource, so you rerun from step 02.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So this is a teaching tool and a rehearsal of the workflow, not a substitute for Prowler, AWS Config or Security Hub. Steps 01 to 08 passed end to end on Windows 11, PowerShell 5.1, AWS CLI 2.39, Terraform 1.13 and Python 3.12.&lt;/p&gt;

&lt;h2&gt;
  
  
  Run it
&lt;/h2&gt;

&lt;p&gt;Needs Docker Desktop, AWS CLI v2, Python 3 and PowerShell 5.1+. Terraform is only needed for step 07.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;cd&lt;/span&gt; &lt;span class="n"&gt;cmd&lt;/span&gt;\&lt;span class="n"&gt;scripts&lt;/span&gt;
&lt;span class="nc"&gt;Set&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;ExecutionPolicy&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Scope&lt;/span&gt; &lt;span class="k"&gt;Process&lt;/span&gt; &lt;span class="nc"&gt;Bypass&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;01&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;start&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;floci&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;02&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;baseline&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;03&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;scan&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;04&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;fix&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;05&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;alerting&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;06&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;drift&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;alert&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;07&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;terraform&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;08&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;cleanup&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;08-cleanup.ps1 -StopFloci&lt;/code&gt; also stops the Floci container this folder started.&lt;/p&gt;

&lt;h2&gt;
  
  
  Next
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Cover IAM users and groups, and &lt;code&gt;Resource: "*"&lt;/code&gt; analysis.&lt;/li&gt;
&lt;li&gt;Replace the IAM delete-only fix with a least-privilege policy derived from access logs.&lt;/li&gt;
&lt;li&gt;Check customer-managed policies and trust policies.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/axololtos/local-cloud-security-lab" rel="noopener noreferrer"&gt;github.com/axololtos/local-cloud-security-lab&lt;/a&gt;. A star helps if this saved you from practicing on a real account, and you can follow me here on DEV for more.&lt;/p&gt;

</description>
      <category>aws</category>
      <category>security</category>
      <category>terraform</category>
      <category>python</category>
    </item>
    <item>
      <title>Run AWS CodePipeline, CodeBuild and CodeDeploy Locally with Floci</title>
      <dc:creator>Vedas Kudalkar</dc:creator>
      <pubDate>Thu, 12 Nov 2026 13:59:50 +0000</pubDate>
      <link>https://dev.to/axololtos_30/run-aws-codepipeline-codebuild-and-codedeploy-locally-with-floci-3k61</link>
      <guid>https://dev.to/axololtos_30/run-aws-codepipeline-codebuild-and-codedeploy-locally-with-floci-3k61</guid>
      <description>&lt;p&gt;&lt;em&gt;A Maven WAR through CodeArtifact, CodeBuild, CodeDeploy and CodePipeline on Floci in Docker. No AWS account, no bill.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;To run an AWS CI/CD pipeline with no AWS account, I pointed the AWS CLI at Floci, a local AWS emulator, and scripted every stage in PowerShell. The pipeline builds a Java web app, deploys it to an "EC2 instance" that is really a Docker container, and serves it on &lt;code&gt;localhost&lt;/code&gt;. Most of it worked as written. CodeDeploy hooks did not, so I wrote a small SSM agent stand-in to run them.&lt;/p&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/axololtos/cicd-pipeline-floci" rel="noopener noreferrer"&gt;axololtos/cicd-pipeline-floci&lt;/a&gt;. The design follows the free NextWork DevOps challenge; the repo is not affiliated with it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why emulate it
&lt;/h2&gt;

&lt;p&gt;The tutorial version needs a real account, IAM setup, a running EC2 instance and careful cleanup. Miss one resource and you pay for it. Floci removes that risk, and the whole thing is repeatable: &lt;code&gt;07-cleanup.ps1&lt;/code&gt; tears it down and the numbered scripts rebuild it.&lt;/p&gt;

&lt;p&gt;The trade-off is fidelity. Floci implements the API surface, not every behavior behind it. Most of this post is about where that gap showed up.&lt;/p&gt;

&lt;h2&gt;
  
  
  Architecture
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5tt0hqwwgbk7p2knidk1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F5tt0hqwwgbk7p2knidk1.png" alt="Architecture" width="799" height="494"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Stage&lt;/th&gt;
&lt;th&gt;Service&lt;/th&gt;
&lt;th&gt;Role&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Source&lt;/td&gt;
&lt;td&gt;GitHub&lt;/td&gt;
&lt;td&gt;Hosts the Maven webapp&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Packages&lt;/td&gt;
&lt;td&gt;CodeArtifact&lt;/td&gt;
&lt;td&gt;Maven repo that &lt;code&gt;mvn deploy&lt;/code&gt; publishes to&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Build&lt;/td&gt;
&lt;td&gt;CodeBuild&lt;/td&gt;
&lt;td&gt;Builds the WAR, uploads it to S3&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Deploy&lt;/td&gt;
&lt;td&gt;CodeDeploy + EC2 + SSM&lt;/td&gt;
&lt;td&gt;Hook scripts fetch the WAR and start Tomcat&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Orchestrate&lt;/td&gt;
&lt;td&gt;CodePipeline&lt;/td&gt;
&lt;td&gt;Chains Source, Build, Deploy&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Stack: Floci in Docker (with the Docker socket mounted, so EC2 instances become containers), PowerShell 5.1+, AWS CLI v2, Docker Desktop, and a Maven 3.5.2 / JDK 8 build image. The scripts live in &lt;code&gt;scripts/&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;01-start-floci.ps1   02-webapp.ps1      03-codeartifact.ps1  04-codebuild.ps1
05-deploy.ps1        06-pipeline.ps1    07-cleanup.ps1       08-screenshots.ps1
env.ps1  ssm-agent.ps1  appspec.yml  compose.yaml  hooks/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Pointing the CLI at Floci
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;env.ps1&lt;/code&gt; holds the only AWS configuration: fake credentials and one endpoint.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="no"&gt;AWS_ENDPOINT_URL&lt;/span&gt;      &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"http://localhost:4566"&lt;/span&gt;
&lt;span class="nv"&gt;$env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="no"&gt;AWS_DEFAULT_REGION&lt;/span&gt;    &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"us-east-1"&lt;/span&gt;
&lt;span class="nv"&gt;$env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="no"&gt;AWS_ACCESS_KEY_ID&lt;/span&gt;     &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"test"&lt;/span&gt;
&lt;span class="nv"&gt;$env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="no"&gt;AWS_SECRET_ACCESS_KEY&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"test"&lt;/span&gt;
&lt;span class="nv"&gt;$env&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="no"&gt;AWS_PAGER&lt;/span&gt;             &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;AWS_ENDPOINT_URL&lt;/code&gt; is the global endpoint override in recent CLI v2 builds, so no command needs &lt;code&gt;--endpoint-url&lt;/code&gt;. Any access key works. &lt;code&gt;aws sts get-caller-identity&lt;/code&gt; returns account &lt;code&gt;000000000000&lt;/code&gt;, which confirms you are talking to Floci. The same file defines &lt;code&gt;$MavenImage = "maven:3.5.2-jdk-8"&lt;/code&gt; and an &lt;code&gt;Mvn&lt;/code&gt; helper that runs Maven in a throwaway container, so the host needs no JDK.&lt;/p&gt;

&lt;p&gt;First-run output: caller identity, the three IAM roles, both S3 buckets, the CodeArtifact repo.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feq99swbia7qe29hhu7qy.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feq99swbia7qe29hhu7qy.png" alt="Floci identity, roles, buckets and CodeArtifact repo" width="800" height="436"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;The same resources in the Floci console:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0u5dxc360kqjtvervvqw.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0u5dxc360kqjtvervvqw.png" alt="Floci console: IAM roles" width="800" height="340"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp2r0nev9kalcirg4uce1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fp2r0nev9kalcirg4uce1.png" alt="Floci console: S3 buckets" width="799" height="293"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Build: CodeArtifact and CodeBuild
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;03-codeartifact.ps1&lt;/code&gt; creates the IAM roles (&lt;code&gt;codebuild-role&lt;/code&gt;, &lt;code&gt;codedeploy-role&lt;/code&gt;, &lt;code&gt;codepipeline-role&lt;/code&gt;), a CodeArtifact domain &lt;code&gt;nextwork&lt;/code&gt; and repository &lt;code&gt;nextwork-devops-cicd&lt;/code&gt;, then runs &lt;code&gt;mvn deploy&lt;/code&gt; from a container. Re-running it prints &lt;code&gt;ConflictException ... already exists&lt;/code&gt;, which is harmless.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fku3srn3n12ienunz5p6e.png" alt="CodeArtifact domain and repo creation, ConflictException on re-run" width="799" height="207"&gt;
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl53eazyrcxjoacbsc03e.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl53eazyrcxjoacbsc03e.png" alt="CodeArtifact domain, repository and Maven endpoint" width="800" height="521"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;code&gt;04-codebuild.ps1&lt;/code&gt; creates two buckets, zips the source with &lt;code&gt;tar.exe&lt;/code&gt; so the zip is Linux-safe, uploads it to &lt;code&gt;s3://nextwork-source/source.zip&lt;/code&gt;, and creates the build project. It polls until &lt;code&gt;buildComplete&lt;/code&gt; is true, then lists the artifact: a 2,291-byte &lt;code&gt;nextwork-web-project.war&lt;/code&gt; in &lt;code&gt;nextwork-artifacts&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  &lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fowfoiaae4bd51ado5aai.png" alt="Buckets, source upload and CodeBuild project" width="767" height="677"&gt;
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpaj6ka3chnljpovkwoqx.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpaj6ka3chnljpovkwoqx.png" alt="Build polled to SUCCEEDED, WAR listed in S3" width="540" height="175"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Maven reported &lt;code&gt;BUILD SUCCESS&lt;/code&gt; in 17.269 s, and the build log group shows up in the console:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi7hknqqtl8aqyl9r5dcc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi7hknqqtl8aqyl9r5dcc.png" alt="Maven BUILD SUCCESS" width="731" height="177"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Floci's IAM does not enforce policies by default, so role ARNs only need to exist. On real AWS, a wrong trust policy fails the build.&lt;/p&gt;

&lt;h2&gt;
  
  
  Deploy: where the emulator gap showed up
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;05-deploy.ps1&lt;/code&gt; creates a key pair and a &lt;code&gt;web-sg&lt;/code&gt; security group (port 8080), then runs &lt;code&gt;aws ec2 run-instances&lt;/code&gt;. Floci starts a container named &lt;code&gt;floci-aws-ec2-&amp;lt;instance-id&amp;gt;&lt;/code&gt;; the script installs Corretto 8, Tomcat 9.0.89 and the AWS CLI inside it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq5ckufcds65udydwtisp.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fq5ckufcds65udydwtisp.png" alt="Key pair, security group on 8080, instance launched as a container" width="799" height="438"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1mtjjadelap9eiyjs3h5.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1mtjjadelap9eiyjs3h5.png" alt="Floci console: nextwork-web instance running" width="800" height="252"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It then registers the instance with SSM, copies &lt;code&gt;scripts/hooks&lt;/code&gt; into the container at &lt;code&gt;/scripts&lt;/code&gt;, and recreates the CodeDeploy app and group.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffjbcg2lw1sjwauc4i04r.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Ffjbcg2lw1sjwauc4i04r.png" alt="Dependencies installed, instance registered with SSM, hooks copied, CodeDeploy app and group created" width="800" height="641"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Problem 1: tag-based targeting finds nothing
&lt;/h3&gt;

&lt;p&gt;A deployment group normally selects instances by EC2 tag. In Floci that lookup fails, so the script registers the instance as an on-premises instance and gives the group no filters:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;aws&lt;/span&gt; &lt;span class="n"&gt;deploy&lt;/span&gt; &lt;span class="n"&gt;create&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;deployment&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;group&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;application&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="n"&gt;nextwork&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;app&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;deployment&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;group&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="n"&gt;nextwork&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;dg&lt;/span&gt; &lt;span class="sb"&gt;`
    --service-role-arn arn:aws:iam::000000000000:role/codedeploy-role
aws deploy register-on-premises-instance --instance-name $id `&lt;/span&gt;
    &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;iam&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;user&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;arn&lt;/span&gt; &lt;span class="n"&gt;arn&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="n"&gt;aws&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="n"&gt;iam&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="mi"&gt;000000000000&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="n"&gt;user&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;devops&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;iam&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Problem 2: nobody runs the hooks
&lt;/h3&gt;

&lt;p&gt;On real AWS the agent on the instance pulls commands and runs the &lt;code&gt;appspec.yml&lt;/code&gt; hooks. Floci queues those commands for an SSM agent, but none exists, and it fails the hook if the command is not acknowledged within about 500 ms.&lt;/p&gt;

&lt;p&gt;So &lt;code&gt;ssm-agent.ps1&lt;/code&gt; is a background job started by &lt;code&gt;05-deploy.ps1&lt;/code&gt;. It polls &lt;code&gt;GetMessages&lt;/code&gt; every 100 ms, acknowledges each message, base64-decodes the payload, runs it with &lt;code&gt;docker exec &amp;lt;container&amp;gt; sh -c&lt;/code&gt;, and sends the result back with &lt;code&gt;SendReply&lt;/code&gt; (status, exit code, output). It must start before the deployment is created, and &lt;code&gt;05&lt;/code&gt; drains stale queued commands first so leftovers from a failed run do not push the real deployment past the ack window.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcuenevbmqqf3bzoyl9zg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcuenevbmqqf3bzoyl9zg.png" alt="Agent log: each hook run through docker exec, exit code 0, Deployment status Succeeded" width="800" height="224"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  The hooks
&lt;/h3&gt;

&lt;p&gt;Floci skips the bundle download and install, so the hook scripts fetch the WAR from S3 themselves. The deployment finished &lt;code&gt;Succeeded&lt;/code&gt; with both hooks exiting 0, as the agent log above shows.&lt;/p&gt;

&lt;p&gt;Floci's port forwarder published the container's 8080 on host port 30000:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F68ykw0rujpqeaupmoi4b.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F68ykw0rujpqeaupmoi4b.png" alt="The deployed page" width="770" height="480"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The pipeline
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;06-pipeline.ps1&lt;/code&gt; takes your GitHub username, writes the definition to &lt;code&gt;pipeline.json&lt;/code&gt;, and creates the pipeline: Source (GitHub, branch &lt;code&gt;main&lt;/code&gt;), Build (&lt;code&gt;nextwork-build&lt;/code&gt;), Deploy (&lt;code&gt;nextwork-app&lt;/code&gt; / &lt;code&gt;nextwork-dg&lt;/code&gt;), with &lt;code&gt;nextwork-artifacts&lt;/code&gt; as the artifact store.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6yajtf2vldo190sfrp0o.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F6yajtf2vldo190sfrp0o.png" alt="pipeline.json: Source stage and artifact store" width="652" height="725"&gt;&lt;/a&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;aws&lt;/span&gt; &lt;span class="n"&gt;codepipeline&lt;/span&gt; &lt;span class="n"&gt;create&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;pipeline&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;cli&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;input&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;json&lt;/span&gt; &lt;span class="s2"&gt;"file://$f"&lt;/span&gt;
&lt;span class="n"&gt;aws&lt;/span&gt; &lt;span class="n"&gt;codepipeline&lt;/span&gt; &lt;span class="n"&gt;start&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;pipeline&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;execution&lt;/span&gt; &lt;span class="o"&gt;--&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="n"&gt;nextwork&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;pipeline&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The first poll shows Build &lt;code&gt;InProgress&lt;/code&gt;, the next shows all three stages &lt;code&gt;Succeeded&lt;/code&gt;:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fh9e7b5g4c7ojzuhow5iq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fh9e7b5g4c7ojzuhow5iq.png" alt="Pipeline execution state and known-gap notes" width="800" height="131"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The full resource check at the end, via the AWS CLI:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw2032nx1f2vjt5ntr9fu.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw2032nx1f2vjt5ntr9fu.png" alt="Build SUCCEEDED, instance running, deployment group, pipeline stages Succeeded" width="800" height="399"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does not prove
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;CodeBuild reads &lt;code&gt;s3://nextwork-source/source.zip&lt;/code&gt;, not the GitHub artifact.&lt;/strong&gt; Floci's CodeBuild accepts only S3 or no source. To ship a change, edit the app and rerun &lt;code&gt;04&lt;/code&gt; and &lt;code&gt;05&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The pipeline's Deploy stage reports success without running hooks.&lt;/strong&gt; The hook path I verified is the direct deployment from &lt;code&gt;05-deploy.ps1&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Floci is in-memory.&lt;/strong&gt; The build script itself warns that artifacts are lost if Floci restarts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CodeArtifact has no upstream resolution&lt;/strong&gt;, so Maven Central serves plugins.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;IAM is not enforced&lt;/strong&gt;, so permission bugs stay invisible.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This is a rehearsal of the pipeline's shape and API calls, not proof that the same definition passes on real AWS.&lt;/p&gt;

&lt;h2&gt;
  
  
  Run it
&lt;/h2&gt;

&lt;p&gt;Needs Docker Desktop, AWS CLI v2, PowerShell 5.1+ and Git. Step 2 needs an empty GitHub repo URL; step 6 needs your GitHub username.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight powershell"&gt;&lt;code&gt;&lt;span class="n"&gt;cd&lt;/span&gt; &lt;span class="n"&gt;scripts&lt;/span&gt;
&lt;span class="nc"&gt;Set&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;ExecutionPolicy&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;Scope&lt;/span&gt; &lt;span class="k"&gt;Process&lt;/span&gt; &lt;span class="nc"&gt;Bypass&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;01&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;start&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;floci&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;02&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;webapp&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;RepoUrl&lt;/span&gt; &lt;span class="n"&gt;https&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="o"&gt;//&lt;/span&gt;&lt;span class="n"&gt;github&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;com&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="no"&gt;YOU&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;nextwork&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;web&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;project&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;git&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;03&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;codeartifact&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;04&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;codebuild&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;05&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;deploy&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;06&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;pipeline&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="nc"&gt;GitHubUser&lt;/span&gt; &lt;span class="no"&gt;YOU&lt;/span&gt;
&lt;span class="p"&gt;.&lt;/span&gt;\&lt;span class="mi"&gt;07&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="n"&gt;cleanup&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;ps1&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;After &lt;code&gt;05&lt;/code&gt;, open &lt;code&gt;http://localhost:&amp;lt;port&amp;gt;/&lt;/code&gt; using the port it prints (30000 in my run).&lt;/p&gt;

&lt;h2&gt;
  
  
  Next
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Feed CodeBuild the pipeline's GitHub source artifact instead of the pre-zipped S3 object.&lt;/li&gt;
&lt;li&gt;Make the Deploy stage run the hooks and prove it with a visible page change.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Repo: &lt;a href="https://github.com/axololtos/cicd-pipeline-floci" rel="noopener noreferrer"&gt;github.com/axololtos/cicd-pipeline-floci&lt;/a&gt;. A star helps if this saved you an AWS bill, and you can follow me here on DEV for more.&lt;/p&gt;

</description>
      <category>aws</category>
      <category>devops</category>
      <category>cicd</category>
      <category>docker</category>
    </item>
    <item>
      <title>Cutting LLM Calls in Incident Triage: Sliding Windows, Log Reduction, and a pgvector Cache</title>
      <dc:creator>Vedas Kudalkar</dc:creator>
      <pubDate>Sun, 01 Nov 2026 17:03:27 +0000</pubDate>
      <link>https://dev.to/axololtos_30/cutting-llm-calls-in-incident-triage-sliding-windows-log-reduction-and-a-pgvector-cache-6hk</link>
      <guid>https://dev.to/axololtos_30/cutting-llm-calls-in-incident-triage-sliding-windows-log-reduction-and-a-pgvector-cache-6hk</guid>
      <description>&lt;p&gt;&lt;em&gt;A Kafka-to-WebSocket pipeline where the model is the last resort, not the first step.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem
&lt;/h2&gt;

&lt;p&gt;The obvious way to add an LLM to log monitoring is to send logs to a model and ask what is wrong. That breaks quickly. Most log lines are not errors. During an outage, the same error repeats thousands of times with only timestamps, UUIDs and counters changing. A raw stack trace with framework frames is mostly noise. And the same database timeout will show up on &lt;code&gt;orders&lt;/code&gt; today and &lt;code&gt;inventory&lt;/code&gt; tomorrow, so you pay for the same diagnosis again.&lt;/p&gt;

&lt;p&gt;I built &lt;a href="https://github.com/axololtos/telemetry-incident-dashboard" rel="noopener noreferrer"&gt;telemetry-incident-dashboard&lt;/a&gt; around one rule: every step before the model must be cheaper than the model, and must be able to stop the pipeline.&lt;/p&gt;

&lt;p&gt;It is a working prototype. I'll say clearly later what has and hasn't been exercised.&lt;/p&gt;

&lt;h2&gt;
  
  
  Architecture
&lt;/h2&gt;



&lt;pre data-lang="mermaid"&gt;&lt;code&gt;flowchart TD
    A[Apps / log shipper] --&amp;gt; K[Kafka topic app-logs]
    K --&amp;gt; C[Spring Boot consumer&amp;lt;br/&amp;gt;virtual threads]
    C --&amp;gt;|every log| W[STOMP /topic/logs]
    C --&amp;gt;|ERROR only| D[Per-service sliding window&amp;lt;br/&amp;gt;10+ errors in 60s]
    D --&amp;gt;|below threshold| X[Stop: no tokens]
    D --&amp;gt;|burst| R[LogPayloadReducer]
    R --&amp;gt; E{Exact fingerprint&amp;lt;br/&amp;gt;in cache?}
    E --&amp;gt;|yes| H[CACHE_EXACT]
    E --&amp;gt;|no| V{pgvector cosine&amp;lt;br/&amp;gt;&amp;gt;= 0.90?}
    V --&amp;gt;|yes| S[CACHE_SEMANTIC]
    V --&amp;gt;|no| L[LLM call via LangChain4j]
    L --&amp;gt; P[(PostgreSQL + pgvector&amp;lt;br/&amp;gt;diagnosis_cache)]
    H --&amp;gt; I[(incidents hypertable)]
    S --&amp;gt; I
    L --&amp;gt; I
    I --&amp;gt; A2[STOMP /topic/alerts]&lt;/code&gt;&lt;/pre&gt;



&lt;p&gt;Stack: Java 21, Spring Boot 3.3, Apache Kafka (KRaft), PostgreSQL with TimescaleDB and pgvector, LangChain4j with OpenAI (&lt;code&gt;gpt-4o-mini&lt;/code&gt; and &lt;code&gt;text-embedding-3-small&lt;/code&gt; by default), and a React + Vite dashboard.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: detect bursts without a model
&lt;/h2&gt;

&lt;p&gt;Each service gets its own &lt;code&gt;ErrorWindow&lt;/code&gt;. It holds the errors from the last 60 seconds, fires when the count reaches the threshold (default 10), and then stays quiet for a cooldown (default 120 seconds).&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight java"&gt;&lt;code&gt;&lt;span class="kd"&gt;synchronized&lt;/span&gt; &lt;span class="nc"&gt;List&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;LogEvent&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="nf"&gt;record&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;LogEvent&lt;/span&gt; &lt;span class="n"&gt;event&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt; &lt;span class="kt"&gt;long&lt;/span&gt; &lt;span class="n"&gt;nowMs&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt; &lt;span class="kt"&gt;long&lt;/span&gt; &lt;span class="n"&gt;windowMs&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt; &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;threshold&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt;
                                   &lt;span class="kt"&gt;long&lt;/span&gt; &lt;span class="n"&gt;cooldownMs&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt; &lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;maxBuffered&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt; &lt;span class="o"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;errors&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;addLast&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nc"&gt;Stamped&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="n"&gt;nowMs&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt; &lt;span class="n"&gt;event&lt;/span&gt;&lt;span class="o"&gt;));&lt;/span&gt;
    &lt;span class="k"&gt;while&lt;/span&gt; &lt;span class="o"&gt;(!&lt;/span&gt;&lt;span class="n"&gt;errors&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;isEmpty&lt;/span&gt;&lt;span class="o"&gt;()&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; &lt;span class="n"&gt;nowMs&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;errors&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;peekFirst&lt;/span&gt;&lt;span class="o"&gt;().&lt;/span&gt;&lt;span class="na"&gt;arrivalMs&lt;/span&gt;&lt;span class="o"&gt;()&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;windowMs&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt; &lt;span class="o"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;errors&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;pollFirst&lt;/span&gt;&lt;span class="o"&gt;();&lt;/span&gt;
    &lt;span class="o"&gt;}&lt;/span&gt;
    &lt;span class="k"&gt;while&lt;/span&gt; &lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="n"&gt;errors&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;size&lt;/span&gt;&lt;span class="o"&gt;()&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;maxBuffered&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt; &lt;span class="o"&gt;{&lt;/span&gt;
        &lt;span class="n"&gt;errors&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;pollFirst&lt;/span&gt;&lt;span class="o"&gt;();&lt;/span&gt;
    &lt;span class="o"&gt;}&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="n"&gt;errors&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;size&lt;/span&gt;&lt;span class="o"&gt;()&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; &lt;span class="n"&gt;threshold&lt;/span&gt; &lt;span class="o"&gt;||&lt;/span&gt; &lt;span class="n"&gt;nowMs&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;lastAlertMs&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; &lt;span class="n"&gt;cooldownMs&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt; &lt;span class="o"&gt;{&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nc"&gt;List&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;of&lt;/span&gt;&lt;span class="o"&gt;();&lt;/span&gt;
    &lt;span class="o"&gt;}&lt;/span&gt;
    &lt;span class="n"&gt;lastAlertMs&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;nowMs&lt;/span&gt;&lt;span class="o"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;errors&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;stream&lt;/span&gt;&lt;span class="o"&gt;().&lt;/span&gt;&lt;span class="na"&gt;map&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="nl"&gt;Stamped:&lt;/span&gt;&lt;span class="o"&gt;:&lt;/span&gt;&lt;span class="n"&gt;event&lt;/span&gt;&lt;span class="o"&gt;).&lt;/span&gt;&lt;span class="na"&gt;toList&lt;/span&gt;&lt;span class="o"&gt;();&lt;/span&gt;
&lt;span class="o"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Info, debug and warning logs never get here. They are counted and streamed to the dashboard, capped at 200 non-error events per second. A malformed Kafka record is counted and dropped. The listener never rethrows, so one bad record can't stall a partition.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv0675gs4sydzxlnx530u.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv0675gs4sydzxlnx530u.png" alt="Code Screenshot - LogAnalysisEngine.resolve" width="799" height="386"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Visual instruction: Capture this exact code section in VS Code using the OneDark-Pro theme. Use a readable font size and crop unnecessary editor UI.&lt;/p&gt;

&lt;p&gt;The cooldown matters. Without it, a long outage would trigger analysis on every incoming error once the window is full.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: shrink the burst
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;LogPayloadReducer&lt;/code&gt; turns a burst into a short context string:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;strips ANSI codes, ISO timestamps, UUIDs and hex addresses&lt;/li&gt;
&lt;li&gt;drops framework frames (&lt;code&gt;java.base/&lt;/code&gt;, &lt;code&gt;jdk.internal.&lt;/code&gt;, Tomcat, Spring AOP and CGLIB, JUnit)&lt;/li&gt;
&lt;li&gt;keeps the top 12 stack lines and notes how many were cut&lt;/li&gt;
&lt;li&gt;groups identical errors by fingerprint and prints them as &lt;code&gt;xN&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;caps the whole thing at 2,000 characters and 5 distinct errors&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The fingerprint is a SHA-256 of the text after volatile parts are normalised. Numbers become &lt;code&gt;&amp;lt;n&amp;gt;&lt;/code&gt;, so &lt;code&gt;Timeout after 3001ms&lt;/code&gt; and &lt;code&gt;Timeout after 9999ms&lt;/code&gt; hash the same:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight java"&gt;&lt;code&gt;&lt;span class="kd"&gt;private&lt;/span&gt; &lt;span class="kd"&gt;static&lt;/span&gt; &lt;span class="nc"&gt;String&lt;/span&gt; &lt;span class="nf"&gt;normalize&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;String&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt; &lt;span class="o"&gt;{&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="no"&gt;NUMBER&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;matcher&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="n"&gt;scrub&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="o"&gt;)).&lt;/span&gt;&lt;span class="na"&gt;replaceAll&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="s"&gt;"&amp;lt;n&amp;gt;"&lt;/span&gt;&lt;span class="o"&gt;);&lt;/span&gt;
&lt;span class="o"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For the 15-error connection-pool burst in &lt;code&gt;sample-data/02-db-timeout-burst.ndjson&lt;/code&gt;, the README reports the model input going from 8,415 characters (about 2,100 tokens) to 506 characters (about 127 tokens). That is one synthetic burst and the token count is a four-characters-per-token estimate, so treat 94% as an illustration, not a benchmark.&lt;/p&gt;

&lt;p&gt;The reduced output looks like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;service=orders errors=15 distinct=1
[1] x15 ERROR HikariPool-1 - Connection is not available, request timed out after 30001ms
java.sql.SQLTransientConnectionException: HikariPool-1 - Connection is not available, request timed out after 30001ms
    at com.zaxxer.hikari.pool.HikariPool.createTimeoutException(HikariPool.java:696)
    at com.zaxxer.hikari.pool.HikariPool.getConnection(HikariPool.java:197)
    at com.shop.orders.Repository.save(Repository.java:48)
    at com.shop.orders.Service.handle(Service.java:71)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Step 3: a two-level cache
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;LogAnalysisEngine.resolve&lt;/code&gt; goes cheapest first.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Exact match.&lt;/strong&gt; One &lt;code&gt;UPDATE ... RETURNING&lt;/code&gt; both bumps the hit counter and fetches the stored diagnosis:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight java"&gt;&lt;code&gt;&lt;span class="nc"&gt;List&lt;/span&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;String&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; &lt;span class="n"&gt;exact&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;jdbc&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;queryForList&lt;/span&gt;&lt;span class="o"&gt;(&lt;/span&gt;
        &lt;span class="s"&gt;"UPDATE diagnosis_cache SET hits = hits + 1 WHERE fingerprint = ? RETURNING diagnosis"&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt;
        &lt;span class="nc"&gt;String&lt;/span&gt;&lt;span class="o"&gt;.&lt;/span&gt;&lt;span class="na"&gt;class&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt; &lt;span class="n"&gt;fingerprint&lt;/span&gt;&lt;span class="o"&gt;);&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Semantic match.&lt;/strong&gt; If there's no exact hit, embed the context and ask pgvector for the nearest row. A cosine similarity of 0.90 or more counts as a hit. This is what lets a database timeout on &lt;code&gt;inventory&lt;/code&gt; reuse the diagnosis made for &lt;code&gt;orders&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight java"&gt;&lt;code&gt;&lt;span class="no"&gt;SELECT&lt;/span&gt; &lt;span class="n"&gt;id&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt; &lt;span class="n"&gt;diagnosis&lt;/span&gt;&lt;span class="o"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="o"&gt;(&lt;/span&gt;&lt;span class="n"&gt;embedding&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;=&amp;gt;&lt;/span&gt; &lt;span class="o"&gt;?::&lt;/span&gt;&lt;span class="n"&gt;vector&lt;/span&gt;&lt;span class="o"&gt;)&lt;/span&gt; &lt;span class="no"&gt;AS&lt;/span&gt; &lt;span class="n"&gt;similarity&lt;/span&gt;
&lt;span class="no"&gt;FROM&lt;/span&gt; &lt;span class="n"&gt;diagnosis_cache&lt;/span&gt;
&lt;span class="no"&gt;WHERE&lt;/span&gt; &lt;span class="n"&gt;embedding&lt;/span&gt; &lt;span class="no"&gt;IS&lt;/span&gt; &lt;span class="no"&gt;NOT&lt;/span&gt; &lt;span class="no"&gt;NULL&lt;/span&gt;
&lt;span class="no"&gt;ORDER&lt;/span&gt; &lt;span class="no"&gt;BY&lt;/span&gt; &lt;span class="n"&gt;embedding&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;=&amp;gt;&lt;/span&gt; &lt;span class="o"&gt;?::&lt;/span&gt;&lt;span class="n"&gt;vector&lt;/span&gt;
&lt;span class="no"&gt;LIMIT&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The table uses an HNSW index with &lt;code&gt;vector_cosine_ops&lt;/code&gt;. The schema is 1536 dimensions to match &lt;code&gt;text-embedding-3-small&lt;/code&gt;. If you change the embedding model, you change &lt;code&gt;docker/init.sql&lt;/code&gt; and &lt;code&gt;EMBEDDING_DIMENSIONS&lt;/code&gt; together. The engine checks the returned vector length and skips the vector cache on a mismatch instead of failing.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;LLM call.&lt;/strong&gt; Only on a miss. The prompt asks for under 150 words in three headings (root cause with confidence, impact, fix) and says not to invent details. The answer and its embedding are written back, so the next occurrence is free.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjkw08uy49okj4a23cfzc.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjkw08uy49okj4a23cfzc.png" alt="Code Screenshot - LogAnalysisEngine.resolve" width="800" height="796"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Visual instruction: Capture this exact code section in VS Code using the OneDark-Pro theme. Use a readable font size and crop unnecessary editor UI.&lt;/p&gt;

&lt;h2&gt;
  
  
  Engineering decisions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Single-flight for identical bursts.&lt;/strong&gt; Two services can hit the same failure at once. &lt;code&gt;diagnoseOnce&lt;/code&gt; keeps a &lt;code&gt;ConcurrentMap&amp;lt;String, CompletableFuture&amp;lt;Diagnosis&amp;gt;&amp;gt;&lt;/code&gt; keyed by fingerprint. The first caller does the work; the rest &lt;code&gt;join()&lt;/code&gt; its future. That avoids paying for duplicate LLM calls in the gap before the first answer lands in the cache.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Never throw from the pipeline.&lt;/strong&gt; If the cache query, the embedding call, the database or the LLM fails, the incident is still recorded with source &lt;code&gt;FALLBACK&lt;/code&gt; and the raw condensed telemetry attached. A flaky dependency degrades the diagnosis, not the stream.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Virtual threads.&lt;/strong&gt; Each Kafka consumer loop and each analysis task runs on a Java 21 virtual thread. Analysis is blocking I/O (HTTP to a model, JDBC), which is the case virtual threads fit. The analysis is also submitted off the consumer thread so a slow model call can't hold up log ingestion.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Timescale for history.&lt;/strong&gt; Cached diagnoses live in &lt;code&gt;diagnosis_cache&lt;/code&gt;. Every incident, including cache hits, goes into an &lt;code&gt;incidents&lt;/code&gt; hypertable with its source, similarity and tokens used, so you can see how often the model is actually needed.&lt;/p&gt;

&lt;h2&gt;
  
  
  Testing
&lt;/h2&gt;

&lt;p&gt;There are two unit test classes, five tests:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;ErrorWindowTest&lt;/code&gt;: fires at the threshold, respects cooldown, and expires old errors from the window.&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;LogPayloadReducerTest&lt;/code&gt;: truncates stacks to 12 lines plus a marker, collapses 200 repeated errors to &lt;code&gt;x200&lt;/code&gt; under the 2,000-character budget, and gives two events with different numbers and UUIDs the same fingerprint.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Nine NDJSON scenarios in &lt;code&gt;sample-data/&lt;/code&gt; cover normal traffic, bursts (DB timeout, NPE, OOM, upstream 502, JWT failures), a similar failure on a second service, malformed lines, and a below-threshold case.&lt;/p&gt;

&lt;h2&gt;
  
  
  Limitations
&lt;/h2&gt;

&lt;p&gt;I'd rather list these than have you find them:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The successful LLM path (real diagnosis written to the cache and then served as a hit) has &lt;strong&gt;not&lt;/strong&gt; been run against a funded OpenAI account. The fallback path, reducer, window logic and the dashboard demo have been run.&lt;/li&gt;
&lt;li&gt;The dashboard's live mode hasn't been tested against the backend.&lt;/li&gt;
&lt;li&gt;Kafka offsets auto-commit, so a crash mid-analysis can lose that burst.&lt;/li&gt;
&lt;li&gt;No auth on the WebSocket endpoint. No cache eviction. Single Kafka broker.&lt;/li&gt;
&lt;li&gt;No throughput or latency benchmarks.&lt;/li&gt;
&lt;/ul&gt;

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



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cp&lt;/span&gt; .env.example .env            &lt;span class="c"&gt;# optionally set OPENAI_API_KEY&lt;/span&gt;
docker compose up &lt;span class="nt"&gt;-d&lt;/span&gt;            &lt;span class="c"&gt;# Kafka (KRaft) + TimescaleDB with pgvector&lt;/span&gt;
&lt;span class="nb"&gt;set&lt;/span&gt; &lt;span class="nt"&gt;-a&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="nb"&gt;source&lt;/span&gt; .env&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="nb"&gt;set&lt;/span&gt; +a
mvn spring-boot:run             &lt;span class="c"&gt;# http://localhost:8080, STOMP at /ws&lt;/span&gt;

&lt;span class="nb"&gt;cd &lt;/span&gt;dashboard &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; npm &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt; npm run dev   &lt;span class="c"&gt;# http://localhost:5173&lt;/span&gt;

scripts/send-sample-logs.sh sample-data/02-db-timeout-burst.ndjson
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Without an API key the app still starts, and bursts are stored as &lt;code&gt;FALLBACK&lt;/code&gt;. There is also a &lt;a href="https://telemetry-dashboard-mu-wheat.vercel.app" rel="noopener noreferrer"&gt;browser-only demo&lt;/a&gt; that simulates the same rules with hand-written diagnoses and is labeled as a simulation. Click "Play the story" to see an LLM call, a below-threshold burst, a similar-error hit and an exact hit.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next
&lt;/h2&gt;

&lt;p&gt;Not implemented yet, but the obvious gaps: manual offset commits after analysis, cache eviction, authentication on the WebSocket, and a real run of the LLM path with measured cache hit rates.&lt;/p&gt;




&lt;p&gt;Code is on GitHub: &lt;strong&gt;&lt;a href="https://github.com/axololtos/telemetry-incident-dashboard" rel="noopener noreferrer"&gt;axololtos/telemetry-incident-dashboard&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If it's useful, a star helps. Issues and PRs are welcome (there's a CONTRIBUTING guide). Follow me here on DEV for more write-ups like this.&lt;/p&gt;

</description>
      <category>java</category>
      <category>kafka</category>
      <category>postgres</category>
      <category>ai</category>
    </item>
    <item>
      <title>Ofrenda: a keeper for stories that runs entirely on your laptop</title>
      <dc:creator>Vedas Kudalkar</dc:creator>
      <pubDate>Sat, 31 Oct 2026 06:56:16 +0000</pubDate>
      <link>https://dev.to/axololtos_30/ofrenda-a-keeper-for-stories-that-runs-entirely-on-your-laptop-4lee</link>
      <guid>https://dev.to/axololtos_30/ofrenda-a-keeper-for-stories-that-runs-entirely-on-your-laptop-4lee</guid>
      <description>&lt;p&gt;&lt;em&gt;This is a submission for the &lt;a href="https://dev.to/challenges/hacktoberfest-week4-2026-10-26"&gt;Hacktoberfest Open-Source AI Challenge Week 4: Ghost in the Machine&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;p&gt;Ofrenda is a command-line tool. You give it a story about someone, and it keeps it. Later you ask a question and it answers from what you told it, and from nothing else.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight console"&gt;&lt;code&gt;&lt;span class="gp"&gt;$&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;python ofrenda.py remember &lt;span class="s2"&gt;"Abuela"&lt;/span&gt; &lt;span class="s2"&gt;"She burned the first tortilla on purpose, for the house. She sang boleros while washing dishes, always the same one, Sabor a Mi. On Sundays she made caldo de res and nobody was allowed to start eating before she sat down."&lt;/span&gt;
&lt;span class="go"&gt;Lit 4 candle(s) for Abuela.

&lt;/span&gt;&lt;span class="gp"&gt;$&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;python ofrenda.py ask &lt;span class="s2"&gt;"Abuela"&lt;/span&gt; &lt;span class="s2"&gt;"What did she cook on Sundays?"&lt;/span&gt;
&lt;span class="go"&gt;On Sundays, she made caldo de res.

&lt;/span&gt;&lt;span class="gp"&gt;$&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;python ofrenda.py ask &lt;span class="s2"&gt;"Abuela"&lt;/span&gt; &lt;span class="s2"&gt;"Where was she born?"&lt;/span&gt;
&lt;span class="go"&gt;The ofrenda does not hold that memory yet. Would you like to add it?
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That last answer is the one I care about. The story never said where she was born, so the tool says it doesn't know. It doesn't guess.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I read the theme
&lt;/h2&gt;

&lt;p&gt;An ofrenda is the altar families build for the dead: photos, marigolds, a favorite dish, a song. The point is that someone is remembered in specific detail. A ghost in a machine sounded to me like the opposite risk. A chatbot that speaks as your grandmother is eerie, and it will say things she never said.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhj3e7yguk7iosu3avxqp.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhj3e7yguk7iosu3avxqp.png" alt="keeper’s system prompt and ask() wrapped in Sentry agent and tool spans" width="800" height="473"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;So the assistant here is called the keeper, and the rule is written into its system prompt: it reads memories aloud, it never speaks as the person, and if the memories don't cover the question it says so.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

&lt;p&gt;A story goes through a short pipeline:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Gemma splits the story into separate memories, returned as JSON.&lt;/li&gt;
&lt;li&gt;Each memory is embedded and stored in a local SQLite file.&lt;/li&gt;
&lt;li&gt;When you ask something, the question is embedded, the closest memories for that person are retrieved, and Gemma answers from those only.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;One story above became four stored memories:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;- She burned the first tortilla on purpose for the house.            ["cooking"]
- She sang boleros while washing dishes, always singing Sabor a Mi.  ["song"]
- On Sundays, she made caldo de res.                                 ["food"]
- Nobody was allowed to start eating before she sat down.            ["ritual"]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Search is a plain cosine-similarity scan filtered by person. That is enough for a family's worth of stories, and it means one person's memories can't leak into another's answers.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnlrvg6awijdxe51kw9da.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnlrvg6awijdxe51kw9da.png" alt="The memory search function: filtered by person, ranked by cosine similarity" width="800" height="129"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The three pieces I used
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Gemma, through Ollama.&lt;/strong&gt; Both the splitting and the answering run on a local Gemma model. For my demo run I used &lt;code&gt;gemma4:e2b&lt;/code&gt;, and the default in the repo is &lt;code&gt;gemma3:4b&lt;/code&gt;. Any tag Ollama can serve works. Embeddings come from &lt;code&gt;nomic-embed-text&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwschvv6qdivb22ow0725.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwschvv6qdivb22ow0725.png" alt="llm.chat(), one local Gemma call traced with model name and token counts" width="800" height="444"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Temporal.&lt;/strong&gt; Saving a story is two steps that depend on a local model, and local models are slow to load and sometimes fail. I wrapped the steps in a Temporal workflow with a retry policy. On my first real run, Ollama returned an HTTP 500 while the model was still loading. Temporal retried the step, and the command finished with all four memories saved. Without the workflow I would have lost the story and seen a stack trace. The activity also falls back to storing the original text as one memory if Gemma returns invalid JSON, so a bad parse can't drop a story.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxqoa7o4vmmicpinw7yex.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxqoa7o4vmmicpinw7yex.png" alt="Gemma extraction with the never-lose-the-story fallback, and the retrying workflow" width="800" height="585"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sentry Agent Tracing.&lt;/strong&gt; Every &lt;code&gt;ask&lt;/code&gt; is traced with Sentry's AI span names: an agent span for the keeper, a tool span for the memory lookup, and chat and embedding spans with model name and token counts. Tracing only turns on if you set a &lt;code&gt;SENTRY_DSN&lt;/code&gt;. One decision here mattered to me: prompts and answers are not attached to traces unless you set &lt;code&gt;OFRENDA_TRACE_CONTENT=1&lt;/code&gt;. Family stories shouldn't end up in a monitoring dashboard by accident.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why open models matter for this
&lt;/h2&gt;

&lt;p&gt;Stories about someone who died are about as private as data gets. With this setup the model, the embeddings and the database all live on your machine. It works with the internet off. The memories are one &lt;code&gt;.db&lt;/code&gt; file you own, so there's no service that can change its pricing or shut down and take them with it. I couldn't build this on a hosted API and feel good about it, and that is the real reason I used open models, not cost.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it doesn't do
&lt;/h2&gt;

&lt;p&gt;It's text only, with no audio recording or transcription. The database isn't encrypted. A small local model can still misread a story, so it's worth checking that what was stored matches what you meant. Search is a linear scan, which is fine for a family and wrong for a million memories.&lt;/p&gt;

&lt;h2&gt;
  
  
  Demo
&lt;/h2&gt;

&lt;p&gt;Live demo (recorded session): &lt;a href="https://axololtos.github.io/ofrenda/" rel="noopener noreferrer"&gt;axololtos/ofrenda_demo&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Ofrenda runs on a local model through Ollama, so it can't be hosted as a live app without sending people's stories to a server, which is the thing I built it to avoid. That page is a preview: a replay of a real run from my laptop, with the same commands and the same output. To use the real thing, run it locally with the steps below.&lt;/p&gt;

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

&lt;p&gt;Code and setup steps are here: &lt;a href="https://github.com/axololtos/ofrenda" rel="noopener noreferrer"&gt;github.com/axololtos/ofrenda&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You need Python, Ollama and the Temporal dev server. The README has the exact commands.&lt;/p&gt;

&lt;p&gt;Prize categories: Best Use of Gemma, Best Use of Temporal, Best Use of Sentry Agent Tracing.&lt;/p&gt;

</description>
      <category>hf26challenge</category>
      <category>ai</category>
      <category>hacktoberfest</category>
      <category>devchallenge</category>
    </item>
  </channel>
</rss>
