From 937167933b511ae0065282cf7d0dde575afee878 Mon Sep 17 00:00:00 2001 From: Lovell Fuller Date: Sat, 27 Dec 2025 09:03:44 +0000 Subject: [PATCH] Docs: Add list of well-maintained Lambda Layers --- docs/src/content/docs/install.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/src/content/docs/install.md b/docs/src/content/docs/install.md index e5a3c182..d2eaa720 100644 --- a/docs/src/content/docs/install.md +++ b/docs/src/content/docs/install.md @@ -188,6 +188,12 @@ and how to configure it. Some package managers use symbolic links but AWS Lambda does not support these within deployment packages. +An alternative approach is to use a well-maintained, third-party Lambda Layer: + +- [cbschuld/sharp-aws-lambda-layer](https://github.com/cbschuld/sharp-aws-lambda-layer) +- [pH200/sharp-layer](https://github.com/pH200/sharp-layer) +- [zoellner/sharp-heic-lambda-layer](https://github.com/zoellner/sharp-heic-lambda-layer) + To get the best performance select the largest memory available. A 1536 MB function provides ~12x more CPU time than a 128 MB function.