Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Amazon Simple Email Service

aws.amazon.com

Post reply on HN
Print view View original

41–50 of 177 posts

Re: Introducing Amazon Simple Email Service

#41

Post by watchandwait »

ordinaryman wrote: post #34

Seems Amazon wants to fight it out with Google, by matching the new services with Google App Engine's free quota. $0.10 per thousand in SES -> $0.0001 per email recipient // Same as in GAE. You can send 2,000 messages for free each day when you call Amazon SES from an Amazon EC2 instance directly or through AWS Elastic Beanstalk. // Same as in GAE. This, along with the recent AWS Elastic Beanstalk release and Amazon'…

It will be interesting to see how Gmail treats email messages from Amazon SES.

Re: Introducing Amazon Simple Email Service

#42

Post by megaman821 »

eli wrote: post #25
leftnode wrote: post #16

I'm not so sure Sendgrid, Postmark, and other email senders should be shaking in their boots. There's plenty of other businesses that leverage AWS technology and resell it for a higher price. I bet they add AWS as an option as a value added reseller. If you have an existing email host integrated throughout your site, it might make more sense to just stick with them. It will force them to lower their prices though.

Agreed. I use Silverpop for high-volume sends even though I pretty sure they're just a front-end for PowerMTA

We used to use SilverPop but then we just bought a PowerMTA license and wrote our own front end. If you are a small company with a large list, SilverPop is too expensive. Amazon is cheap but it doesn't look like it has any mailmerge (email personalization) capabilities.

Re: Introducing Amazon Simple Email Service

#44

Post by ordinaryman »

ordinaryman wrote: post #34

Seems Amazon wants to fight it out with Google, by matching the new services with Google App Engine's free quota. $0.10 per thousand in SES -> $0.0001 per email recipient // Same as in GAE. You can send 2,000 messages for free each day when you call Amazon SES from an Amazon EC2 instance directly or through AWS Elastic Beanstalk. // Same as in GAE. This, along with the recent AWS Elastic Beanstalk release and Amazon'…

To add to it, it is not that I want to switch from GAE to AWS now. But, to know that it will be easier in case I need to, makes it good news.

I also believe competition which facilitates such migrations not only validates the space and the standard (write for GAE, you can host it on Google or on AWS), but also helps drive innovation and service levels.

Re: Introducing Amazon Simple Email Service

#45

Post by boundlessdreamz »

aristidb wrote: post #20

So I was immediately looking at their REST API... And true to form, Amazon adds yet another slightly incompatible request signing method. Consistency is for wimps.

You can easily integrate it with postfix

http://docs.amazonwebservices.com/ses/latest/DeveloperGuide/...

That is awesome. So even without third part libs supporting this API I will be able to use this service

Re: Introducing Amazon Simple Email Service

#46

Post by arikfr »

markessien wrote: post #7

Sendgrid & other such senders will be shaking in their shoes now. Personally, as soon as I have more time, I'll switch to the amazon service. Also, any new app I make will use Amazons service by default. Sending email out is quite important for growth, and such services really help businesses. What impresses me about amazon is that they are not looking at what the competition is charging or trying to charge high base…

I think they aligned their prices with Google App Engine (they charge the same $0.1 per 1000).

Why are you going to switch from the other providers to Amazon? Because of price?

Re: Introducing Amazon Simple Email Service

#48

Post by pilif »

I wonder who's going to be the first to announce a SMTP proxy for this?

More seriously:

While I can kind of understand that Amazon has their API and probably wants this to work similarly, but there is already a wide-spread protocol for sending out email (SMTP) and I just can't understand why they can't provide an endpoint for that.

Many applications which I really see making use of this already have built-in SMTP support (and are using that today), so why force developers to work with another, completely different API to send email over Amazon?

Re: Introducing Amazon Simple Email Service

#49

Post by ez77 »

kevin_morrill wrote: post #31
DanielBMarkham wrote: post #28

I love what Amazon is doing with AWS, and I like this new service a lot. Plus I'm a happy customer. But damn this is all getting very complicated. First they turn off email, so you have to find a provider, then they turn it back on, but you have to pay them. Looking at my AWS console, I've got 8 or 9 tabs on there -- each representing a little piece of what I might want in an app. Each has it's own help section with…

Seems like a white labeling opportunity. Though I am not sure if their TOS allows it.

Could anyone explain the usage of 'white label' here? The Wikipedia entry (+) doesn't help this foreign speaker.

(+) http://en.wikipedia.org/wiki/White-label_product

Re: Introducing Amazon Simple Email Service

#50

Post by alttab »

kevin_morrill wrote: post #31
DanielBMarkham wrote: post #28

I love what Amazon is doing with AWS, and I like this new service a lot. Plus I'm a happy customer. But damn this is all getting very complicated. First they turn off email, so you have to find a provider, then they turn it back on, but you have to pay them. Looking at my AWS console, I've got 8 or 9 tabs on there -- each representing a little piece of what I might want in an app. Each has it's own help section with…

Seems like a white labeling opportunity. Though I am not sure if their TOS allows it.

I think white label here means manage and package aws services under one bill

Edit, which could also mean a custom interface

Post reply on HN