News for hackers. Stuff that matters.
Re:AWS OpsWorks - Flexible Application Management in the Clo... by danielhunt on Tuesday February 19, 2013 @04:37AM (#5243464)
Not only that, but there's no allowance made for micros either.

Also, SSL on a per-app basis is confusing me - does that mean that each box individually is handling SSL termination, or is it done on the loadbalancer side? I have a lot of reading to do before I can really understand what's happening here I think

Re:AWS OpsWorks - Flexible Application Management in the Clo... by devopstom on Tuesday February 19, 2013 @06:25AM (#5243735)
The lack of micro instance is a real shame. I suspect that's because the time taken to do a full chef install run on a micro might be vast.
Re:AWS OpsWorks - Flexible Application Management in the Clo... by pravka on Tuesday February 19, 2013 @09:50AM (#5244528)
I've used t1.micros extensively with chef -- it's not as bad as you might think.
Re:AWS OpsWorks - Flexible Application Management in the Clo... by neonlex on Tuesday February 19, 2013 @04:40AM (#5243472)
ssl is handled on app basis not in the load balancer and by the way, you can hook into everything by rewriting or overwriting the recipes
Re:AWS OpsWorks - Flexible Application Management in the Clo... by danielhunt on Tuesday February 19, 2013 @04:49AM (#5243496)
That's what I figured. It seems odd that they'd be enforcing that approach from the start, though