- Newest
- Most votes
- Most comments
Hello @Tom,
Thank you for taking the time to respond to this issue.
The issue has been resolved and was caused by our server not being able to handle the number of requests being sent to us through SNS, we were able to identify this with the help of a representative through the support channel and looking through our log on Cloudwatch. Also, the missing in the initial question was for record purposes to identify the events which of the events from SES we couldn't account for and it was queried as "bounced is null and complained is null and delivered is null" etc using column names as available on our database table.
Thank you once again.
Hello,
Thank you for posting on AWS re:Post forum. My name is Tom. I see that you would like to view the list of email events (other than SEND) on webhooks subscribed to SNS topics.
Based on the event types mentioned, looks like the events (such as "OPEN", "DELIVERED", "DELAY-DELIVERY", "BOUNCE" or "COMPLAINT") are reported from SES side. However, looking further on the event types that can be monitored on SES, there is no such event named "missing" [1]. Therefore, please confirm and validate on how the {"missing": 7748"} metric is generated. Furthermore, reviewing on the various ways to monitor for email activities [1], it appears using "Event Publishing" might be a more detailed option in receiving email-related activities, as compared to "Feedback Notifications". Using "Event Publishing" [2] allows to receive SNS notification on "opens", "clicks", "rejects", and "rendering failures", in addition to the "deliveries", 'bounces", and "complaints" event types.
With that said, the "Event Publishing" feature requires the SES user to configure event destination [3], and when configuring event destination, please ensure to select all interested event types (as compared to selecting "Send" event type only). If configured correctly, the received JSON object in SNS topic will have the field "eventType" describing the type of email events. [4]
I hope the above information is helpful. If further assistance is required, please feel free to open a Technical Support Case [5] to Simple Email Service for more in-depth troubleshooting. Have a nice day!
Links and References
[1] https://docs.aws.amazon.com/ses/latest/dg/monitor-sending-activity.html
[2] https://docs.aws.amazon.com/ses/latest/dg/monitor-using-event-publishing.html
[3] https://docs.aws.amazon.com/ses/latest/dg/event-destinations-manage.html#event-destination-add
[5] https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
Relevant content
- Accepted Answerasked a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
I might have missed it in your question, but have you turned on SNS delivery logging for your topic(s)? That would give you a better idea of what SNS thinks it did. https://docs.aws.amazon.com/sns/latest/dg/sns-topic-attributes.html