- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Hi,
Is that a Lambda@Edge function? See Lambda@Edge logs and Aggregating Lambda@Edge Logs for more details if my guess was correct.
Regards.
Hello.
Can you confirm that the output destination log group has been changed from the console of the target Lambda?
https://docs.aws.amazon.com/lambda/latest/dg/monitoring-cloudwatchlogs.html
Also, is the IAM policy attached to the Lambda IAM role configured to output logs to a custom log group?
Hi, Thanks for looking into the issue. Yes, in console loggroup name is updated for that lambda (inside monitoring and operations.. tab ). AWS managed AWSLambdaBasicExecutionRole policy is associated with lambda role. policy contains createLoggroup, createlogstream, PutLogEvents actions for all resources.
Still lambda sends logs in aws/lambda/us-east-1.<function-name> loggroup.
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa
Hi, Thanks for your inputs. Yes, It is Lambda@Edge function. As documentation suggests, for edge functions region code in loggroup name seems reasonable. Thanks again for clearing it.