This message was deleted.

If anybody has a good example for this, please share it with me. Thanks!

So here is the problem: Each lambda runtime requires a different packaging technology. All packages require to end up in S3 bucket Lambda resource Requires S3 url There isn't any built-in functionality that can help you with that AFAIK. (similar to what serverless framework does) Feel free to browse examples and prove me wrong https://github.com/pulumi/examples/ So what you need to build yourself (CDK devs did that as well) is a functionality that enables you to package the lambda with all its dependencies and uploads it to S3. There are multiple ways to achieve this: 1) Build the package zip files and upload them to S3 before running pulumi in your pipeline 2) Maybe plugin https://www.pulumi.com/docs/intro/concepts/assets-archives/ But that won't let you store previous versions in S3 if that's what you want (it's basically doing this: https://registry.terraform.io/modules/nozaq/lambda-auto-package/aws/latest?tab=dependencies) 3) Build a custom provider that can do that for you - essentially replicate the behaviour of this: https://docs.aws.amazon.com/cdk/api/latest/docs/aws-lambda-python-readme.html

Thank you for the detailed breakdown @great-sunset-355 - I appreciate it! 🙃

I would also ask what you mean by “external packages” — do you mean like a library from npm? (If so, the answer may be much simpler.)

@miniature-musician-31262 I'm curious about your solution, how would you create a required

.zip

file for lambda in a repository that contains lambda functions with multiple runtime languages? The ultimate goal is to upload a

.zip

with all dependencies (or a portion if using Lambda Layers)

one option that’s might be considering is just using AWS SAM to create the lambda zips