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

Likely by assigning a role to the lambda (`role` property on `aws.lambda.CallbackFunction` resources) and attaching a policy to that role using `aws.iam.PolicyAttachment`.

hey <@U01CBNPKTV2> - there's a more verbose example here which shows how to this:
<https://github.com/pulumi/examples/blob/f2c2f7771674035da4945cc31373b20fc3940069/aws-ts-serverless-raw/index.ts>

Ah I forgot to add I wanted to use this -&gt; <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/apigateway/> I’ve checked the parameters I can pass to options and don’t see a slot for role. anywhere in the endpoints definition there.

<@U01CBNPKTV2> it’s talking about the authorized here, but you can do the same thing with your event handler. Define a callback function and a role, and then pass that to your event handler

<https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/apigateway/#specifying-the-role|https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/awsx/apigateway/#specifying-the-role>