Lambda can have its place in some architectures. I am not a fan of them in general, I've seen enough giant webs of lambdas that become impossible to truly understand the full architecture as they are split across 100 repos, just a web of slop lambdas. This feels like a canary in a coal mine, if you need this, you really need to start migrating to a standalone service on a machine instead of a lambda, where you are using it wrong.
I agree they can get bad but it's so nice to be able to take event driven workflows, like "pick up this file just written to S3, do some stuff to it, and write results out somewhere", and just have it work with basic features like autoretry, DLQs, built-in logging, etc.
Stringing together a bunch is an anti-pattern IMO but when it's not being abused, it's wonderful tech.