Hi Everyone, Was going through the SST example of social-cards (https://serverless-stack.com/chapters/dynamically-generate-social-share-images-with-serverless.html) and it uses lambda layers to drive chrome-aws-lambda and puppeteer. We have a similar use case for chrome-aws-lambda but using the layer results in 25-32 seconds of total time. Separately, we tried a no lambda layer approach using serverless.com and packaging up an instance of chrome using a .zip which resulted in 5-10 second execution time. So now weWe couldn’t figure out how to get the chrome-aws-lambda to work without a non-layer

Hey @Tony J

using the layer results in 25-32 seconds of total time.

Is the building step taking the most time? Or is the deploying step?

Yeah which step is taking all that time?