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 have a question - when I have `aws.lambda.Alias`  how can I wire it up with `API`  ? I was not able to find any documentation on this.

<https://www.pulumi.com/docs/reference/pkg/aws/lambda/alias/#outputs>

You can hook up the `invokeArn` to the `uri` that an integration expects: <https://www.pulumi.com/docs/reference/pkg/aws/apigateway/integration/>

<@UTH0AMTQQ> Thanks for your help, one more question: is there a way to use that simple notation with routes?

``` new API(name, {
        routes: [
            {
                path: "/",
                method: "ANY",
                eventHandler: lambda,
            },
            {
                path: "/{proxy+}",
                method: "ANY",
                eventHandler: lambda
            }],
    });```

When I use the code above, the trigger is not created

I presume you’re using `awsx`  then? In which case, instead of using `eventHandler` for the route, you’ll want to take a look at using an integration target: <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/apigateway/#IntegrationRouteTargetProvider>

I found this <https://github.com/pulumi/pulumi-awsx/issues/184> but is there any documentation/example how to wire it up?

Thanks for helping, I'm trying to wrap my head around how it should be used but some docs/examples would help a lot