This message was deleted.

Create the log group manually, instead of letting lambda create one for you. There's an example in the docs: https://www.pulumi.com/registry/packages/aws/api-docs/lambda/function/#cloudwatch-logging-and-permissions

example in typescript

const lambdaFunctionApi = new aws.lambda.Function(
  `${appName}-api`,
  { handler: "lambdaApiHandler.handler", ...lambdaFunctionArgs, ...lambdaAdditionalFunctionArgs },
  { dependsOn: [applicationRole] },
);

lambdaFunctionApi.name.apply(
  lambdaFunctionName =>
    new aws.cloudwatch.LogGroup(`${appName}-function-api-lg`, {
      name: `/aws/lambda/${lambdaFunctionName}`,
      retentionInDays: 14,
    }),
);

Can I suggest that creating the log group inside an

apply()

could be avoided thus:

new aws.cloudwatch.LogGroup(`${appName}-function-api-lg`, {
      name: pulumi.interpolate`/aws/lambda/${lambdaFunctionApi.name}`,
      retentionInDays: 14,
    });

We tried something like that a while ago and had issues, so we landed on the

apply()

. Thank you for the tip, because it would be nice to drop those applys in favor of interpolation.

wont the lambda create the log group then the new aws.cloudwatch.LogGroup will fail due to the log group already existing?