Learning AWS and Chef (1)
The cloud platform like AWS and OpenStack are gaining popularity these days, and I came up with my mind to take time to study on them. The followings are some notes of my first trials.
AWS OpsWorks is an application management service using chef as its configuration engine. It can define the layer of application on EC2 instances with some pre-configured cookbook settings, like rails and node.js servers.
It’s nice to have default built-in chef recipes, but it’s still limited ones yet (also, issues and pull requests seems stacking up).
OpsWorks supports loading custom cookbook too, but it’s a little cumbersome. I tried to put them on GitHub, but it requires very fixed directory structure as in the above User Guide. There’re many public cookbooks in the GitHub, but it cannot be easily applied.
If your cookbooks are fully established, this approach may work, but it might be a little difficult to take try and error approach.
Then I’m switching to the aws plugin for vagrant. It nicely starts up EC2 instances through standard vagrant CLI commands, as similar way as local virtual machines.
The above site nicely describes the process to setup git server on AWS. Along with the “berkshelf” gem which manages cookbooks, it seems to allow more flexibly setup of chef environment. Nice.