1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi,
The lambda logs can give more insight on the type of the error you are getting. If you are trying to send messages through SES from a Lambda code and the message is received by SES, then you should receive a message ID. If there is no message ID, this means that the messages has not been received by SES at all, and in that case, the lambda logs should give you more insight about the error you are encountering.
Hope this helps! Mo
répondu il y a un an
Contenus pertinents
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 6 mois
- demandé il y a 6 mois
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Sadly, I only found the timeout on lambda logs. None further information... I added some application logs and I realized that the timeout occurs on the (smtp.Connect(_appSettings.SmtpHost, _appSettings.SmtpPort, SecureSocketOptions.Auto);) step.
I have consulted cloudtrail but got nothing...
I also added AdministratorAccess role to the lambda policy and nothing...