Welcome to AWS-Lambda-Docker-Puppeteer Discussions! #1
Replies: 1 comment 7 replies
-
|
How big is the docker image? I have something like this running in AWS but the image is 2.2gb 👎 which causes terrible cold start times. |
Beta Was this translation helpful? Give feedback.
-
|
Just as an additional note, I would recommend Playwright over Puppeteer in lambda for parallel browsers in a single invocation. I found it easier to run Playwright with multiple pages/browsers over Puppeteer. I have a repo for Playwright Docker in Lambda here. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting, I will probably try this implementation considering the image is much smaller. Provisioned concurrency is a good solution but it seems to me that AWS bumped the prices up. I am glad that container images are supported for lambda now, before trying this was a complete nightmare in my experience. |
Beta Was this translation helpful? Give feedback.
-
|
Also, I have github actions setup which tags and pushes images to ECR based on version numbers. Then it connects the newly tagged image to the lambda so it ties it together nicely for continuous delivery. I think having a pipeline like that could be somewhat useful for this repo. |
Beta Was this translation helpful? Give feedback.
-
Just added this! |
Beta Was this translation helpful? Give feedback.
-
|
For the first one, make sure your user data dir on the disk is saved in /tmp. Thats the only place AWS Lambda supports writing files to during runtime. For the second issue, it seems as though the aws-lambda-ric npm package didn't install correctly for some reason. |
Beta Was this translation helpful? Give feedback.
-
👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:
build together 💪.
To get started, comment below with an introduction of yourself and tell us about what you you're doing with this repo.
Beta Was this translation helpful? Give feedback.
All reactions