You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The .NET runtime (via the AWSLambdaPSCore module), which has no cold-start support (only single-file handler scripts)
The PowerShell Custom Runtime, linked above, which implements the Lambda Runtime event-loop itself using a full build of the PowerShell runtime for Linux.
I'd be happy to submit a PR with a little more guidance on how to contribute new runtime variants. Some specific areas of uncertainty I had are:
For all build types, what portions of this repo need to be updated?
The only areas I noticed were:
s3-uploader/runtimes, which appears to have folders per variant with build scripts
manifest.json, which references the runtime definition above
For layer/ZIPped Lambdas, how are layers being built/deployed?
The only layer function I see is one for Bun - it's not clear if this runtime is being built/deployed outside the scope of what's in this repo.
It would be great if AWSLabs' PowerShell Custom Runtime were added to the performance comparisons.
PowerShell in Lambda has two options:
I'd be happy to submit a PR with a little more guidance on how to contribute new runtime variants. Some specific areas of uncertainty I had are:
The only areas I noticed were:
s3-uploader/runtimes, which appears to have folders per variant with build scriptsmanifest.json, which references the runtime definition aboveThe only layer function I see is one for Bun - it's not clear if this runtime is being built/deployed outside the scope of what's in this repo.