<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws on Project Wintermute</title><link>https://wintermutecore.com/tags/aws/</link><description>Recent content in Aws 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/aws/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><item><title>Services</title><link>https://wintermutecore.com/services/</link><pubDate>Sun, 13 Feb 2022 11:11:11 -0100</pubDate><guid>https://wintermutecore.com/services/</guid><description>&lt;p&gt;&lt;p style="text-align:center;"&gt;
 &lt;img src="https://wintermutecore.com/services.jpg" alt="Services" /&gt;
&lt;/p&gt;
&lt;/p&gt;
&lt;p&gt;Below is what we actually do day to day. We try to keep the list short and the descriptions honest. If something here matches what you need, get in touch.&lt;/p&gt;

&lt;h2 id="software-engineering" class="anchor-link"&gt;&lt;a href="#software-engineering"&gt;Software engineering&lt;span class="pilcrow"&gt;&amp;nbsp;¶&lt;/span&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;We write backend services in Java, Kotlin, Go, and Groovy. Most of the work falls into a few buckets: REST and gRPC APIs, distributed systems handling high request volumes, and the occasional batch job that has to be reliable more than fast.&lt;/p&gt;</description></item></channel></rss>