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

Hello everyone. I worked through this example and it was probably the easiest lambda / api gateway deployment (complete with secrets management) that I've done so far: <https://github.com/pulumi/examples/tree/master/aws-ts-apigateway-auth0> | However I have a question. Let's say that I wanted to only deploy that authorizer and attach it to an existing API gateway? Can this be done?

Hey Damian, this blog post may be helpful for you: <https://www.pulumi.com/blog/adopting-existing-cloud-resources-into-pulumi/>

it isn't even so much that I want to add it to the existing api gateway, I just don't understand how to deploy a lambda that isn't tied to an api gateway

actually I think I might have found an example

here's the docs on how to use the lambda module <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/lambda/>