<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Acm on ferkakta.dev</title><link>https://ferkakta.dev/tags/acm/</link><description>Recent content in Acm on ferkakta.dev</description><generator>Hugo</generator><language>en-US</language><copyright>Copyright fizz.</copyright><lastBuildDate>Mon, 09 Feb 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://ferkakta.dev/tags/acm/index.xml" rel="self" type="application/rss+xml"/><item><title>Your ACM certificate request is a beacon — scanners are watching Certificate Transparency logs</title><link>https://ferkakta.dev/acm-certificate-transparency-scanners/</link><pubDate>Mon, 09 Feb 2026 09:00:00 -0600</pubDate><guid>https://ferkakta.dev/acm-certificate-transparency-scanners/</guid><description>&lt;p&gt;I accidentally exposed production secrets on a public endpoint. Here&amp;rsquo;s what happened and what I learned about Certificate Transparency.&lt;/p&gt;
&lt;h2 id="the-setup"&gt;The setup&lt;/h2&gt;
&lt;p&gt;We&amp;rsquo;re building a multi-tenant SaaS platform on EKS. During development, our Terraform module defaulted to &lt;code&gt;ealen/echo-server&lt;/code&gt; for three microservices — a lightweight HTTP server that echoes back request info. Seemed harmless.&lt;/p&gt;
&lt;p&gt;What I missed: echo-server echoes EVERYTHING. Every environment variable in the container, including ones injected from AWS SSM via External Secrets Operator. Database connection strings. Redis auth tokens. OAuth client secrets. Signing keys. A single unauthenticated &lt;code&gt;GET /&lt;/code&gt; returns it all as JSON.&lt;/p&gt;</description></item></channel></rss>