This message was deleted.
# general
s
This message was deleted.
1
b
if you export the stack - do you get a resource ID? Would it be possible that you have pointed Pulumi to a different AWS account?
g
Thanks for the quick response. I'll try that and get back to you!
b
👌
g
The missing log group was a red herring (after
pulumi destroy
and
pulumi up
it was created as expected). However, when I pass the ARN of the newly-created log group into CloudTrail, I get the following error:
Copy code
error: Error creating CloudTrail: InvalidCloudWatchLogsLogGroupArnException: Check the log group ARN: CloudTrail can't validate it.
According to the AWS java SDK docs, "This exception is thrown when the provided CloudWatch log group is not valid."
b
If you can open an issue in Pulumi-aws with some code to reproduce it, I can try and investigate
👍 1
g
Sorry for the radio silence. The issue was that the
log_group
resource ARN lacks the
:*
suffix required for the CloudTrail resource. My workaround:
Copy code
log_group_arn = pulumi.Output.apply(log_group.arn, lambda arn: f"{arn}:*")
trail = cloudtrail.Trail(
    ...
    cloud_watch_logs_group_arn=log_group_arn,
    ...
)
b
yeah this was a breaking change in the upstream provider in pulumi-aws v3.0.0
💡 1
it's linked in the upstream TF provider changelog
✔️ 1
I am sorry you hit this problem
🙏 1