- The flexibility of sending emails from various products using the same email address, without the necessity of having the same domain for the product and the email address.
- Allow you to perform basic verification and add DKIM signing to the domain. You can verify by domain or email. If you don't or can't sign DKIM, SES still sends out your email but it may end up in somebody's Spam folder or being shielded by institutional firewalls.
- The flexibility of doing mail relay from the server or the code level. You can configure Postfix and make sure all emails are relayed via AWS SES. You can also write emailing class in Python, PHP, etc. which utilizes the SES API to send emails without dealing with Postfix.
- Highly responsive and efficient. Sending large batches of newsletter queues to SES has never been a problem. And delegated emails are usually received instantly.
- Official documentations are pretty good. Follow the tutorial and you can setup your mail relay quickly and verify your email or website domain.
- The SES support actually watches your back for you. Because they care about the bounce rate which affect their reputation, they monitor your bounce rate. I work at a large institution and the unit had never cared about the bounce rate until one day we were told our SES service was throttled due to high bounce rates (>40%). So we had to clean up our database's client table which had not been cleaned for maybe 10 years. This kind of instances have happened multiple times, and I was glad secretly because it in effect obliges the administrative to care about their service quality and user experience.
- Can hook up with other AWS or non-AWS services to send out automatic notifications. For example, we are sending automatic emails via SES whenever our website is down, newsletter (also sent via SES) is bounced, an Elastic Transcoder job is done, etc. These are setup via AWS SNS. It's also totally possible to automate whatever email sending by utilizing the SES API. You can accomplish virtually anything you want.
The major complaint is SES is (almost) totally self-managed and they don't provide tools to add to the values external to the core product functionality. For instance, they don't provide email logs from which you can debug your scripts or server config. They also don't provide newsletter templates or management tools that can make your life really easy. For newsletters, we ended up creating the template and test it out in Mailchimp, before we use it with SES in production.
I really hope they can provide some additional features to simplify a lot of things for you.
Requires basic experience with servers and domain certificates to get SES running quickly. To use advanced features (e.g. via AWS SNS or utilizing the SES API), more experiences are needed. If you are a startup and don't want to invest lots of time to get the newsletters sent, probably you should first look at Mailchimp or other similar "dummy-proof" solutions.
1) Having a dozen products that all want to send out notifications/newsletters from the same email address.
2) Wanting to pay minimum for sending emails (currently it's $0.10 per 1,000 emails).
3) Worry-free once the relay is setup. Just let it run and AWS makes sure it's working all the time.