<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AWS Spot on The road</title><link>https://kane.mx/tags/aws-spot/</link><description>Recent content in AWS Spot on The road</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 08 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kane.mx/tags/aws-spot/index.xml" rel="self" type="application/rss+xml"/><item><title>Self-Hosted GitHub Runners on AWS Spot for AI Dev Teams</title><link>https://kane.mx/posts/2026/self-hosted-github-runners-aws-spot/</link><pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate><guid>https://kane.mx/posts/2026/self-hosted-github-runners-aws-spot/</guid><description>
&lt;p>&lt;a href="https://kane.mx/posts/2026/autonomous-dev-team-openclaw/">Autonomous AI dev teams&lt;/a> move the bottleneck. When a dispatcher fans out work to dev and review agents every 5 minutes, the constraint is no longer human attention — it is the &lt;strong>CI/CD pipeline that gates every PR&lt;/strong>. Each agent push triggers builds, tests, E2E verification, and bot reviews. With even a small team of agents iterating in parallel, GitHub Actions minutes become the dominant operational cost.&lt;/p>
&lt;p>Hosted runners are convenient, but they are billed per-minute and capped at 2 cores on the standard tier. For a team of agents that pushes dozens of times an hour and runs container builds + Playwright suites, the math stops working. The lever is &lt;strong>self-hosted runners on AWS spot EC2&lt;/strong> — bigger instances, multi-architecture, scaling to zero when idle.&lt;/p>
&lt;p>&lt;a href="https://kane.mx/posts/2026/self-hosted-github-runners-aws-spot/">Read More&lt;/a>&lt;/p></description></item></channel></rss>