I made the OSS https://github.com/rynop/aws-blueprint partially to address this problem. Easily migrate from Lambda to ECS (remove lambda lock-in). It abstracts all the difficult & time consuming to learn aws idiosyncrasies in to a best-practice production ready harness.
You could argue that if you have lots of lambdas, this is non-trival. I would argue that tons of lambda is a poor architecture. What you gain with isolation you lose
management, complexity, nimbleness, attack vector surface.
You could also argue my harness locks you into AWS as it is aws specific. However I'd argue that it is the other aws services locking you in (ex: Dynamo) or your code/architecture.
You could argue that if you have lots of lambdas, this is non-trival. I would argue that tons of lambda is a poor architecture. What you gain with isolation you lose management, complexity, nimbleness, attack vector surface.
You could also argue my harness locks you into AWS as it is aws specific. However I'd argue that it is the other aws services locking you in (ex: Dynamo) or your code/architecture.