Yeah - this is a somewhat unfortunate thing with Lambda - it lazily creates the LogGroup using a well known name when there are first logs.
I believe I’ve had success in the past creating the loggroup with the same name explicitly prior to the lambda - which will then reuse that loggroup. You can the refer to it from other resources.