2 Antworten
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
Hello.
Isn't there any execution history left in the Lambda log?
If it is not logged, check whether CloudWatch Alarm has permission to run Lambda in Lambda's resource-based policy.
https://docs.aws.amazon.com/lambda/latest/dg/access-control-resource-based.html
0
Lambda history stopped back on 1/09/24. Lambda shows the invoke permission granted to the alarm ARN.
I decided to just change the trigger on the Lambda directly to come from the CW log group and typed a filter in there. But it would be really nice to know how to create a CW alarm and have it trigger a Lambda. The console wizard seems like it's very easy, but in my attempts, it doesn't work.
beantwortet vor 3 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 8 Monaten
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren