How we run Firecracker VMs inside EC2 and start browsers in less than 1s
1–10 of 251 posts
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#2“ click this button, type this text, read this page, take this screenshot.”
You left in the Ai’s instructions. lol
Interesting read though, thanks
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#3“ click this button, type this text, read this page, take this screenshot.” You left in the Ai’s instructions. lol Interesting read though, thanks
well that's how browser agents work in a nutshell lol
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#4[flagged]
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#5crazy that the maker of chrome(google) and also the owner of a massive amount of cloud services has not made a cloud product identical to this yet
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#6How do you handle browser sessions?
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#7> The catch is that regular EC2 is already a VM. AWS runs our host inside its own isolation layer, and then we run browser VMs inside that host. In other words, every browser is a VM inside a VM.
yes but i think there is specifically some ec2s which give you hypervisor access and thereby firecracker too - someone correct me if im wrong?
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#8Very cool to see more use of userfaultfd, really powerful API because you can fully control how and from where memory is loaded during a pagefault.
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#9> Plain headless Chromium is easy to detect by websites with anti-bot measures. Plain headless Chromium avoided getting blocked by websites only 2% of the time, according to our stealth benchmark.
> Our browsers avoid blocks 81% of the time on our stealth benchmark, and 84.8% on Halluminate BrowserBench, the highest of any provider.
Seems very unethical, no? Who uses service providers like this? The whole point of anti-bot measures is to get rid of bots - you are not wanted there.
These kinds of services inevitably make the web more human-hostile and expensive. Websites will continue pushing back on automated usage, meaning more hurdles to access content.
No doubt part of why we see this push for verified ID on the web - not just age gating and "protect the children", but also protect sites from bots, and protect ad revenue (not a statement of support; just seems like an obvious higher order effect)
Re: How we run Firecracker VMs inside EC2 and start browsers in less than 1s
#10> Plain headless Chromium is easy to detect by websites with anti-bot measures. Plain headless Chromium avoided getting blocked by websites only 2% of the time, according to our stealth benchmark. > Our browsers avoid blocks 81% of the time on our stealth benchmark, and 84.8% on Halluminate BrowserBench, the highest of any provider. Seems very unethical, no? Who uses service providers like this? The whole point of an…
> Who uses service providers like this?
People who don't want their headless browser to get blocked?