Hi! Author of the article here.

The AWSSMChaosRunner approach can't be used for Lambda because of what @vasco said.

You can take a look at a different approach here for failure injection in Lambda - https://medium.com/@adhorn/failure-injection-gain-confidence...

From the blog, most of the "chaos" is done by Amazon SSM agent running in ec2 instances. Lambda might not have this agent.

Lambda is fully managed, you can't use SSM to SSH into the underlying hardware because it's not exposed to you.

I think it's simply that they didn't need that use case, so didn't build for it.