<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Building AWS in Public on Samuel Tillman</title><link>https://samueltillman.com/series/building-aws-in-public/</link><description>Recent content in Building AWS in Public on Samuel Tillman</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 20 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://samueltillman.com/series/building-aws-in-public/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an AWS Multi-Account EKS Platform in Public</title><link>https://samueltillman.com/posts/refplatform/building-an-aws-eks-platform-in-public/</link><pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate><guid>https://samueltillman.com/posts/refplatform/building-an-aws-eks-platform-in-public/</guid><description>&lt;p>Most public AWS examples are fragments. One account, one purpose, and, if you read closely, a quiet dependency on a stored credential or some prerequisite a human built by hand and never wrote down. They teach you the shape of a resource, not the shape of a system.&lt;/p>
&lt;p>I wanted the other thing. So I&amp;rsquo;ve been building a complete AWS organization in the open: multiple accounts, an internal developer platform on Kubernetes, and a realistic demo workload, a fictional fishing-charter booking SaaS, because &amp;ldquo;hello world&amp;rdquo; doesn&amp;rsquo;t have a database, a queue, and async jobs. It&amp;rsquo;s MIT-licensed, it lives on GitHub, and the whole point is that you can fork it, set your variables, and stand up your own.&lt;/p></description></item></channel></rss>