Hacker News Reader

You answered the questions on exactly what is wrong with the console...

How so? Op is correct - you shouldn’t be using the console to actively manage your infrastructure. The consoles primary purpose is to let you quickly spin up resources while you explore. If you have a real business use case, all your infrastructure should be defined in configuration and deployed out to AWS. That way, you always know what you need to spin up and it’s exact, specific configuration, all stored in source control.

Because when you do that nothing ever needs tweaked on the fly? Because issues of load and scale aren't often times emergent?

I am not making an argument against what you are saying. I am saying that a common interface between the two would be the sane and rational decision. It should be trivial to use the console and turn that back into your new behavior for committing back to your repository.

"The consoles primary purpose is to let you quickly spin up resources while you explore."

And it's pretty bad at this.

I'm not saying the interfaces are the worst ever invented, just that they are a step above internal enterprise software, and despite the fact that AWS makes almost 8 BILLION DOLLARS there appears to be less that 1/1000th of that revenue invested in improving it.

Reply on news.ycombinator.com