Could be worth to consider the following guide when it comes to performance: https://docs.aws.amazon.com/ses/latest/dg/troubleshoot-throughput-problems.html
Based on your explanation, it seems that when you use the AWS CLI to send emails via SES, it's getting delivered as expected. However, when triggering emails from your backend application in the development environment, there is a delay of approximately 5 minutes.
In this case, the issue appears to be related to the sending server or application. To troubleshoot the delay, you can try to follow these steps:
Check SES Message IDs: For each successfully enqueued message, SES returns a unique message ID. Make sure you are logging these message IDs on your side. This will help you track whether SES has accepted your messages.
Compare Timestamps: Compare the timestamp when your application logs the message ID with the timestamp when the call to SES was made. If there is a significant time difference, it indicates that something happened between your application sending the email and SES acknowledging its receipt.
Investigate Custom Software: If you have any custom software between your application and SES, it's important to examine the software's logs for any evidence of delays. Some software may buffer or introduce delays in message delivery.
By examining the logs of any intermediary software and comparing timestamps, you can identify where the delay might be occurring. It's possible that the delay is introduced by the custom software in your backend environment.
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- Why are emails failing to deliver when I send Amazon SES emails using the SendTemplatedEmail operation?AWS OFFICIALUpdated 7 months ago
- EXPERTpublished a year ago