News for hackers. Stuff that matters.
Re:Introducing Amazon Simple Email Service by DanielBMarkham on Tuesday January 25, 2011 @07:53AM (#2138859)
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 bunches of docs to read to get up to speed. Each has it's own forum category. Each has a usage policy.

Don't get me wrong -- it's all good stuff. But good luck trying to guestimate what kinds of prices you'll be paying. You're paying for data transfer in and out of the cloud, you're paying for disk storage, you're paying for a database, you're paying for basic email services, etc.

So I'm kind of stuck looking at the monthly bill and saying "Does this look about right?" instead of having some firm idea of what's going on without having to use a spreadsheet and 3 whiteboards. That's no good. It's probably completely acceptable for BigCorp, who has a guy dedicated to figuring all of this out and managing it, but I'm busy and pressed for time all I want is the big red button to push -- and a known price for pushing it.

I love what they're doing. Just wish they'd put a little more "simple" back into it, especially in terms of pricing and bundling.

Re:Introducing Amazon Simple Email Service by plusbryan on Tuesday January 25, 2011 @09:51AM (#2139210)
You think that's complicated? Boy, back in my day, we didn't have no fancy "management console" or "tabs". Why, you had to play with your AWS services by hand! And you liked it.
Re:Introducing Amazon Simple Email Service by subbu on Tuesday January 25, 2011 @10:53AM (#2139465)
Wanted: A webapp/dashboard that tracks money you have spent acorss Amazon services.
Re:Introducing Amazon Simple Email Service by frisco on Tuesday January 25, 2011 @12:01PM (#2139780)
Re:Introducing Amazon Simple Email Service by anonymous246 on Tuesday January 25, 2011 @01:22PM (#2140183)
There is actually a company that does this. But since Amazon doesn't do OAuth, they require you to give them your amazon login and password. They download your account usage logs from amazon and put a GUI over it. The password requirement was a showstopper for me so I didn't even try the co. The graphs sure looked pretty. :)

Sorry, the name of the company escapes me ATM.

Re:Introducing Amazon Simple Email Service by joseakle on Wednesday January 26, 2011 @01:21AM (#2142376)
ylastic.com
Re:Introducing Amazon Simple Email Service by easp on Tuesday January 25, 2011 @12:06PM (#2139796)
Which was still infinitely better than racking your own servers and then, later, driving to the colo at 4:30 am because of yet another contingency you failed to anticipate in your HA planning. One of the earlier contingencies was that the colo's "remote hands" service was actually staffed by bonobos.
Re:Introducing Amazon Simple Email Service by kevin_morrill on Tuesday January 25, 2011 @08:14AM (#2138899)
Seems like a white labeling opportunity. Though I am not sure if their TOS allows it.
Re:Introducing Amazon Simple Email Service by sofuture on Tuesday January 25, 2011 @09:11AM (#2139057)
See: Heroku

AWS is awesome for exactly that reason, one can build a more integrated package on top of the individual parts and sell it.

Re:Introducing Amazon Simple Email Service by charlesju on Tuesday January 25, 2011 @12:48PM (#2140037)
Or dropbox...
Re:Introducing Amazon Simple Email Service by ez77 on Tuesday January 25, 2011 @08:58AM (#2139016)
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 by detst on Tuesday January 25, 2011 @09:03AM (#2139031)
"White label" in this context would basically be a middleman. Customer pays the white label for the AWS services and the white label pays AWS.

The white label would obviously have to offer something of value and in this discussion, that value would be predictable pricing and maybe simplification of the services.

Re:Introducing Amazon Simple Email Service by corin_ on Tuesday January 25, 2011 @12:55PM (#2140060)
Actually white label doesn't quite describe it correctly, as white label is normally just that - a relabelling.

Typically, in addition to releasing it as a different brand for the same services, pricing might be altered, customer service would be seperate, different marketing, and so on. It's not a term designed for creating a new service that happens to use AWS underneath it.

(Depending on how much the "simplification of the services" changes the AWS offering, maybe I'm being pedantic, but maybe not. Dropbox, for example, is not a white label solution, it's a completely seperate example, even if it 100% uses AWS services.)

Re:Introducing Amazon Simple Email Service by ez77 on Tuesday January 25, 2011 @10:30AM (#2139376)
Thank you and jrnkntl (edit: and alttab) for explaining it.
Re:Introducing Amazon Simple Email Service by jrnkntl on Tuesday January 25, 2011 @09:02AM (#2139025)
Resell services under another name, maybe in another package. In this particular case, with a fixed price :)
Re:Introducing Amazon Simple Email Service by executive on Tuesday January 25, 2011 @09:06AM (#2139039)
Sendgrid is essentially an Amazon white label e-mail service now.
Re:Introducing Amazon Simple Email Service by alttab on Tuesday January 25, 2011 @09:01AM (#2139019)
I think white label here means manage and package aws services under one bill

Edit, which could also mean a custom interface

Re:Introducing Amazon Simple Email Service by ajju on Tuesday January 25, 2011 @09:54AM (#2139220)
Seriously, the lack of a flat fee model is the main thing that has kept me away from AWS.
Re:Introducing Amazon Simple Email Service by sofuture on Tuesday January 25, 2011 @10:23AM (#2139340)
That's the point, though: usage driven fees. It's absolutely not the most economical offering, but the freedom and ability to either quadruple your infrastructure or shut it down entirely, no strings attached, in an instant is what you're paying for.
Re:Introducing Amazon Simple Email Service by anto1ne on Tuesday January 25, 2011 @12:10PM (#2139824)
With most of dedicated server providers now, you can get any server with a 1 month contract, no strings attached, for a fraction of the price of an equivalent ec2 instance, and good IO as a bonus. And good providers usually delivers within 24h.

I love aws services and use them myself, but for ec2, but I doubt most users have such volatile needs. The main advantage I see, for aws users (non ec2) is to have everything in the same place.

Re:Introducing Amazon Simple Email Service by zmmmmm on Tuesday January 25, 2011 @05:37PM (#2141247)
> With most of dedicated server providers now, you can get any server with a 1 month contract

Still not really the point. You're going to have to buy enough servers in advance to handle your peak load every month. And then you're going to have to forecast ahead at the end of the month and cancel all the ones you don't need. It might be theoretically possible but in practice it is ridiculous. EC2 brings the contract interval to 1 hour and lets you control it with API calls.

Re:Introducing Amazon Simple Email Service by Titanous on Tuesday January 25, 2011 @09:29PM (#2141845)
http://newservers.com/ does hourly-billed, API provisioned, dedicated servers.
Re:Introducing Amazon Simple Email Service by rapind on Tuesday January 25, 2011 @01:37PM (#2140244)
I would love it if you could provide a link to your cheaper for more service providers. I've not found anything comparable for less $. Also, if you're comparing lock-in prices, compare them against the EC2 reserved instance prices.
Re:Introducing Amazon Simple Email Service by boundlessdreamz on Tuesday January 25, 2011 @02:07PM (#2140372)
Re:Introducing Amazon Simple Email Service by rapind on Wednesday January 26, 2011 @06:38PM (#2145811)
They look great. Too bad they're in Germany :(
Re:Introducing Amazon Simple Email Service by kmg on Wednesday January 26, 2011 @01:58AM (#2142437)
Yeah another shout for hetzner http://www.hetzner.de/en/, their eq line is pretty good value for money http://www.hetzner.de/en/hosting/produktmatrix/rootserver-pr...
Re:Introducing Amazon Simple Email Service by jolan on Tuesday January 25, 2011 @04:24PM (#2140937)
Re:Introducing Amazon Simple Email Service by rapind on Wednesday January 26, 2011 @06:40PM (#2145820)
Interesting pricing breakdown (reminds me of Heroku), however they seem to be more expensive than Linode and definitely more than EC2.
Re:Introducing Amazon Simple Email Service by jolan on Thursday January 27, 2011 @04:32PM (#2149582)
They're cheaper than both for bandwidth which is what I care about most.
Re:Introducing Amazon Simple Email Service by ericd on Tuesday January 25, 2011 @02:34PM (#2140482)
serverbeach has dual quad-core servers with 6-48 gigs of RAM for relatively reasonable prices, month to month.
Re:Introducing Amazon Simple Email Service by rapind on Wednesday January 26, 2011 @06:37PM (#2145810)
I used to use serverbeach. They are definitely not cheaper if you compare RAM to RAM (just under 2x the cost of EC2 reserved), but of course they're dedicated not VPS, which is a better offering... not sure how much more their cheapest dedicated boxes are worth in comparison to an ec2 small instance though.
Re:Introducing Amazon Simple Email Service by Groxx on Tuesday January 25, 2011 @03:15PM (#2140640)
How about research uses? That kind of computing power is almost entirely un-buyable at the short terms many research needs have. You buy a month, or you buy nothing. EC2: you buy a minute, if that's all you need.
Re:Introducing Amazon Simple Email Service by wahnfrieden on Tuesday January 25, 2011 @10:42AM (#2139414)
Many companies will resell space to you on AWS with a flat fee model. Many hosts now are simply AWS front-ends.
Re:Introducing Amazon Simple Email Service by easp on Tuesday January 25, 2011 @12:09PM (#2139820)
In my limited experience, the actual costs have been small enough that I regret even spending time on a detailed spreadsheet based cost model to predict costs.

At some point, that will change. At that point I'll have a very clear basis for calculating ROI on migrating to different infrastructure.

Re:Introducing Amazon Simple Email Service by Travis on Tuesday January 25, 2011 @12:53PM (#2140052)
On the other hand, because of the utility-based charges, you can run tests for a week or two if you'd like.

Also, it sounds like what you're looking for is basically a calculator on top of the service -- are there really no decent calculators online?

I think Elastic Beanstalk is intended to reduce much of this complexity, as well. Want your app to just scale? clicks on EBeanstalk.