3 ms·

In my experience, you are better off with ECS/Fargate than Lambda for serving an API. You get much more flexibility. Also, I've witnessed people editing Lambda

• scarface_74 2y ago
  You can’t edit Lambda code in the console when you deploy a Docker image to Lambda. 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 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/blob/master/fargate.yaml https://github.com/1Strategy/fargate-cloudformation-example/...
• mschuster91 2y ago
  > Also, I've witnessed people editing Lambda code through the console instead of doing a real deploy. what a mess... 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.
  • scarface_74 2y ago
    You can’t edit Lambda code directly in the console when using Docker deployments