Amazon Simple Email Service (SES) Reviews and Ratings

Use Cases and Deployment Scope

We use Amazon Simple Email Service (SES) for sending email related to information, notification, workflow approval, one time password from our self created applications and systems. These emails are rolled out to customers as well as internal teams. As we're on AWS so it is the best suited service for us to use for all these scenarios.

Likelihood to Recommend

This is really easy to integrate and fastest mailing service I have seen till not. Moreover downtime is negligible. Never faced issue with service downtime.

Use Cases and Deployment Scope

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.

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).

Use Cases and Deployment Scope

We were looking for a tool to send bulk promotional and transactional emails without putting them in spam, then we looked over Amazon Simple Email Service (SES). It offers various features which are not simple, as its name sounds. We can use their well-developed SDK to send emails via our server and our domain.

Likelihood to Recommend

Amazon Simple Email Service comes with the bundle of Amazon Web Services (AWS) and it also offers a limited number of emails per month for free. One who has a technical background and wants to send custom emails with custom domains in a professional way can go with Amazon Simple Email Service. If you have no technical background or tech team, it might not be useful for you.

Use Cases and Deployment Scope

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

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.

Use Cases and Deployment Scope

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.

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.

Use Cases and Deployment Scope

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.

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.

Use Cases and Deployment Scope

We use Amazon Simple Email Service (SES) on several client accounts as well as several of our own applications and services. We primarily use Amazon Simple Email Service to send informational emails related to status notifications, important updates, and information requests within different applications and services. We've implemented SES for as many as 50 domains and feel confident when recommending it to clients.

Likelihood to Recommend

Amazon Simple Email Service is an excellent choice for integrating high-volume or important email delivery into an existing application, service, or custom established workflow in your organization. If you have a true development group looking for a seamless way of handling email delivery, this is the right product for you. It's easiest to set up if you're already using other AWS services such as Route53 for DNS but can function as a standalone service. However, if you're expecting a product that was designed to do all of its intended functions from a user interface, that's not what Amazon Simple Email Service was intended to be.

Use Cases and Deployment Scope

We use it to send newsletters from our company. And we have installed it to a lot of clients, integrated with PHP email scripts (that we made ourselves) so they can send emails too. We have users with more than 1 million mails sent per day. It's very useful because delivery is fast and it's easy to integrate with PHP scripts.

Likelihood to Recommend

It's not for spam. They have a limit for bounced emails, so you must have your email lists clean and updated.

Use Cases and Deployment Scope

We decide to use Amazon Simple Email Service for our email service, as we were having all of our infrastructure running in AWS, and we really think this was the best move. Working on a specific web application and we need it to send emails, so for developers was really easy to interact with AWS SDK for implementing the changes. For operation, this was a great option also, as the price is really low, and this is a great plus compare to other services in the market.

Likelihood to Recommend

If you're working with an AWS infrastructure this is the best move, as you will get great benefits from using it and your development team will feel that they know what they're doing. If you're not using AWS, this probably can be a problem, as you will not get the 62,000 emails for free, or developers will feel a little strange working with different technologies.

Use Cases and Deployment Scope

I use SES both internally and for customers. Internally it is used for our website contact forms and other internal applications.

We have used SES with several customers for the past 8 or so years.

SES solves one of the most common annoyances in programming. Email deliverability. With SES (configured correctly) we have no issues with spam filters.

Likelihood to Recommend

SES is great when you have an online form that needs to send email. It's bullet proof and can handle large loads.

I probably wouldn't use SES for a smaller temporary use case. There is configuration needed with SES and potential (tiny) costs.

Generally, I have one configuration that I use for most forms unless I expect high traffic. In that case I keep it separate.