Letting the experts do the heavy lifting: How I switched a part of our email delivery to AWS

I wrote another article briefing about my agony towards Microsoft and their bad spam filters. I have tried a lot of recommendations from my industry friends to improve the IP reputation but all in vain. I had to make a call about what to do! I devised to leverage AWS (SES) to improve the situation. Since a lot of our email infrastructure is mission critical (important notifications to clients/customers, uptime notifications to sysadmins etc.) we needed robust solutions. My first choice was mailgun since I've been a mailgun user since forever (actually 2014), They used to graciously offer 10k emails for free. That changed earlier this year when they decided to discontinue that offer and start charging for all emails. Now, don't get me wrong they're still cheaper than a lot of competitors and offer a dirt cheap pricing, I was unwilling to take that path. Given the fact that I'd have to pay per email anyway, I made up my mind that I'll go with SES. that's one less invoice raised. That is because we're already using AWS S3 for storing our overnight backup. I thought that instead of adding a new biller altogether in our accounts, it's rather better to pay AWS a slightly higher bill based on email volume. Since their pricing is also very identical: mailgun offers $0.80 / 1000 emails in their Pay as you go plan while SES offers $0.10 for every 1,000 emails plus $0.12 per gigabyte (GB) of data in the messages so assuming that we only incur the bare minimum cost (our emails aren't very huge in size so 1GB is the least we'd pay for) We actually save a few pennies by going with SES.


This is a companion discussion topic for the original entry at https://www.tekduke.com/move-to-aws-ses/