Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Amazon SES low info

0

I'm using Amazon SES in my app to send password reset and token emails. However, it's taking a long time, and I can't figure out why. The email is configured as specified in the identities area. I've created a configuration set that exports data to CloudWatch. But the information I need the most is missing; I only have a graph of sent or not sent emails. I need a complete log: when the server sent the message, the time it took to confirm the sending, something I can use to identify the problem. Has anyone managed to create a log that is truly useful in CloudWatch or Amazon SES? Something that's not just a success or failure counter?

Even though I've set up a configuration set to export data to CloudWatch, I'm not getting the specific details I need from the logs. The emails I sent yesterday only arrived 4 to 5 hours later. I am sending to two email addresses, and the delay time is too long. The only thing I haven't finalized in the SES configuration is the domain identity, as I am testing my app locally.

Topics
Front-End Web & MobileManagement & GovernanceBusiness ApplicationsNetworking & Content Delivery
Tags
Amazon CloudWatchAmazon Simple Email Service
Language
English
asked 2 years ago188 views
1 Answer
0

Hi Pablo.

To get more detailed logging from Amazon SES, ensure your domain identity is fully verified, as this can affect email prioritization. Use SES's Event Publishing feature with a configuration set that includes detailed event types like "send," "delivery," and "bounce" for better insights in CloudWatch. Consider using SES via SMTP to capture comprehensive logs and test with different email addresses to pinpoint if delays are due to SES or the receiving server. If you have any questions or need further assistance, feel free to reach out!

EXPERT
answered 2 years ago
EXPERT
reviewed 2 years ago
  • Jesse_T
    a year ago

    Sending without a domain identity will fail the domain's DMARC policy, causing messages to be rejected or treated as spam by the receiving mail server.

    Use event publishing to also monitor for "deliveryDelay" events, if you want to see when messages are delayed by the receiving mail server (the message is not yet delivered or bounced)

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content