Issue with chromium on AWS Lambda with 127.0.6533.99 (amd64): Chromium Stuck and Lambda Timeout
I’m using Chromedp (v0.10.0) to launch Chromium on AWS Lambda.
My setup involves deploying a Docker container based on the latest Debian image and installing the latest version of Chrome. On an arm64
architecture, everything works fine (using Chrome version 126.*). However, on an amd64 architecture, Chrome gets stuck and eventually causes the Lambda function to time out.