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

Add a Ghostscript layer: https://github.com/shelfio/ghostscript-lambda-layer

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.