You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 3, 2024. It is now read-only.
My lambda handler has the code below. After running some tests in Lambda, it's obvious that webdrive.Chrome(), driver.get() and driver.quit() are the methods lagging it the most. But without proxy that's not a problem.
On local machine the proxy works fine.
Is there any way to work around this? Do you have similar cases where newer versions of Selenium-Wire or Python work inside Lambda?
Apparently, newer versions of Selenium-Wire won't work inside Lambda, so I'm using the following config to deploy my Lambda function:
Versions
[headless-chromium] = 1.0.0-57
[chromedriver] = 86.0.4240.22
urllib3==1.26.6
selenium==3.141.0
pyopenssl==22.0.0
cryptography==38.0.4
selenium-wire==4.0.4
Lambda settings
Runtime = Python 3.7
Memory = 10240 MB
Timeout = 300 seconds
My lambda handler has the code below. After running some tests in Lambda, it's obvious that
webdrive.Chrome()
,driver.get()
anddriver.quit()
are the methods lagging it the most. But without proxy that's not a problem.On local machine the proxy works fine.
Is there any way to work around this? Do you have similar cases where newer versions of Selenium-Wire or Python work inside Lambda?
The text was updated successfully, but these errors were encountered: