Also, I've witnessed people editing Lambda code through the console instead of doing a real deploy. what a mess...
As far as flexibility, while there have been third party libraries that let you deploy your standard Node/Express, .Net/ASP, Python/Flask app to Lambda, now there is an official first party solution
https://github.com/awslabs/aws-lambda-web-adapter
And as far as ECS, it is stupid simple
I’ve used this for years
https://github.com/1Strategy/fargate-cloudformation-example/...
Yeah, exactly that's what I am talking about. Utter nightmare to recover from, especially if whoever set it up thought they needed to follow some uber-complex AWS blog post with >10 involved AWS services and didn't document any of it.
https://aws.amazon.com/blogs/containers/introducing-aws-app-...
Google has something similar.
Like what, Lambda? I've seen so much horrible hacks and shit done with it (and other AWS services cough API gateway cough), these days I rather prefer a set of Kubernetes descriptors and Dockerfiles.
At least that combination all but enforces people doing Infrastructure-as-a-code and there's (almost) no possibility at all for "had to do live hack XYZ in the console and forgot to document it or apply it back in Terraform" .