chrome-aws-lambda-layer | 43 MB Google Chrome to fit inside AWS Lambda Layer | Cloud Functions library

by shelfio Shell Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | chrome-aws-lambda-layer Summary

chrome-aws-lambda-layer is a Shell library typically used in Serverless, Cloud Functions, Tensorflow, Nodejs applications. chrome-aws-lambda-layer has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

43 MB Google Chrome to fit inside AWS Lambda Layer compressed with Brotli

Support

Quality

Security

License

Reuse

Support

chrome-aws-lambda-layer has a low active ecosystem.

It has 468 star(s) with 43 fork(s). There are 35 watchers for this library.

It had no major release in the last 6 months.

There are 5 open issues and 29 have been closed. On average issues are closed in 253 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of chrome-aws-lambda-layer is current.

Quality

chrome-aws-lambda-layer has 0 bugs and 0 code smells.

Security

chrome-aws-lambda-layer has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

chrome-aws-lambda-layer code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

chrome-aws-lambda-layer is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

chrome-aws-lambda-layer releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of chrome-aws-lambda-layer

Get all kandi verified functions for this library.

chrome-aws-lambda-layer Key Features

No Key Features are available at this moment for chrome-aws-lambda-layer.

chrome-aws-lambda-layer Examples and Code Snippets

No Code Snippets are available at this moment for chrome-aws-lambda-layer.

Community Discussions

Trending Discussions on chrome-aws-lambda-layer

Iterate over multiple payloads and take multiple screenshots with Puppeteer AWS Lambda

Serverless framework: Serverless Error Function not found:

How to see console.log statements in deployed Lambda function

Lambda: Value of property Layers must be of type List of String

QUESTION

Iterate over multiple payloads and take multiple screenshots with Puppeteer AWS Lambda

Asked 2020-Aug-23 at 03:42

I am currently using the following Puppeteer AWS Lambda Layer to scrape 30 URLs and create and save screenshots in S3. At the moment, I send 30 individual payloads therefore running 30 AWS Lambda functions. https://github.com/shelfio/chrome-aws-lambda-layer

Each JSON payload contains a URL and an image file name that are sent every 2-3 seconds to API Gateway via a POST request. The first 6 or 9 Lambda functions in the list seem to run fine, then they start to fail with Navigation failed because browser has disconnected! as reported in AWS Cloudwatch.

So I am looking for an alternative solution, How could I edit the code below to batch screenshot a set of 30 URLs, by handling a single array of JSON payloads? (eg. For loop etc)

Here is my current code for generating individual AWS Lambda screenshots and sending to S3:

...

ANSWER

Answered 2020-Aug-23 at 03:42

I tried to replicate the issue and modify the code to use loop.

While working on this issue, I found several things worth pointing out:

the lambda requires a lot of RAM (at least 1GB in my test, but more better). Using small amount of RAM lead to failures.
lambda timeout must be large to handle a number of URLs to screenshot.
your img from the JSON payload is not used at all. I did not modify this behavior, as I don't know if this is by design or not.
similar errors to yours were observed when running async for loop and/or not closing pages opened.
modified return value to output an array of s3 urls.
undefied URL

Modified code

Here is the modified code that worked in my tests using nodejs12.x runtime:

Source https://stackoverflow.com/questions/63489068

QUESTION

Serverless framework: Serverless Error Function not found:

Asked 2020-Jun-05 at 18:41

I'm getting started with nodejs and the serverless framwork.

My handler.js contains:

...

ANSWER

Answered 2020-Jun-05 at 18:41

Let me explain here. Serverless framework can invoke(run) lambda in two ways(locally and in cloud-AWS). It seems you are trying to invoke lambda in AWS. (arn:aws:lambda:us-east-1:155754363046:function:sellthelandnow-dev-hello) Basically this arn does not exist in your AWS-155754363046 account. you need to use

Source https://stackoverflow.com/questions/62221815

QUESTION

How to see console.log statements in deployed Lambda function

Asked 2020-Jun-05 at 00:41

I'm getting started trying to write a lambda function with node and puppeteer. I'm using the serverless framework

I've been trying to follow https://codissimo.sinumo.tech/2019/12/27/serverless-puppeteer-with-aws-lambda-layers-and-node-js/ to utilize the provisioned chrome at https://github.com/shelfio/chrome-aws-lambda-layer . My function is working as expected locally.

my handler.js contains:

...

ANSWER

Answered 2020-May-31 at 20:35

These are accessible in CloudWatch logs.

If you access in the region you execute the Lambda in it should have a log group of /aws/lambda/functionname.

Then a stream of the save revision

Source https://stackoverflow.com/questions/62121378

QUESTION

Lambda: Value of property Layers must be of type List of String

Asked 2020-May-29 at 23:17

I'm getting started trying to write a lambda function with node and puppeteer. I'm using the serverless framework

My Yaml file contains:

...

ANSWER

Answered 2020-May-29 at 22:20

There is a space in your layer ARN.

Your config in YAML:

Source https://stackoverflow.com/questions/62093365

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install chrome-aws-lambda-layer

Click on Layers and choose "Add a layer", and "Provide a layer version ARN" and enter the following ARN. Current version: chrome-aws-lambda v9.1.0 & Chromium v91.0.4469.0.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: