chrome-aws-lambda-layer VS chrome-aws-lambda

This repository hosts a Community Lambda Layer so we can use it directly on our function. At this time the latest version is 24

Have you installed a Chrome / Chromium binary as a Lambda layer (e.g. this layer)? Chrome isn't included by default.

FROM laravelphp/vapor:php74 RUN apk update && apk add --no-cache curl unzip WORKDIR /opt RUN curl -sSL https://github.com/shelfio/chrome-aws-lambda-layer/raw/master/chrome_aws_lambda.zip --output chrome_aws_lambda.zip RUN unzip chrome_aws_lambda.zip -d /opt RUN rm chrome_aws_lambda.zip RUN curl -sSL https://github.com/lambci/node-custom-lambda/raw/master/v12.x/layer.zip --output node-custom-lambda.zip RUN unzip node-custom-lambda.zip -d /opt/node-custom-lambda RUN cp -avr /opt/node-custom-lambda/bin /opt/bin RUN rm node-custom-lambda.zip && rm -rf node-custom-lambda WORKDIR / COPY . /var/task

Puppeteer automates Chromium browsers (headless and non-headless), but can Chromium run in a Lambda function? Not without some great work from the community to create a Chrome build for the AWS Lambda runtime. There’s also a Lambda layer solution for this too, although I haven’t tried this approach yet. Another great feature of this package is that it runs headless when running in Lambda and non-headless when running locally - so it’s frictionless to develop, test and run your scripts.

Lambda would be my choice for this. You could even stay within the free tier depending how often you run this process. You can orchestrate puppeteer UI flows in lambda using this package https://github.com/alixaxel/chrome-aws-lambda My team does this and it works great.

git clone --depth=1 https://github.com/alixaxel/chrome-aws-lambda.git && \ cd chrome-aws-lambda && \ make chrome_aws_lambda.zip

When requesting the API route, the Next.js serverless function will actually spin up a web browser on the server (a headless instance of Chromium, using chrome-aws-lambda). Next, a webpage will be generated with HTML we can define ourselves. This HTML will be used to construct the image. That means that as a developer we can generate images using HTML and CSS, technologies we are already familiar with!

This plugin is used for all our AWS Lambda deployments, using a wide range of Node modules, some with more quirks than others. We use it together with Lambda Layer Sharp and Chrome AWS Lambda.

I was able to successfully to run chrome with puppeteer in AWS Lambda for a similar use case. I used an "optimized" version of chrome packaged as an AWS Lambda Layer.

git clone --depth=1 https://github.com/alixaxel/chrome-aws-lambda.git && \ cd chrome-aws-lambda && \ make chrome_aws_lambda.zip

Simplest method use ]Puppeteer](https://blog.risingstack.com/pdf-from-html-node-js-puppeteer/) with chrome-aws-lambda.