Why would it? AWS was doing Chaos Engineering long before it was even called Chaos Engineering and well before Chaos Monkey at Netflix. Most historical coverings of Chaos Engineering trace back to Jesse Robbins at AWS pulling power cables from racks to simulate failure and running GameDays in the early 2000s.

See: https://en.wikipedia.org/wiki/Jesse_Robbins#Contributions_to... https://medium.com/the-cloud-architect/chaos-engineering-ab0...

People have been doing Chaos Engineering, and the more general category of "DevOps", for years before those things were given labels. I think we may credit Netflix with the awesome name of Chaos Monkey and for building a systemic in-house practice, but they were not the first to perform intentional destructive resilience testing in production.

Case in point, I've been yanking out active drives, cables, PSUs and CPUs since the 1980s, and not always by accident.

What's more, I was taught to do by someone who'd been babysitting VAXes for years; they had a ceramic axe that, at the age of fourteen, I'd seen them swing right through a three-phase minicomputer power feed at my local university's data center "for test purposes".

One of the more memorable projects in my career had me sticking pens in fans for months on end, because it tickled an error-handling edge case.

Chaos Monkey was explained to me as "The (virtual) monkey swinging around the (virtual) data center unplugging the (virtual) cables". It very well could have been based on Robbins. The point wasn't originality - the point was to have the same benefit in our burgeoning cloud environment.

In the 80s we had a serial line in our test lab set up with a chain of paperclips on the TX and RX lines.

Made it easy to insert comms errors and failures.

Not saying you're wrong, but maybe Wikipedia is leaving off a lot of relevant history on the Chaos Engineering article then.

Edit: Funny how my original comment is downvoted for contradictory reasons, both because "obviously that was irrelevant to the state of the art in chaos engineering", and because "oh don't worry, that's relevant, they just discuss it in other contexts".

I think your comment was downvoted because it's a silly thing to focus on.

> but maybe Wikipedia is leaving off a lot of relevant history on the Chaos Engineering article then.

This is certainly true.

However the very first sentence is "AWS Fault Injection Simulator is a fully managed chaos engineering service".

I know -- still no mention of the state of the art or what product it might replace.

In Dr Vogel's keynote presentation he brought up Netflix and Chaos Monkey specifically as precursors to this service.

It would be better if that context carried over to this document.

That would be superfluous to the content in which most people would refer to that document for. Amazon already state it’s for Chaos Engineering, they don’t need to list other similar projects on their own product page.