I created a basic Lambda function that activates when I upload a file to a bucket and then saves an image to another bucket. It used to log its activities to CloudWatch, but now it isn't saving any logs, even though everything else functions properly. I've played around with permissions, and I've confirmed that the ARNs for the CloudWatch log groups are set up correctly. What could be causing this issue?
3 Answers
Yeah, checking permissions seems essential. If those are fine, it could be a networking issue, like if something's changed that is preventing access to the CloudWatch API. Better take a look!
It sounds like your Lambda function might not have the necessary permissions to write logs to CloudWatch. Make sure the AWSLambdaBasicExecutionRole is attached to your Lambda, and that should fix the problem.
If the logging was working before and suddenly stopped, try to think about what might have changed. Did you move the function into a different subnet in a VPC recently? Or has anyone modified the function's role policy?
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically