2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
Looks like this was indeed self-inflicted. When I went to the IAM role, I discovered that logging was authorized only for a specific ARN. Checking the "authorize for all in this group" button resulted in my starting to get logs again.
I don't remember when I would have changed that, but.... Whew.
beantwortet vor 2 Jahren
0
Please check if your Lambda function's execution Role has permissions to write logs to CloudWatch. You can use the AWS managed policy AWSLambdaBasicExecutionRole or if you are creating the IAM role/policy manually (and follow least privilege), refer to this document: https://docs.aws.amazon.com/lambda/latest/operatorguide/access-logs.html
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren