Starter Kit for running Headless-Chrome by Puppeteer on AWS Lambda.
It can use alone and also supported Serverless Framework.
This is simple and don't need IAM role but you have to deploy package by yourself. Don't worry, even if you will become to use Serverless in the future, what you should do for migration is little.
$ git clone -o starter-kit https://github.com/sambaiz/puppeteer-lambda-starter-kit.git your_project_name
Serverless Framework can manage settings with CloudFormation and deploy.
$ serverless install --url https://github.com/sambaiz/puppeteer-lambda-starter-kit --name your_project_name
By executing SLOWMO_MS=250 npm run local, you can check the operation while actually viewing the chrome (non-headless, slowmo).
Lambda's memory needs to be set to at least 384 MB, but the more memory, the better the performance of any operations.
512MB -> goto(youtube): 6.481s
1536MB -> goto(youtube): 2.154s
If you use alone, run npm run package, and deploy the package.zip.
If you use with Serverless, run serverless deploy (this runs npm run package when packaging).
Due to the large size of Chrome, it may exceed the Lambda package size limit (50MB) depending on the other module to include. In that case, put Chrome in S3 and download it at container startup so startup time will be longer.
Run npm run package-nochrome, deploy the package.zip, and set following env valiables on Lambda.
CHROME_BUCKET(required): S3 bucket where Chrome is putCHROME_KEY(optional): S3 key. default:headless_shell.tar.gz
This kit includes Chrome built by myself because official build Chrome installed by Puppeteer has problems about running on Lambda (missing shared library etc.).
If you want to use latest chrome, run chrome/buildChrome.sh on EC2 having at least 16GB memory and 30GB volume.
See also serverless-chrome.
Once you build it, link to headless_shell.tar.gz in chrome dir.
Lambda上でPuppeteer/Headless Chromeを動かすStarter Kitを作った - sambaiz-net