3 ms·
Until you need to do one thing outside the Beanstalk pattern, then you're dealing with CloudFormation templates all the time.
by mentat 11y ago
Until you need to do one thing outside the Beanstalk pattern, then you're dealing with CloudFormation templates all the time.
- dfsegoat 11y agoNo. You learn to use it just like you would a normal linux box - or you use their managed container service which is basically plug and play with docker compose.
- mentat 11y agoActually you don't or else you break the whole scaling / immutability model. I'm talking from production experience here. I ended up moving to OpsWorks and the level of abstraction worked better for me then.
- pjungwir 11y agoI'm curious what you thought of OpsWorks? I tried it a couple years ago, when it was really new, and it was pretty painful. I'd rather just run Chef myself on regular EC2 instances and Autoscaling Groups. I recall a lot of issues hooking into the OpsWorks lifecycle at the right place, broken Berkshelf support, failures with no good error messages, an even slower build-test-fix cycle than usual, discrepancies between the OpsWorks cookbooks on Github vs what was actually run, and difficulty testing things out in Vagrant first. Has any of that gotten better?
- mentat 11y agoThis was a while ago too but I used AWS support and the Loft extensively to try to bang out what actually worked. Most of my stuff was pretty simple and I was a one person ops team so it was "good enough". I would not try to make it work with a larger team but still better than that generation of EB.