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

<https://github.com/pulumi/pulumi-awsx/blob/ce18ba6e676e10077c91a393a33a86feedd92502/nodejs/awsx/apigateway/api.ts#L79-L85>

so in your routes to API you would basically do this:

`[{ path: "/whatever", method: "GET", eventHandler: yourAwsLambda }]`

`eventHandler` is typed as `eventHandler: aws.lambda.EventHandler&lt;Request, Response&gt;`

And `EventHandler` is just an alias like so:

`export type EventHandler&lt;E, R&gt; = Callback&lt;E, R&gt; | LambdaFunction;`

where `LambdaFunction` *is* just `aws.lambda.Function`.

so, basically, we're saying: you can give us a JS callback, or a real aws Lambda.

Oh, it was right in front of my nose and I haven't seen it!

we should advertise this functionality more.  but it is our intent that any place we allow a JS callback, you should be able to pass a real AWS lambda.