Simple question

[yarikbratashchuk]

Hello)
@adieuadieu, could u, please, explain for me some simple stuff:

How is that possible that chrome can bind to the port 9222 on aws lambda?
Does it binds to a port at all?
I'm asking because i want to use binary with cdp client written in go.
Will it work at all?

Sincerely

[adieuadieu]

Hi @yarikbratashchuk. I'm not sure I understand your question. Chrome binds to port 9222 just like any other program can bind to a port. Lambda doesn't forbid you from creating ports. You should be able to use Go to connect to port 9222 from within a Lambda invocation. However, you won't be able to connect to the port from outside of the Lambda function. Lambda functions do not have a public IP.

[yarikbratashchuk]

@adieuadieu thank u for the answer)
The go client makes get request to http://127.0.0.1:9222/json/new, but gets "context deadline exceeded", that is why i asked, it doesn't work for me for now.
How much memory this lambda probably needs?

[adieuadieu]

Hi @yarikbratashchuk. I'm not familiar with that error message. Is there any more information in the function's CloudWatch logs? I would recommend running the function with at least 1024 MB of memory. I usually use the maximum 1536 MB. Chrome is not.. lightweight.

[yarikbratashchuk]

@adieuadieu, this is what i get when try to test function via aws lambda dashboard:
Get http://localhost:9222/json/new: dial tcp 127.0.0.1:9222: getsockopt: connection refused,
but sometimes i get http://localhost:9222/json/new: dial tcp 127.0.0.1:9222: EOF.

context deadline exceeded means that some time has passed but it didn't get a response from http://127.0.0.1:9222/json/new.
Does headless_shell depends on some js stuff, to work?
Does it matter how i invoke lambda?

What is weird is that max memory used
is only 31 MB. As for me it just can't be enough.
And duration is 5258.77 ms.

Thanks a lot for any thoughts

[adieuadieu]

Hm..

Launch the headless_shell with --disable-gpu --single-process --no-zygote --no-sandbox flags. If you want logging, add --enable-logging --log-level=0 --v=99. Try to capture or log the output from headless_shell to CloudWatch (in JS this is done with console.log.) There's usually some kind of error that gets logged to stdout/stderr by headless_shell if something went wrong.

[yarikbratashchuk]

@adieuadieu, seems like no logs on startup. I'm going to leave my go implementation and use your project.