Amazon Beefs Up Its Cloud Ahead of MS Announcement
Amazon has announced several major improvements to its EC2 service for cloud computing. The service is now in production (no longer beta); it offers a service-level agreement; and Windows and SQL Server are available in beta form. ZDNet points out that all this news is intended to take some wind out of Microsoft's sails as MS is expected to introduce its own cloud services next week at its Professional Developers Conference.
Though I've long admired Amazon's EC2 platform, Spamhaus evidentally considers it a hive of spammers.
[...]and Windows and SQL Server are available in beta form[...]
As to anybody else. Where is this news?
What exactly is "cloud computing"?
I've read several articles and websites and still don't understand what the hell this mysterious new "cloud computing" thing is.
It can't just be me, can it?
Cloud is dense vapor high above you.
Patents Drive Free Software as Hurricanes Drive Construction Industry
As seen here:
For normal instances, Windows is 25% more expensive then Linux/UNIX, and for high CPU instances 50% it is 50% more expensive.
Desktop-computer sellers should learn something from that...
Though I've long admired Amazon's EC2 platform, Spamhaus evidentally considers it a hive of spammers.
Well, of course, haven't you read the terms of use. They've got this great section on indemnification where they wash their hands of any responsibilities from their users.
I could see a really bad pattern of someone approaching Amazon with claims of spamming and Amazon saying that they notified the user of improper behavior and that they are not liable for it.
Thank god they claim you shouldn't be able to do this though:
4.2. Restricted Uses Generally.
4.2.1. You may not interfere or attempt to interfere in any manner with the functionality or proper working of the Services.
4.2.2. You may not compile or use the Amazon Properties or any other information obtained through the Services for the purpose of direct marketing, spamming, unsolicited contacting of sellers or customers, or other impermissible advertising, marketing or other activities, including, without limitation, any activities that violate anti-spamming laws and regulations.
4.2.3. You may not remove, obscure, or alter any notice of any Mark, or other intellectual property or proprietary right designation appearing on or contained within the Services or on any Amazon Properties.
4.2.4. Subject to the terms and conditions of this Agreement, you may generally publicize your use of the Services; however, you may not issue any press release with respect to the Services or this Agreement without our prior written consent.
So really you should see these things get fixed ASAP. Should. I bet spammers are just as good as avoiding being shutdown at EC2 as they are anywhere else.
My work here is dung.
Or cloudy beef? Why have to choose, when you can have FLORG? FLORG is the future, FLORG is technology that allows YOU to be YOU! Also SPACE PANTS
"The service is now in production (no longer beta)"
Then they have already reached a state that Google will never achieve.
Better known as 318230.
Sorry, but I am still creeped out by the concept of keeping your data offsite, allowing a third party to control not only your data integrity, but its privacy, AND the cost structure of accessing/maintaining it. Seems like a very unhealthy dependency.
They win either way. Amazon is paying out the nose for Windows licenses to host their Windows and MSSQL "cloud" services. They can't compete with Microsoft on price there, because Microsoft doesn't have to pay to license its own products.
Having another successful vendor offering Microsoft-hosted services is only good for Microsoft. What would be bad news would be if Amazon dug in and did not offer MS-hosted services, and instead pushed only bridge or transitioning services to poach Microsoft-hosted customers to its own platform.
corporations compete for business; film at 11.
Good people go to bed earlier.
After reading the SLA at http://aws.amazon.com/ec2-sla/, I see it as all a big show with no real guts behind it:
# Availability is averaged over the last 365 days, but you only get credit for the current month's costs.
# You only get a service credit for 10% of the current month's costs. If you decide to move your business elsewhere, you may not apply the credit toward any past charges, including for the month in which the outage occurred.
# Availability refers to the "region" availability, and makes no guarantees about instance (computer) reliability, storage consistency/reliability. As far as I can imagine, it might be rather hard to figure out what constitutes a region's "availability" independently. The official measure stated in the SLA is basically a measurement made solely by Amazon.
# To receive any of this pathetic service credit (again, it is not a refund), you are required to send Amazon an email documenting (dates, times, regions) and providing evidence (heartbeat request logs, etc). *Yes, they want logs.* For almost all of their customers, the time and effort involved in filing a claim would outweigh the benefit of the credit.
It's not just the remote hosting that's appealing - it's the scalability.
If I write an app and put it on a dedicated host, I'm okay until I exceed the capacity of that host. Then I have to find another box or boxes and I may even have to change my software since I had assumed it would only be on one server. Finding additional capacity, refactoring and load balancing not only add cost, but effort (and therefore time).
On a service like EC2 (or even Google Apps), I'm renting space on the massive infrastructure of Amazon or Google. Their frameworks restrict you from developing anything that can only run on a single server. And if I need more capacity, I just right a bigger check that month.
That scalability goes for bandwidth as well. If you poke around the internet, you'll find lots of folks using Amazon's storage service for that reason.
"Yes, that is a problem, and we are working on it".
In a cloud setting, your application doesn't run on a single machine. It typically runs on a bunch of them.
The first popular examples of these were applications like Seti@Home where thousands of machines (a cloud of machines) help search for ET.
The variable number of machines is probably a typical trait of a cloud computing application.
Typically, a lot of machines are available if you want them and in the case of Amazon they are even virtual machines, not real boxes.
News about the Kettle Open Source project: on my blog
Wonder how well that works out. Is there any law preventing Microsoft from tweaking cost of future CALs to Amazon in light of the competition?
"Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
I'm sure Microsoft will be terribly upset about Amazon selling Windows VMs in huge numbers.
Speaking of which, I bet the licensing for this was rather complex.
Paul Leader
While most of what you say is true, that particular statement is not. EC2 provides a virtual machine, running the operating system of your choice - anything you could do on your single co-located server, you can do on an EC2 machine.
Amazon has said very little clearly about who is paying for the Windows license in the VM, and what situations you can replicate a Windows VM in.
What they wish you could do and what Microsoft allows you to do (given the need to change SIDs and machine names, and the fact that a VLK can't be used in that scenario) means Amazon is punting license compliance onto the end user who will likely not be able to do what they wish they could do.
In the performance throughput of BSOD generation metrics.
Deleted
Although the law is motivating enterprises to keep e-mail in reliable archival systems, confidentiality concerns suggest a preference for record-retention systems to be in-house rather than in the cloud. On the topic of enterprise confidentiality in the cloud, stay tuned to commentary in the legal community. The topic merits careful review and more analysis. --Ben http://hack-igations.blogspot.com/2008/02/collaboration-e-discovery-and-record.html
Benjamin Wright, Dallas, Texas, benjaminwright.us
I was going to use it for sending a lot of emails (closed-loop confirmed opt-in, not spam. We just have a million customers and they like alerts for certain types of sales), but the spamhaus listing ruins that.
Still useful for some things, but it can't sub in for normal IP space if they can't handle the spam thing.
Maybe amazon can maintain a spam-free block where you post a bond before you can use it.
While most of what you say is true, that particular statement is not. EC2 provides a virtual machine, running the operating system of your choice - anything you could do on your single co-located server, you can do on an EC2 machine.
There are heaps of limitations compared to dedicated machines. Check out the Amazon forums, and you'll be surprised how far you'll be from getting the full sensation of the real thing.
You can for example only have 1 static public IP per instance. Bad for hosting multiple Web apps with SSL on each domain.
Load balancing multiple instances is also a bitch.
We considered it seriously for a high-volume high-availability Web site project, but kept running into dealbreaking limitations, and some we just happened to stumble upon during testing. Minor things that suddenly turn incredibly difficult to solve.
Add to that the cost.. In our cost comparisons we found EC2 costing the same or more than managed dedicated servers with tier 1 providers.
There's no question EC2, VMWare and other "cloud" platforms will be highly attractive, but not yet.
on page: www.bbc.co.uk/weather/weatherwise/glossary/c.shtml
"A structure formed in the lower atmosphere by condensed water vapour and ice particles."
In other words just what i said...
Patents Drive Free Software as Hurricanes Drive Construction Industry
It's been a big week for news about MS: good news, generally. Most of it was not about Microsoft: can we find a new abbreviation for them? I know M$ has already been tried, but Multiple Sclerosis has been around a bit longer than Bill Gates has. The current state of MS research and treatment is IMHO far more interesting than anything coming out of Redmond these days...
(this is not a
For normal instances, Windows is 25% more expensive then Linux/UNIX, and for high CPU instances 50% it is 50% more expensive.
Desktop-computer sellers should learn something from that...
Ummm.. Did you read the summary?
Microsoft is releasing a competing platform next week. Do you really think that Amazon got a great deal on their Windows licensing?
Apples, meet Oranges.
They don't grade fathers, but if your daughter's a stripper, you fucked up. --Chris Rock
Add to that the cost.. In our cost comparisons we found EC2 costing the same or more than managed dedicated servers with tier 1 providers.
BAM! That's what turned me off of Amazon as well. Anything they can do, I can do cheaper elsewhere with "conventional" servers. There are literally hundreds if not thousands of hosting companies just dying to lease you a $49/mo dedicated server that runs circles around any EC2 VPS, and most of them have at least 500gb of traffic included in the base price.
For ~$150 I have 10mbit unmetered, on a dual-core Xeon. Actually I have several, with reverse proxies and what-have-you, just like the Amazon cats do when they want to scale. The big differences are: I have static IPs, and my costs are lower. I am at risk of hardware failures, but then again I can afford an extra box or two for redundancy/backups.
I could see EC2 being worthwhile for small or short-lived jobs, but the moment you start talking about multiple instances and pound/squid nodes, you might as well move to a dedicated box.
-Billco, Fnarg.com
"I have static IPs"
Amazon has offered "Elastic IPs" for quite some time. Once you request an IP address it is yours until you release. It doesn't have to be assigned a particular instance.
The key difference is that you pay for an Amazon instance only as long as it is turned on. If you use dynamic or scheduled scaling (if you have predictable traffic patterns) you can scale up or down your servers as you need. You only pay for the time they are turned on. Obviously it completely depends on the type of application you are running as to whether or not this is an advantage.
Sometimes my arms bend back.
Someone finally defined teh Cloud
Your definition of "cheap" amuses me.
Thing is, your dying "$49/month" hosting companies tend to suddenly become *very* expensive when and if you need to scale.
In reality the common route is indeed to start out on such a discounter, until it assplodes. And then rent a rack somewhere, fill it with own hardware and move as fast as you can.
Compared to *this* route (which many startups can sing a song about) the amazon prices don't look so hefty anymore.
And frankly, it is definately that part of the scalability story that you should watch out for.
What does it matter whether you pay $49/month or ~$90/month (amazon) during the early days?
I don't think those $600 bucks that you may save in the first year will ease you much when you get to spent 5 digits on hardware to handle load spikes that, on amazon, would only cost you a few hundred bucks each...
"Condensation is the change in matter of a substance to a denser phase"
So, yeah.
Patents Drive Free Software as Hurricanes Drive Construction Industry
That's funny, I've been scaling for years, and my host has been around since the last 90's.
I don't deal in anything that has such dramatic spikes as to discredit my system. I'm perfectly comfortable with the fact that my machines are 80% idle during off-peak times. I'm far more concerned with issues like network congestion and Apache hogging because my traffic is bandwidth-bound, not CPU bound.
Just because all the kids today are writing hungry RoR apps, doesn't mean I'm bound by such ridiculous bottlenecks. Just one of my boxes can serve roughly 100 requests per second, which is why I have to use squid frontends, else the clients end up tying all my Apache threads waiting to finish.
Designing my app to be easily distributed means I can scale Google-style, by adding cheap servers as needed. I also spread out my servers geographically around the globe, with plentiful bandwidth at each location. With EC2, you're sharing the pipe with everyone else. You can't get dedicated bandwidth, and from what I've seen the capacity just isn't there (yet?).
Yes, I'm talking about serving pr0n. Next question.
-Billco, Fnarg.com
I don't see why you think that ec2 should be discredited as a whole based on a use-case that they're not even remotely targeting?
Ec2 is for application hosting or number crunching. Static content (like porn) is the job for a CDN. Ec2 is not a CDN.
And honestly, claiming you are bandwidth bound, using apache and serving a miserable 100 hits/sec per node all in the same paragraph does not help your credibility much.
You're either doing it really, really wrong (cf. epic fail) or you're just trying to sound important without having ever really touched a large scale system.
For reference, an async-io server like nginx, lighty, zeus or similar will easily saturate a Gbit uplink on moderate hardware, either with small files (then it will push upwards of 1000 reqs/sec) or with large files (then your "100 reqs/sec"-statement makes even less sense). Sorry, but thanks for playing.