Skip to content

Commit

Permalink
docs(troubleshooting): add aws lambda resources (puppeteer#1926)
Browse files Browse the repository at this point in the history
  • Loading branch information
ebidel authored and aslushnikov committed Jan 31, 2018
1 parent bae44a8 commit 1716a74
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions docs/troubleshooting.md
Original file line number Diff line number Diff line change
Expand Up @@ -243,3 +243,11 @@ When you click add buildpack, simply paste that url into the input, and click sa
If you need to render Chinese, Japanese, or Korean characters you may need to use a buildpack with additional font files like https://github.com/CoffeeAndCode/puppeteer-heroku-buildpack

There's also another [simple guide](https://timleland.com/headless-chrome-on-heroku/) from @timleland that includes a sample project: https://timleland.com/headless-chrome-on-heroku/.

## Running Puppeteer on AWS Lambda

AWS Lambda [limits](https://docs.aws.amazon.com/lambda/latest/dg/limits.html) deployment package sizes to ~50MB. This presents challenges for running headless Chrome (and therefore Puppeteer) on Lambda. The community has put together a few resources that work around the issues:

- https://github.com/adieuadieu/serverless-chrome/blob/master/docs/chrome.md (tracks the latest Chromium snapshots)
- https://github.com/sambaiz/puppeteer-lambda-starter-kit (uses an old version of Chromium)
- https://github.com/universalbasket/aws-lambda-chrome

0 comments on commit 1716a74

Please sign in to comment.