This message was deleted.

sparse-intern-71089

02/15/2022, 2:17 PM

This message was deleted.

billions-processor-3086

02/15/2022, 2:20 PM

someone else may know something i don't here, but since those log groups aren't created until the function executes i don't believe Pulumi would have any way of knowing they exist or what they're named

thousands-area-40147

02/15/2022, 2:21 PM

Ah, hm, so it's entirely an AWS thing

thousands-area-40147

02/15/2022, 2:21 PM

Thanks for the answer!

billions-processor-3086

02/15/2022, 2:21 PM

sure thing

proud-art-41399

02/21/2022, 5:36 AM

You have to create the log group after the Lambda function and explicitly set a dependency. In Python:

Copy code

my_lambda_log_group = aws.cloudwatch.LogGroup(
    "my-lambda",
    retention_in_days=30,
    name=my_lambda.name.apply(
        lambda name: f'/aws/lambda/{name}'
    ),
    opts=pulumi.ResourceOptions(depends_on=[my_lambda])
)

This way it's also possible to set e.g. retention which would otherwise be 1 month by default.

🙌 1

proud-art-41399

02/21/2022, 5:38 AM

The only downside is that you can't come with your own name for the log group, it has to follow the standard naming (i.e.

/aws/lambda/...

)

7 Views

Open in Slack

Previous Next

Pulumi Community

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.