NLog.AWS.Logger does not work when launched from an AMI of another AWS account

[t-nakajimaa]

I am logging to both file and cloudwatch logs in the NLog of account A's Windows instance and everything is working fine.
I share this AMI with account B, launch the instance, and then create the same IAM policy as account A (Required IAM Permissions in README) and assign the EC2 IAM role, but the logs are output to a file, but not to cloudwatch logs.
I was able to manually send the logs to the cloudwatch logs using the "aws logs" command in the CLI of the account B instance, so it seems that policy assignment is not a problem.
I would like to investigate the cause of the problem, but I don't know what more I can do since the aws-logger-errors.txt file has not been created and I don't see any errors anywhere.
Please let me know what I should do.

[ashishdhingra]

@t-nakajimaa Could you please check if the region where new EC2 instance is created in account B is different from what was used in account A. If region is not set explicitly in AWS NLog configuration, then it would infer region from EC2 instance. If the region is different in account B, then access the CloudWatch logs in that region.

Thanks,
Ashish

@github-actions proposed-answer

[github-actions[bot]]

Hello! A team member has marked the above comment as the likely answer to this discussion thread.

• If you agree, please upvote that comment, or click on Mark as answer. I will automatically mark the comment as the answer next time I check.

• If this answer does not help you, please downvote the answer instead and let us know why it was not helpful. I will add a label to this discussion to gain attention from the team.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.