<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ephemeral Environments on Project Wintermute</title><link>https://wintermutecore.com/tags/ephemeral-environments/</link><description>Recent content in Ephemeral Environments on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Apr 2026 11:00:00 +0200</lastBuildDate><atom:link href="https://wintermutecore.com/tags/ephemeral-environments/index.xml" rel="self" type="application/rss+xml"/><item><title>Tag-based AWS resource cleanup: patterns that actually scale</title><link>https://wintermutecore.com/posts/aws-tag-based-resource-cleanup/</link><pubDate>Fri, 03 Apr 2026 11:00:00 +0200</pubDate><guid>https://wintermutecore.com/posts/aws-tag-based-resource-cleanup/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR.&lt;/strong&gt; Name and time filters are not enough for safe AWS bulk cleanup. Use tags as the primary signal, expect &lt;code&gt;ListTagsForResource&lt;/code&gt; to be your bottleneck, enforce tagging at provisioning time, and run an audit job that flags untagged resources so the policy stays honest.&lt;/p&gt;
&lt;p&gt;The &amp;ldquo;delete a lot of AWS resources at once&amp;rdquo; problem shows up in every account: CI sandboxes, expired test estates, dev environments forgotten about, ad-hoc reproductions left behind. Bulk cleanup tools that target this exist and work well. Used carelessly any of them is a footgun. Used carefully with tag filtering, they become one of the most useful pieces of cost discipline you can ship.&lt;/p&gt;</description></item></channel></rss>