We integrate it into our website to get feedback or help the customers after the launch and it was great working using simple email service (SES). It was easy to set up. it is efficient to use. It is very cheap in cost as well. It was a great experience using it
Pros
It very cheap in cost.
it provide efficient monitoring for the quotas of our email limits.
It is very easy to configure set up and handle.
Cons
It is only hard when we need sandbox environment to setup because it is only provide on valid cases.
Likelihood to Recommend
It is difficult to set a Sandbox environment. In the SNS environment, we need to verify all emails we need to send emails and all emails we want to receive an email so it becomes difficult when we integrate it to a website where tons of emails are going to receive in it.
We use Amazon SES to send non-transactional (marketing) emails for our online services. It makes sense for us to keep transactional and non-transactional email routing totally separate, and Amazon SES allows that.
Pros
Deliverability reports
DKIM and Dmarc integration
Ease of integration with non-Amazon infrastructure
Cons
SES handles sending email really well, but receiving email part is very bare-bones. It can forward to HTTP endpoints, but cannot provide industry standard APIs like IMAP.
Likelihood to Recommend
Amazon SES is well-suited for a "do-it-yourself" mass-mailing solution, where fine control over mail delivery is required. Since mail server reputation affects deliverability greatly, and SES has a good reputation, it's a great fit for SMBs: mail server reputation cannot be built overnight. Amazon SES is not a turnkey solution, so significant internal expertise is required, and it cannot be compared to packaged services like Mailchimp.
We use Amazon Simple Email Service to send out email notifications on different scenarios and different triggers like when EC2 shuts down due to crash. We also detect events like memory overflow on EC2, S3 bucket changes, and various fishing attacks on an EC2 instance.
Pros
Sends out email notifications
Pay as you use
Cons
Cannot send emails to unregistered users
Reporting section is weak
Likelihood to Recommend
We use Amazon Simple Email Service to auto-respond to users that submit messages through a contact form. We are using Amazon Simple Email Service with our self hosted python application to send our marketing emails, get feedback for our services, and Hackathons.
Amazon SES is currently being used by our team (Mobile/ IoT) to send customized emails to users in reaction to events.
Pros
It provides a simple syntax to create templates for customized emails
It has a great rate limit once moved out of the sandbox
Nice mechanisms to handle bounce and replies
Cons
The AWS console needs to provide a GUI to create a template for an email rather than developers having to use the CLI or SDKs
The initial sandbox limits are too low for any production application
Likelihood to Recommend
It is best suited for sending customized emails to users in reaction to events from other AWS services. It is less appropriate for just sending out notification emails in which case SNS should be used.
I've used several email service products over the years, mainly SendGrid, MailChimp, and SES. In my role as a consultant, I aim to recommend the best tool for the business problem being solved. While most companies can get away with stock or lightly modified SaaS solutions, if email is absolutely core to your business, I'd recommend Amazon's Simple Email Service. It provides the lowest pricing outside of building up your own sender reputation while providing the same flexibility and performance, especially if your application servers are already in AWS.
Pros
Great pricing
Amazing performance when accessed from inside AWS
Granular API provides great amounts of flexibility
Cons
Improve performance when accessed from outside AWS
Improve web interface capabilities
Likelihood to Recommend
While most companies can get away with stock or lightly modified SaaS solutions, if email is absolutely core to your business, I'd recommend Amazon's Simple Email Service. It provides the lowest pricing outside of building up your own sender reputation, while providing the same flexibility and performance, especially if your application servers are already in AWS.
The drawback to all this power is that you need to dedicate engineering resources to building, modifying, and maintaining your email pipeline. If you can't justify those expenses, go with a SaaS product.
We use Amazon's Simple Email Service to handle sending out important notifications and replies from our ticketing system. When we initially launched we quickly surpassed the volume of email that Google allowed through their SMTP relay, so I quickly set up SES to get our system back up and running. Where Google limited us to sending 2,000 messages a day, SES allowed us to send 12,000 each day, which was more than enough.
Pros
Setup was easy. It does require proof of domain control as well as a human review, but while those items are pending you are able to fully set up the system to be able to run once approval is done and not have to bounce between development and production configurations.
Cons
SES does not seem to have any major issues at the moment, it's an email relay service and it does that job swimmingly.
Likelihood to Recommend
Amazon SES is great for sending bulk mail, particularly notifications. It is not intended for holding a conversation as there is no way to view the mail that has been sent, so unless you are using a third party system that tracks what mail is being sent, such as a ticketing system like Kayako, you would not want to use it for regular communication.
We use Amazon Simple Email Service (SES) in a number of our software products to send large quantities of emails on behalf of our customers. Their support of DKIM allows us to send high-quality emails without worrying as much about spam filters. It has also served as a simple solution for sending SMTP email from various websites (think contact forms and the like) where using the computer's native "sendmail" commands are insufficient.
Pros
Very high send rates. We often send out over 50,000 emails in a matter of minutes (30-40 minutes).
Very simple to authorize email sending from an entire domain.
You get full control of your emails and are not as strictly bound to a set of policies as you would be with an email "platform" like MailChimp. Of course, that means you have to do more legwork too.
Cons
You cannot send embedded images (Base64 encoded) in your emails. This is a pretty big gotcha. So if you want to send images along, it's best to store them externally.
Virtually zero analytics on your emails. It is up to you to implement open detection, click detection etc.
Has no email list storage. That's up to you.
Likelihood to Recommend
SES is truly a "simple" email sender. It's focused on the actual technology behind sending emails, and sending emails that appear that they genuinely come from a specific domain. This is awesome if you've got some developers to implement the technology to make this kind of service valuable. However, if you don't know how to write code to conform to an API, or how DNS records work – steer clear. This is not for the faint of heart.
Our entire organization uses multiple pairs of SMTP credentials from AWS to send all our transactional, marketing, and system monitoring e-mail messages. It makes life for the developers very easy, because they have a single interface to send an e-mail, regardless of the system originating the message.
In addition to its simplicity, the dirt-cheap pricing is almost negligible. The monthly bill for all of our e-mails is roughly $4 per month, and simply cannot be beat by any other SMTP provider.
Pros
DKIM signing for all messages. This absolutely maximizes the probability of a message reaching a user's inbox, and not the spam folder.
API *and* SMTP access, making it possible to connect any system to SES. No matter what programming language or what server, there is always a library for sending e-mail messages that is compatible with SES.
SES makes it trivial to send thousands of e-mails from known mail servers. No longer do you have to worry about your server's IP address being blacklisted because it originated too many e-mails.
Incredible credential management for increased security. With IAM, you can create API keys (or SMTP credentials) for each individual piece of an infrastructure, making debugging very easy.
Cons
For users that are not used to semi-complex APIs, the AWS SDK can be a little intimidating. That said, with the SMTP credential feature, the API learning curve can be avoided.
It is frustrating that you have to verify each e-mail address or domain name (wildcard) you wish to use in the From: header of the e-mail messages. I understand this is a security feature, but for long-time verified accounts, it would be nice to use arbitrary e-mail addresses and domains.
Likelihood to Recommend
As I said before, SES is ideal for outsourcing any and all e-mail message origination. Marketing e-mails, new user signup e-mails, and e-mails that notify engineers of service problems are all excellent use cases for SES. For startups, the fact that you get 10,000 free e-mails, just for signing up, makes it a no-brainer when in the early development stages of writing a program. Once the credentials are loaded into the code, you can forget about e-mail origination forever (almost)!
I use Amazon Simple Email Service (SES) in our organization across various projects to reliably send transactional emails from our applications to our users. The business problems addressed are scale and deliverability - making sure we can send as much as we need to and know it will have the highest chance of avoid user's spam folders.
Pros
Simple API
Easy to setup
Realiable deliverabilty
Cons
I think setup could be even simpler
Provide more in-depth solutions for errors
API key access over IAM stuff would be easier
Likelihood to Recommend
I think Amazon Simple Email Service (SES) is a great option for many projects, but sometimes it's overkill. It's best when you know you need the ability to send high volume. It's also good for when you are sending mail and notifications where high deliverability is a must-have for your project (like invoices, etc).
