Permissions issue on AWS, spawn EACCES about chrome-aws-lambda HOT 6 CLOSED

Hi @danteata, altought the repository is new (and might change name[space]), I've been running these binaries in AWS Lambda successfully for quite some time, I just ran the example code in the README and the CloudWatch logs output a successful decompression of the binary:

chrome-aws-lambda Inflating 'chromium.br'.
chrome-aws-lambda Finished inflating 'chromium.br' into '/tmp/chromium'.

I also get the correct output from Lambda ("Example Domain").

As you can see on:

I'm using the appropriate AMI image and the binary is also statically linked.

I assume you have transpiled your code to run Node 6.10 using Babel or similar?

from chrome-aws-lambda.

@alixaxel confirmed, my codebase is transpiled to run Node 6.10 via Babel. Could that be the reason? Thanks for the quick reply.

from chrome-aws-lambda.

It's unlikely as I'm doing the same.

Would you mind sharing some more details so we can get to the bottom of this issue? As I mentioned, the example code works just as expected, so I'm out of ideas with what I know.

from chrome-aws-lambda.

How much memory have you given to your Lambda?

from chrome-aws-lambda.

@alixaxel it strangely started working ok without any further updates to the deploy. I allocated ~1GB of memory.

from chrome-aws-lambda.

Closing as it seems to be resolved.

from chrome-aws-lambda.