In May 2026, open‑source veteran Tarus Balog posted a farewell note after four years on AWS’s Open Source Strategy team. He had escalated a Severity‑2 ticket in August 2025 that forced the CEO to intervene and restore a Moroccan developer’s ten‑year‑old account. The employee who rescued a customer’s data became the company’s newest casualty and his story resonated across the developer community.

The timeline shows a pattern. After Balog’s escalation, AWS launched a “Correction of Error” process, yet two layoff waves in October 2025 and January 2026 stripped his team. By May, senior leadership dismissed him despite the CEO’s earlier attention. Meanwhile, AWS blamed human error for three high‑profile AI mishaps that caused data loss and a six‑million‑order outage. These incidents highlight systemic resistance to accountability.

Balog’s firing underscores a contradiction: AWS touts open‑source credibility while treating its champions as expendable. His blog noted that AI‑generated content now eclipses human judgment, a shift that marginalizes the very empathy that saved a customer. Open‑source advocates hear this: without protectors, cloud betrays users.