Werner Vogels

CTO @ Amazon

[Werner Vogels @Werner]

In 2004, I picked @SwamiSivasubram as my intern. It was probably one of the best decisions I have made as Amazon's CTO. He learned early that you can only test a system properly in a high-fidelity copy of the environment it will actually run in. AWS Emulator, launched today and written and tested entirely by agents, gives you that kind of environment for more than 200 AWS services. Read Swami's guest post on what the engineer's job becomes when agents write the code: https://t.co/yv8zVjkQnE

[Marc Brooker @MarcJBrooker]

From $0.022 to $0.0005 per ticket classified, with Strands decider.
https://t.co/cOfL8ivh6r

[Werner Vogels @Werner]

Using AWS WAF to apply mitigations for PHP2Shell RCE vulnerabilities (CVE-2026-109618 and CVE-2026-109619) https://t.co/TW2zDAFV6K

[Werner Vogels @Werner]

The hardest part of AWS was always the first hour. Not anymore.

[AWS Developers @awsdevelopers]

AWS just got a lot easier to use.

[Werner Vogels @Werner]

I wrote about invisible engineering for @ComputerWeekly 's 60th anniversary.

https://t.co/CwWdUyH9sa

[Werner Vogels @Werner]

@DHH and I may have some fundamental technical differences, but the work he is doing on https://t.co/YAxPWDki2B is excellent. Happy to be a patron

[Werner Vogels @Werner]

Mandatory reading!

[Clare Liguori @clare_liguori]

I just published a manifesto for all the developers out there who use an AI coding tool, but feel like they're not shipping much faster

I wrote 10 principles for changing how you build software with AI, based on what I've seen work for teams across Amazon
https://t.co/smq7Rt5QkZ

[Werner Vogels @Werner]

Since launch I've been spending time with Kiro Crew, and its memory system is what holds my attention. What it keeps, what it compresses, what it lets go. Our engineers started from pure engineering constraints and landed where evolution did long ago: the brain. https://t.co/IfYTq13ZRt

[Swami Sivasubramanian @SwamiSivasubram]

Today we're launching one of the most exciting ground up innovations in the agent landscape: Kiro Crew! What started as a side project inside @amazon (known as Meshclaw) grew into something tens of thousands of builders across the company relied on daily. It's now open source for everyone.

@kirodotdev Crew is a persistent, self-evolving workspace that keeps work moving, online or off. It's built for engineering work that goes beyond a single chat session, and spans repos, tools, and days. Kiro Crew remembers your project context and history across sessions, turns your corrections into durable lessons and reusable skills, and keeps recurring jobs running on schedules you set. Devs can run several efforts in parallel or hand work to subagents that report back, so nothing waits in line.

Hundreds of contributors shared feedback with us, helping make this launch possible. See how you can build your crew: https://t.co/YCZTTXZLAA

[Matt Garman @mattsgarman]

Honored to be named to @TIME's 2026 TIME100 AI list. This one belongs to our customers and the teams at @awscloud. Still early.

[Werner Vogels @Werner]

There are mashups that are kind of OK. And then there the one's beyond anything. Please turn up your headphones to High. https://t.co/KUmwz6UhZY

[Werner Vogels @Werner]

Zak van der Merwe has spent 14 years building control planes at AWS. His blog is a candid look at what happens when your bookkeeping layer has to keep up with the scale of the cloud, and why some of the most interesting problems in distributed systems often hide in the most "boring" parts. https://t.co/VIs0r6BDed

[Werner Vogels @Werner]

A excellent conversation with @clare_liguori. She really is in the trenches on developers support for Agents and on Kiro.

[Clare Liguori @clare_liguori]

I sat down with Thomas Betts on the @InfoQ podcast to talk about what it takes to go from demo to production agent:
- why more if statements make your agent worse
- how to achieve high accuracy and low cost with small models and just-in-time guidance
- what observability means when every hop is inside the agent
https://t.co/aRStZ6cVgo

[Werner Vogels @Werner]

@ChiefScientist @Cloudflare @GoDaddy @iwantmyname @hover @gandi_net @RegeryServices @awscloud Noted.

[Werner Vogels @Werner]

@mndoci Not to forget Gullit & Rijkaard

[Werner Vogels @Werner]

If only I was looking for another job...

[Karun Singh @karun1710]

We're hiring a Research Engineer at @Arsenal ⚽🔴⚪ to work directly with our Men's First Team!

We're building state-of-the-art AI models for the football domain. This role will focus on building the application layer for our research to advance coaching and analysis workflows.

[Werner Vogels @Werner]

Absolutely worth a read if you are into modern, large-scale, systems design: Aurora DSQL: Scalable, Multi-Region OLTP

[Marc Brooker @MarcJBrooker]

Check out the paper here: https://t.co/ImZeFdS7lr
And my blog post about it here: https://t.co/VcGXxM0wjM

[Werner Vogels @Werner]

I am not a big fan of doing this client-side, for a whole slew of reasons, but this is impressive engineering by the @Zalando team. I like the "lessons learned" they conclude with. https://t.co/5kZkLsT2ro

[Werner Vogels @Werner]

Two-pizza culture was never about feeding hungry engineers. It was about ownership, speed, and not being bogged down by bureaucracy. Working backwards from the customer and putting pen to paper have always been our way of forcing clarity of thought. But the industry is changing, and it’s time to reconsider how we bring products to live. Read more: https://t.co/TIfpLLWRNQ

[Werner Vogels @Werner]

It was a disgrace. Morocco deserved to win, as the Dutch played not to lose. With a depleted midfield, there was no feeding of the forwards. If you have 9 Premier League players in the starting 11 you would expect they could handle a physical playing opponent better. No guts, no glory...

[11tegen11 @11tegen11]

It was really really bad.

[Amazon Web Services @awscloud]

20 years ago, Dr. Werner Vogels almost hung up on Amazon.

"It's just a bookstore. How hard can it be?"

He went anyway. And realized AWS engineers were solving—in *production*—problems academia was still debating on whiteboards.

That culture never changed. 🧵

A hypervisor bottleneck? Gone.

Time sync in distributed systems? A problem the field said was unsolvable. Now it's invisible infrastructure millions rely on.

Today? AI. How do you build trust into an agent that actually does what you expect?

The hardest problems are always the ones no one sees being solved.

Read more stories from Dr. Vogels: https://t.co/sYkFPx3qij