Diego Parrilla

The new version implements the changes suggested. It also implements a new optional parameter with the API hostname.

Good feedback! I have to review some of the suggestions because I don't understand the implications, I will try to do my best this weekend 👍

I made it work and I created this: https://github.com/diegoparrilla/headless-chrome-aws-lambda-layer Changing from the vanilla Selenium it's almost straight forward. Hope it helps.

Hi Otto! I have used this project with [undetected-chromedriver](https://github.com/ultrafunkamsterdam/undetected-chromedriver) driver successfully. You only need to write in your lambda your own [`src/headless_chrome.py`](https://github.com/diegoparrilla/headless-chrome-aws-lambda-layer/blob/main/src/headless_chrome.py) importing the undetected-chromedriver libraries instead of the selenium...

Any update on this topic?

I used it in several scenarios and never found a disk space issue. The layer uses the` /tmp` folder in the AWS lambda and it's[ limited by design to 512MB](https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html)....

Sorry, the chrome and driver binaries need a lot of space and cannot be trimmed. I suggest finding alternatives to trim the size of other libraries. Example: avoid embedding binaries...

Version 0.0.18 will allow custom selection of the virtual drives A: or B: Ex: Drive A as a physical drive/Gotek, Drive B an emulated drive by the device

This appears to be a regression. The implementation of "Disable XBIOS trap" was specifically designed to address this issue. Disabling the XBIOS traps should resolve the visibility problem with windows....

I've been diving into the problem with frogs13.st on TOS 1.00 UK, and it looks like I've managed to pinpoint where things might be going awry. Interestingly, the "disable XBIOS...