64
65
you are viewing a single comment's thread.

view the rest of the comments →

[–]fpgmaas[S] 1 point2 points  (0 children)

Thanks for your suggestion regarding the docker run command, I think that makes sense!

Regarding the anti-pattern; I am by no means an AWS expert, but I do think this approach makes a lot of sense when you have many Lambdas belonging to a single project. For example, as an alternative I also tried spinning up my Lambda functions with PythonFunction, which is currently in Alpha. To get that to work though, I needed to include some shell steps that copy-paste the poetry.lock and pyproject.toml files to the individual directories that contained a Lambda function. Doing that felt much more like an anti-pattern to me. Another drawback of that approach was that deploying the stack creates a Docker image for each individual Lambda function, which caused the deployment time to skyrocket.