No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

If you want to manage your Lambda source code outside of Pulumi, you can do it just the traditional Lambda way - prepare a seperate Node package, put it in a folder, then include it in your Lambda along the lines of this example:

<https://github.com/pulumi/examples/blob/d61e7a2a662523ef69e70d3c9b658ba8b15b49ab/aws-ts-serverless-raw/index.ts#L53>

<@UB3BGTV63> gotcha, I’d prefer to let Pulumi manage it but when my eventHandler requires a JS file in the same folder, it doesn’t actually get bundled with the lambda

Is it expected with Pulumi that if you need to expand to a more modular lambda that you create the lambda explicitly? using the example you linked above