Amazon Simple Email Service（SES）の評判・口コミ 全16件

What do you dislike?

It is really lengthy process to get help for this product and have to wait bit long to contact the customer care. If that can be improved then this tool is the best.

What do you like best?

It is one of the beat mass email service out there. It has really simple user interface and other amazing thing about this tool is that it is really cheap as usual amazon products are.

Recommendations to others considering the product

I would recomment all the comapnies which are doing mass email or email marketing.

What do you dislike?

Lack of functionality of advanced transactional email service, such as template editing.

What do you like best?

The robustness of the service. The cheap pricing.

Recommendations to others considering the product

If you just want to send out emails, or receive some to your s3 while providing the content and managing it yourself, this is a basic cheap solution. Most of the times, I need more. Use it only for high volume transactional email sending for a very cheap pricing.

What do you dislike?

I don't like how the emails sometimes take a long time to send or receive, and sometimes notifications take a few hours (longer than expected) to sync.

What do you like best?

The fact that it loads fast and has a slick UI and has an inexpensive pricing plan. Also it seems to be just as reliable if not more reliable than other email services such as Gmail (server almost never down).

Recommendations to others considering the product

You can use this if your current email provider isn't very good. This product may be beneficial if you want a highly scalable, reliable, and inexpensive email service.

What do you dislike?

No transactional support, no support for read receipts. No support for templates (we use this with SendWithUs).

What do you like best?

Very fast and reliable. Easy to add in our own domains, even with DKIM support.

Recommendations to others considering the product

Don't forget to get approved for Production mode before you turn it live, or you will be quickly limited in how much you can send out to clients. Also don't forget to check the DKIM settings to prevent your emails from being marked as spam.

What do you dislike?

Steep learning curve at first and Amazon documentation is seriously the worst in the industry, like severely the worst, seriously.

What do you like best?

The way I can simply create a user group for logging purposes or server monitoring purposes. We can blast out emails to see if our EC2 instances have gone down or a Docker goes down or an app is blowing up.

Recommendations to others considering the product

Use it, it's easier than configuring your own sendmail.

What do you dislike?

Their UI is useful for tracking, but not for creating the campaigns or managing lists, it's designed for transactional email. This is easily fixed by using a self-hosted solution like Sendy.co, but it's not as easy to use as MailChimp for example.

What do you like best?

Price and deliverability. It just works and they are way cheaper than MailChimp. If you're sending a lot of campaigns or you have a huge mailing list, you can save a lot of money for exactly the same. Also it's great because you only pay exactly what you're using, no monthly plans.

Recommendations to others considering the product

If you're just starting, and only have just a few subscribers, it doesn't worth the hassle to set it up, just go with MailChimp or any other ready and easy to use solution. But if you already have thousands of subscribers, or if you're sending a lot of transactional emails, Amazon SES is the way to go.

What do you dislike?

The major complaint is SES is (almost) totally self-managed and they don't provide tools to add to the values external to the core product functionality. For instance, they don't provide email logs from which you can debug your scripts or server config. They also don't provide newsletter templates or management tools that can make your life really easy. For newsletters, we ended up creating the template and test it out in Mailchimp, before we use it with SES in production.

I really hope they can provide some additional features to simplify a lot of things for you.

What do you like best?

- The flexibility of sending emails from various products using the same email address, without the necessity of having the same domain for the product and the email address.

- Allow you to perform basic verification and add DKIM signing to the domain. You can verify by domain or email. If you don't or can't sign DKIM, SES still sends out your email but it may end up in somebody's Spam folder or being shielded by institutional firewalls.

- The flexibility of doing mail relay from the server or the code level. You can configure Postfix and make sure all emails are relayed via AWS SES. You can also write emailing class in Python, PHP, etc. which utilizes the SES API to send emails without dealing with Postfix.

- Highly responsive and efficient. Sending large batches of newsletter queues to SES has never been a problem. And delegated emails are usually received instantly.

- Official documentations are pretty good. Follow the tutorial and you can setup your mail relay quickly and verify your email or website domain.

- The SES support actually watches your back for you. Because they care about the bounce rate which affect their reputation, they monitor your bounce rate. I work at a large institution and the unit had never cared about the bounce rate until one day we were told our SES service was throttled due to high bounce rates (>40%). So we had to clean up our database's client table which had not been cleaned for maybe 10 years. This kind of instances have happened multiple times, and I was glad secretly because it in effect obliges the administrative to care about their service quality and user experience.

- Can hook up with other AWS or non-AWS services to send out automatic notifications. For example, we are sending automatic emails via SES whenever our website is down, newsletter (also sent via SES) is bounced, an Elastic Transcoder job is done, etc. These are setup via AWS SNS. It's also totally possible to automate whatever email sending by utilizing the SES API. You can accomplish virtually anything you want.

Recommendations to others considering the product

Requires basic experience with servers and domain certificates to get SES running quickly. To use advanced features (e.g. via AWS SNS or utilizing the SES API), more experiences are needed. If you are a startup and don't want to invest lots of time to get the newsletters sent, probably you should first look at Mailchimp or other similar "dummy-proof" solutions.

What do you dislike?

I don't have anything to dislike this service. It's so good

What do you like best?

It's easy to configure and easy to use. I like to use Amazon SES to send instituitional emails from systems I use.

Recommendations to others considering the product

They have a great integration with Amazon Web Services, but it's no need to use all services from Amazon, we can use with any services.

What do you dislike?

I'd like to be able to see raw logs of emails being sent, possibly through CloudWatch.

What do you like best?

I really like the way domain authentication is handled; being integrated with Route53 makes setup and verification pretty quick, and it's possible to allow other AWS accounts to use SES to send emails for verified domains, with a very granular control over permissions (through IAM)

Recommendations to others considering the product

If you're using AWS, there's no reason you shouldn't consider SES over any other transaction email system, particularly if you're concerned about security.