Sorry, the name of the company escapes me ATM.
AWS is awesome for exactly that reason, one can build a more integrated package on top of the individual parts and sell it.
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.
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.)
Edit, which could also mean a custom interface
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.
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.
and
http://www.hetzner.de/en/hosting/produktmatrix/rootserver-pr...
been with them for 3+ years and never had a problem
At some point, that will change. At that point I'll have a very clear basis for calculating ROI on migrating to different infrastructure.
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.
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.