chrome-aws-lambda | Chromium Binary for AWS Lambda and Google Cloud Functions | Cloud Functions library

I'm running headless chrome in a lambda layer (https://github.com/alixaxel/chrome-aws-lambda).

Issue is, I am trying to call .toLocaleString("en-AU"), but everything comes out as UTC/GMT regardless. I have read that node didn't always ship with internationalization options. I'm assuming something along those lines is what is going on here.

Any suggestions for how to work around this?

I'm trying to create this lambda function in AWS using Amplify however when I try to launch the chromium the lambda function does not return any value and the function end up timing up:

"errorMessage": "2020-12-09T02:56:56.210Z 57402f8e-9fb2-4341-837d-bdf2ee6e9262 Task timed out after 25.57 seconds" I add the Layer as suggested by @James Shapiro, now I'm getting a URL return for the chromium but it still not launching it:

This is my function:

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:

I am currently working on an AWS Lambda that generates a PDF from HTML. The lambda is working perfectly once deployed however I would like to get it to run locally to make development easier.

I have installed SAM from AWS as well as Docker which AWS says will be needed to run a lambda locally.

In my solution folder in the command line I am running sam local invoke "HelloWorldFunction" -e pdf/test-data/test.json which then appears to work as it says that it is fetching it and then mounting it to the local docker container. However it then gives the following error:

Which appears to be an error about the puppeteer executable for chrome not existing even though it is in there. I am using the following variables:

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

My handler.js contains:

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:

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 Yaml file contains:

I have created a simple application that accepts a URL and converts it to a PDF. It stores the resultant PDF in an S3 bucket and returns the URL of the PDF. It uses Chrome (running headless) to convert the URL to a PDF. I used the serverless framework, AWS Lambda, and the chrome-aws-lambda npm package. When I execute this setup locally using serverless it all works great. I can use postman to make a request with a URL and it returns the URL of the resultant PDF. When I deploy this setup to AWS Lambda, it returns a 502 internal server error response. When I look at the AWS logs for my application I see the following:

So a little background to the task, I'm trying to run the chrome-aws-lambda on aws lambda.

As you can see on the GitHub, it follows async/await syntax. My problem is, I want to be able to read a value from dynamodb in the middle of the execution of chrome-AWS-lambda.

I know how to read the value from dynamodb in normal function, I know how to use chrome-AWS-lambda. I just can't get these 2 to work together.

Should I be using some special function to read the data from dynamodb? currently, I am using DocumentClient.get()

Any help would be very appreciated.