Email marketers' experiences with Amazon SES for bulk sending are varied. Some find it easy to set up and use, while others note it requires more technical expertise than other platforms. SES's pay-as-you-go pricing is cost-effective for many, especially high-volume senders, but costs can escalate. A strong consensus emphasizes the importance of sender reputation and proper authentication (SPF, DKIM, DMARC) for deliverability. Warming up IPs, monitoring bounce and complaint rates, and requesting increased sending limits from AWS are crucial. SES primarily functions as a transactional email service and lacks some marketing features and customer support found in dedicated platforms. Using dedicated IPs allows senders more control over their reputation.
11 marketer opinions
Email marketers' experiences with Amazon SES for bulk sending vary. While SES offers a cost-effective pay-as-you-go pricing model, its setup and management require more technical expertise than other platforms. Deliverability is heavily dependent on sender reputation and proper authentication, necessitating careful IP warming and monitoring of sending limits, bounce rates, and complaint rates. A potential downside is the limited customer support and the lack of marketing-specific features found in dedicated email marketing platforms, making it primarily a transactional email service.
Marketer view
Email marketer from G2 Crowd reviewer says that a potential downside to using Amazon SES is the lack of readily available customer support. SES primarily focuses on the technical aspects of sending emails, and users looking for more hands-on assistance might find other platforms more suitable.
28 Sep 2021 - G2
Marketer view
Email marketer from Mailjet shares that Amazon SES requires more technical expertise to set up and manage compared to other email marketing services, and that other services have more user-friendly interfaces and features.
9 Jun 2024 - Mailjet.com
4 expert opinions
Experts report generally positive experiences with Amazon SES for bulk sending. Some found it easy to set up and use, and clients have successfully sent high volumes of emails (30K to 100M per day). Maintaining a good sender reputation and ensuring proper email authentication (SPF, DKIM, DMARC) are crucial for deliverability.
Expert view
Expert from Email Geeks shares experiences of clients sending through SES successfully, ranging from 30K to 20M emails per day, with spikes to 100M. Suggests setting up rDNS for dedicated IPs.
10 Oct 2023 - Email Geeks
Expert view
Expert from Email Geeks shares that Amazon SES was easy to set up and use, and they were very happy with it after switching to it when they had issues with their own hosted MTA.
2 Dec 2024 - Email Geeks
4 technical articles
Amazon SES uses initial sending limits to protect its reputation and avoid spam, which can be increased by request. They provide tools to monitor sender reputation via bounce and complaint rates, as high rates negatively impact deliverability. Proper email authentication (SPF, DKIM, DMARC) is vital, and using dedicated IP addresses allows senders to build and maintain their own reputation, especially beneficial for high-volume sending.
Technical article
Documentation from Amazon Web Services explains that Amazon SES provides tools for monitoring your sending reputation, including bounce and complaint rates. High rates can negatively impact deliverability.
13 Oct 2024 - Amazon Web Services
Technical article
Documentation from Amazon Web Services explains that it is important to properly authenticate your emails using SPF, DKIM, and DMARC to improve deliverability and sender reputation when using SES.
17 Feb 2023 - Amazon Web Services
Are there email sending issues with AWS?
How can I manage Feedback-ID headers when using Amazon SES to send emails, especially with Gmail's upcoming sender requirements?
How do I show 'signed by' my domain when using Amazon SES or Mailchimp?
How do Iterable shared infrastructure and Amazon SES handle SPF alignment and DMARC compliance?
How to setup BIMI when sending from Iterable through SES shared pools?
Should I remove DMARC and DKIM records to use Amazon SES shared domain reputation?