3 ms·
So, I remember when EC2 didn't have a UI at all: it was just a set of APIs and a handful of command line tools which were mostly for use as a demo. The entire c
by saurik 9y ago
So, I remember when EC2 didn't have a UI at all: it was just a set of APIs and a handful of command line tools which were mostly for use as a demo. The entire concept was that you were either going to use the API directly in order to build a fleet of automatically-scaling servers or you were going to cobble some system management shell scripts together that just ran the command line tools. For some services, a UI really makes sense (like Route 53), but for EC2 a UI is only going to be usable if you want to boot like, a handful of one-off hand-configured machines... that isn't really the use case for EC2. I mean, I do do that, and to be honest I have often used the UI to do it, but the only reason is because searching for the current Ubuntu AMI is easier using the UI... otherwise, using ec2-run-instances is pretty simple, and I frankly shouldn't be doing that as those one-off hand-configured servers are the bane of my existence when it comes to later system maintainability.
It just isn't clear to me what the job of a user interface is to EC2 other than as a kind of fallback / emergency dashboard for when your software loses track of what you have running; it is essentially the Task Manager / Activity Monitor of AWS: a tool you only use when you screwed something up or have to fix something by hand. The kinds of workloads that you do with EC2 just don't map well to a UI without some kind of deep framework integration (such as "understand enough about my database server stack to determine that I've run out of connections in order to trigger an autoscaling event"; the way you'd normally do that is by building a custom CloudWatch metric with a daemon on your database server, at which point the software you wrote is probably handling that <- if what you are looking for is so specific, you usually want to be using a more dedicated/SaaS part of AWS or using a service like Heroku that is built on top of AWS).
I guess maybe the disconnect is that you seem to feel like "smaller dedicated and VPS providers" are a competitor to EC2, when in my mind the entire reason someone would use EC2 is because they need to do something you fundamentally could never do before using those existing services: automatically provision as many machines as you want, all of which become available within minutes, and where you can turn off machines you don't need and be build in by-the-hour increments. That was just fundamentally never possible before, which meant for the kinds of use cases for which EC2 was designed (workloads with high variance, whether temporary high-throughput batch jobs against data stored in S3 or services that have periodic or even unpredictable usage) they could be charging three or four times as much as their competition and you'd still use them, as to use their competitors you'd have to have five times as many servers constantly all doing nothing but burning cash.
- Terretta 9y agoYour comment is so important to grokking and exploiting the full value of public cloud. I happened to be on the front row at re:Invent listening to Andy Jassy’s keynote with another AWS Customer Advisory Board member who has used EC2 since launch. We joked it might be dangerous to drink a shot every time Jassy said “just click” or “with a click of a mouse”. As believers in the value of repeatable declarative “infrastructure as code”, we were dismayed at the increasing tendency to prioritize “AWS Console” web UIs over APIs for a number of AWS capabilities.
- deleted 9y ago[deleted]