Layer with Python runtime support

[justincandoit]

Would it be possible to create a similar Chrome AWS Lambda layer that is compatible with Python Lambda functions?

[vladholubiev]

It is supported; we publish the layer without restricting the runtime.

[justincandoit]

Do you know what the import statement would be?

[vladholubiev]

The layer contains a pre-compiled Chromium binary, which you can run just like any other executable in Python. It's probably located at /var/task/bin/chromium, but to confirm, you might want to download the Lambda Layer ZIP from AWS and check for yourself.

[hexi-verifiet]

Hey @vladholubiev, I had a similar use case of trying to launch Playwright-Python (Pyppeteer package recommended Playwright) browser on a lambda function using the layer here. I ran into two issues:

1. The path for my lambda layer has been '/opt/nodejs/node_modules/@sparticuz/chromium/bin'. I've gotten this path to work well with Nodejs puppeteer. This invocation is returning BrowserType.launch: Failed to launch:Error: spawn /opt/nodejs/node_modules/@sparticuz/chromium/bin EACCES and I'm unable to debug from here. Is this bin the correct binary to invoke?
2. Seems like the architecture of x86_64 is not compatible with ARM_64. The reason I used ARM was to use PIP for code bundling. Looks like this request should address this incompatibility: [REQUEST] arm64 support Sparticuz/chromium#186

[Sechorda]

Hey @vladholubiev, I had a similar use case of trying to launch Playwright-Python (Pyppeteer package recommended Playwright) browser on a lambda function using the layer here. I ran into two issues:

1. The path for my lambda layer has been '/opt/nodejs/node_modules/@sparticuz/chromium/bin'. I've gotten this path to work well with Nodejs puppeteer. This invocation is returning BrowserType.launch: Failed to launch:Error: spawn /opt/nodejs/node_modules/@sparticuz/chromium/bin EACCES and I'm unable to debug from here. Is this bin the correct binary to invoke?
2. Seems like the architecture of x86_64 is not compatible with ARM_64. The reason I used ARM was to use PIP for code bundling. Looks like this request should address this incompatibility: [REQUEST] arm64 support Sparticuz/chromium#186

Can you please share more info?

When I download the .zip layer I only see nodejs/node_modules. How do I use this within python runtime?

[dgallitelli]

Just to add a bit more details to this discussion. I'm using Layer v50.

this is what I get when I listdir the content of the layer in /opt:

/opt/nodejs/node_modules/@sparticuz/chromium/package.json
/opt/nodejs/node_modules/@sparticuz/chromium/bin/al2.tar.br
/opt/nodejs/node_modules/@sparticuz/chromium/bin/al2023.tar.br
/opt/nodejs/node_modules/@sparticuz/chromium/bin/chromium.br
/opt/nodejs/node_modules/@sparticuz/chromium/bin/fonts.tar.br
/opt/nodejs/node_modules/@sparticuz/chromium/bin/swiftshader.tar.br
/opt/nodejs/node_modules/@sparticuz/chromium/build/helper.js
/opt/nodejs/node_modules/@sparticuz/chromium/build/index.js
/opt/nodejs/node_modules/@sparticuz/chromium/build/lambdafs.js

this is the content of /var/task, as @vladholubiev seemed to suggest we should find the chromium binary there:

/var/task/lambda_function.py

Any suggestions on how to use the Layer with Python is appreciated. I really want to avoid having to use Docker images if possible.