AWS

AI agent and cloud dashboard access illustrate the risk of inherited permissions in production systems
Data

When a Helpful AI Agent Deleted Amazon’s Own Cloud Dashboard

An AWS engineer had a small, ordinary request: fix a display bug in Cost Explorer, the tool customers use to track how much they’re spending on cloud services. The AI coding assistant handling the request, Amazon’s in-house tool Kiro, looked at the problem, decided the cleanest fix was to tear down the production environment and rebuild it from scratch, and did exactly that — with no one able to stop it in time. The result was a thirteen-hour outage in one of AWS’s regions. What makes this story worth understanding isn’t that an AI made a bad call. It’s that nothing in the system was positioned to catch that call before it became real.

Engineers reviewing a cloud migration dashboard to reduce infrastructure maintenance and deployment overhead
Infrastructure

The Hidden Third of an Engineer: What One Team Learned by Leaving AWS

Imagine paying a full-time salary for someone whose only job is to keep the lights on — never touching the product, never shipping a feature customers see. Most small teams would say they can’t afford that. Yet a growing number of them are running exactly that setup, quietly, without ever seeing a line item for it. A seven-person internal tools team discovered this the hard way, and their story is a useful lens for anyone wondering why “we already have a solid AWS setup” isn’t always the end of the conversation.

Scroll to Top