[alixaxel]

Yes, this is a good solution but only if you don't have any sort of session data that you want flushed out after it runs. One could argue you could use browser contexts (incognito tabs) to have ephemeral sessions, but unfortunately that feature doesn't work in --single-process mode (which AWS Lambda requires).

[pouta]

I'm using incognito mode to parse some pages that for some reason I can't using the normal context.

I have been considering moving my pool of chromium workers to lambda functions so we can avoid api slowdowns due to a high number of parsings at the same time.

Are there any other side effects of running chromium headless in a lambda function?