2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
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.
répondu il y a 2 ans
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
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- demandé il y a 6 mois
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans