- Le plus récent
- Le plus de votes
- La plupart des commentaires
Hello.
When I click on cloudwatch logs, I do see this message even though it is not affecting the execution of function: Log group does not exist The specific log group: /aws/lambda/Test_sendemail does not exist in this account or region.
The most likely reason why CloudWatch Logs cannot be found is that the IAM policy for outputting from Lambda to CloudWatch Logs is not set.
If you have not set up the IAM policy described in the document below, please try setting it up.
https://repost.aws/knowledge-center/lambda-cloudwatch-log-streams-error
Do you know why I am not receiving any emails after I run the function?
I sent an email using the same code in my environment and was able to confirm sending and receiving without any problems.
Did it go to your spam mail?
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a 7 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 7 mois
Hi
I updated the IAM role attached to the Lambda function and added "CloudWatchFullAccess" AWS managed policy to it and I still get that cloudwatch log error. Could it be related to creating the function in "us-east-2" instead of "us-east-1"?
<<<There is no emails sent to spam folder. I am getting this non-delivery email in source email. >>>
I am surprised it is running fine at your end. Could it be related to my "Free Tier Account" or is there a way to know more details why AWS cannot deliver the email? Do you have to have a domain or something else configured for SES?
thanks,
The region in which you create your Lambda function should not matter. If it is the default setting, I think the log will be output to the same region as the Lambda function.
You can use SES even if you have a free account. Also, if the email address is verified, you can send, so there is no problem even if you do not configure the domain. When troubleshooting SES, I think you need to refer to the following documents and check them one by one. For example, the bounces listed in "Check for sending issues from Amazon SES to the recipient domain" are possible causes for not being able to send emails. https://repost.aws/knowledge-center/ses-unable-receive-email
Hi I am wondering if this email delivery problem might be due to "Yahoo" security blocking some auto message from AWS? Have you used Yahoo email addresses or Gmail or Corporate Email addresses in your test?
https://repost.aws/questions/QUMl39S_9PSjCT6PQI6ow7fg/unable-to-deliver-to-yahoo-addresses-ses-ip-getting-blocked
https://stackoverflow.com/questions/25378125/ses-delivery-status-notification-failure
Do you think the CloudWatch Log would show what is causing the problem if it works or not?
Thanks,
I do not use Yahoo email addresses. I did the test using Gmail. It is possible that Yahoo is blocking it, but in that case I don't think we can handle it.
I think you can check the failure of SES API execution, but I don't think you can see the information that it is blocked on Yahoo etc.
Yes, it was Yahoo blocking Email. Worked fine using GMAIL addresses.