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

`Lambda@Edge` `503 ERROR`

*The situation*
• I have a Cloudfront Distribution and defined `defaultCacheBehavior.lambdaFunctionAssociations`  to trigger a lambda on `origin-request` .
• Weirly enough, there is no trigger in the lambda function overview, it says "+ Add trigger". I am not sure if I am missing iac here at some point.
*The Problem*
When I open the url, I get an `503 ERROR` .

*What I tried*
• There are some logs written to s3 (linked in _CloudFront &gt; Telemetry &gt; Logs &gt; S3 Bucket_) , but the only valuable information I read out of it that there was a `LambdaExecutionError` .
• If I go to the Lambda@Edge Function and click in Monitoring and then View in CloudWatch, it says `Log group does not exist` .
Can anybody point me into the right direction? Many thanks in advance

Ok, `Log groups &gt; /aws/{region}.{function.name}` (region: us-east-1) and then changing the region to where the request is coming from (in my case from eu-central-1 brought up all logs including why the lambda is failing