Amazon’s powerful new AWS CEO faces his first public crisis — and it’s revealing cracks not just in the cloud, but in corporate accountability.
When Amazon Web Services (AWS) faltered this week, the internet shuddered. From Snapchat to Zoom, Roblox to banking platforms like Halifax and Lloyds — millions were reminded that their “cloud” isn’t as untouchable as they thought. But amid the digital chaos, one question rose louder than the outage alerts: Who’s actually in charge when the cloud collapses? Enter Matt Garman, the relatively new CEO of AWS.
The Man Behind the Cloud
Matt Garman took over as CEO of AWS in June 2024 — a quiet succession that didn’t make global headlines then, but now suddenly matters. He’s no outsider parachuted in from Silicon Valley’s carousel of execs. Garman has been with Amazon since 2006, helping launch AWS’s earliest services. On paper, he’s the perfect insider: engineer, product manager, strategist. But here’s the irony — the man who helped build the cloud is now watching it stumble under its own weight.
It’s not just about restoring services; it’s about restoring confidence. When Garman says AWS is “working toward complete resolution,” it sounds rehearsed — because in the age of digital dependency, apologies no longer calm the storm. Should a CEO’s job be about explaining outages, or preventing them altogether?
A Salary Smaller Than the Storm
Reports suggest Garman earns around $358,750 — a number that might sound high until you realize AWS controls a trillion-dollar ecosystem. For context, that’s less than many tech VPs in far smaller firms. Does a modest paycheck make him more relatable, or does it subtly shield Amazon from scrutiny when things go wrong? If you underpay the captain of the ship, who do you blame when it hits the iceberg — the captain or the corporation?
Garman’s leadership style has been described as collaborative and deeply technical, but AWS’s scale has outgrown even the most hands-on executive. No one person truly “controls” it anymore. That’s the quiet truth behind every outage headline — when the cloud fails, accountability evaporates faster than data.
The Invisible Empire of AWS
AWS isn’t just a service provider; it’s the invisible infrastructure of modern life. Your bank, your game, your favorite app — all rely on it. And that’s precisely what makes outages like this so terrifying. We’ve built a world where a single company’s technical hiccup can silence entire industries. Is that innovation or dependence disguised as progress?
While customers panic over broken streaks or frozen transactions, the larger question is rarely asked: should one corporation — no matter how efficient — hold this much power over the internet’s nervous system?
The Cloud Illusion: Reliability or Monopoly?
AWS sells reliability as its brand. “World-class performance,” “seamless uptime,” “scalable architecture” — these phrases fill marketing pages. But every outage chips away at that illusion. Maybe the real risk isn’t technical failure but concentration of control. As more startups, governments, and global banks move onto AWS, every crash becomes less of an inconvenience and more of a geopolitical event.
Garman may not be responsible for the architecture’s flaws, but he’s now the public face of its vulnerability. And that’s the paradox of modern leadership — when systems run smoothly, no one notices; when they fail, everyone suddenly remembers your name.
The Uncomfortable Future of the Internet
Matt Garman’s appointment symbolized continuity — a loyal insider carrying Jeff Bezos’ and Andy Jassy’s vision forward. Yet his first major crisis has revealed how brittle that vision has become. The cloud, once a metaphor for infinite possibility, now feels more like a single point of failure.
So maybe the real question isn’t what Matt Garman earns — it’s what the rest of us are paying for. Are we buying convenience, or selling control? And if the next AWS outage lasts longer, what happens to the digital world built entirely on trust — and silence — in a system that’s never truly ours?