Amazon Simple Email Service (Amazon SES) is a great option for businesses that need a flexible and cost-effective email delivery infrastructure. It integrates well with the AWS ecosystem and can handle a wide range of email sending requirements, from transactional notifications to large-scale marketing campaigns.
Having tried several email marketing solutions, I’ve found that SES offers quite a lot of flexibility. However, simply connecting an SMTP server and starting to send campaigns isn’t enough. There are a few things worth paying attention to if you want to optimize your sending infrastructure and keep your SES account healthy.
Here are four areas I would recommend looking into:
- Domain Authentication
- Sending Limits
- Tenant Management
- Bounce & Feedback Handling
1. Domain Authentication
Before sending campaigns, make sure your sending domains are properly verified in Amazon SES. It’s also important to configure DKIM, SPF, and DMARC correctly. These authentication mechanisms help receiving mail servers verify your sending identity and reduce the risk of domain spoofing.
If you’re managing several brands or customers, keeping track of multiple sending domains can become a little tedious. Having a platform that simplifies domain verification and identity management can save quite a bit of operational work.
2. Sending Limits
Amazon SES assigns sending quotas and maximum sending rates to each account, depending on factors such as account status and AWS Region. New accounts also start in the sandbox, where sending is restricted.
Rather than trying to use your full quota immediately, it’s generally better to increase sending volume gradually and monitor your sending reputation along the way.
For multi-user platforms, I would also recommend setting individual sending limits for different users or sending servers. This helps prevent one user’s campaign from unexpectedly consuming the available sending capacity.
3. Tenant Management
This is perhaps one of the more interesting Amazon SES features that doesn’t receive as much attention as it deserves: Tenant Management.
If you’re running an email marketing platform for multiple customers, you may initially connect everyone to the same SES account and share the same sending infrastructure. This works, but it also means that one customer’s poor sending practices could potentially affect resources shared with others.
Amazon SES Tenant Management offers a more structured way to organize sending resources for different customers. Depending on your configuration, you can associate identities, configuration sets, reputation metrics, and suppression policies with individual tenants.
For example, if one customer starts generating an unusually high number of bounces or spam complaints, tenant-level reputation monitoring and policies can help you identify the problem and take appropriate action without treating all customers as one undifferentiated sending group.
Of course, tenant management doesn’t automatically isolate every aspect of an SES account. You’ll still need to configure the relevant resources and policies properly. However, for anyone operating a multi-customer email marketing platform, this is definitely a feature worth exploring.
In my opinion, it’s one of those useful infrastructure features that can make a meaningful difference as your email marketing operation grows.
4. Bounce & Feedback Handling
Another important aspect of running Amazon SES is making sure you properly handle delivery feedback.
SES can provide notifications for hard bounces, soft bounces, spam complaints, and other delivery events through services such as Amazon SNS and Configuration Sets.
These notifications shouldn’t simply be collected and forgotten. Your email marketing application should be able to process them, identify the affected subscribers, and update their statuses accordingly. In particular, hard-bounced and complained addresses should be handled carefully to avoid repeated sending.
If you’re operating a multi-tenant platform, it’s also important to associate each feedback event with the correct customer. Ideally, one customer’s bounce or complaint records should not unnecessarily interfere with another customer’s mailing list.
This may sound like a relatively small technical detail, but it becomes increasingly important when managing multiple customers and large sending volumes.
5. Choose the Right Platform
Amazon SES takes care of email delivery, but you’ll still need an application to manage subscribers, campaigns, automation, scheduling, and sending infrastructure.
There are quite a few options available, depending on your requirements. Mailchimp and Brevo (formerly Sendinblue) are popular hosted platforms, while Sendy and AcelleMail are worth considering if you prefer a self-hosted solution with Amazon SES.
Personally, I find AcelleMail interesting because it supports many of the configurations discussed above directly through its web interface. This includes sending server management, sending limits, multi-tenant capabilities, and automated bounce and complaint handling.
Instead of having to manage every detail separately through the AWS Console, you can handle much of the day-to-day email marketing infrastructure from one place.
You can take a look at AcelleMailAcelleMail if you’re interested in exploring it.
Final Thoughts
Amazon SES provides a solid foundation for email delivery, but maintaining a healthy sending infrastructure involves more than just connecting an account and launching campaigns.
Proper domain authentication, sensible sending limits, tenant management, and automated feedback handling all deserve attention.
If there’s one feature I’d suggest exploring a little further, it’s Tenant Management. It may not be essential for every small sender, but it can be particularly useful when your platform starts serving multiple customers.
And, of course, choosing an email marketing platform that makes these configurations easier to manage can save you a lot of time in the long run.