A common scenario when configuring an environment is that certain elements of the scripts may need to be executed using a specific user’s credentials. If you’ve looked at the documentation for the various means of execution within Chef you might have noticed the “user”, “domain” and “password” parameters. The “powershell_script” action is particularly useful when … Continue reading OpsWorks + Windows: Alternate user identity execute support
Chef
Git + OpsWorks: Getting Organized
In OpsWorks, each "Layer" can be linked to its own repository. You can also specify a branch of your choosing. The terminology mapping between AWS, Git and Application Architecture can sometimes be a bit confusing and can lead to mal-configured OpsWorks stacks which can subsequently lead to OpsWorks being used inappropriately due to perceived technical … Continue reading Git + OpsWorks: Getting Organized
Manually Run a Chef Script on OpsWorks
Let’s say you’re manually testing a recipe on one of your OpsWorks instances. This recipe is the nth step in a multi-step process and you’ve fully tested and integrated into your “Setup” lifecycle event all the recipes that handle steps 1 through n-1. The highlighted recipe is such a recipe. It resides within a parent … Continue reading Manually Run a Chef Script on OpsWorks
The Three ‘Don’ts’ of OpsWorks
Don't Treat Them Like Regular Virtual Machines I've seen OpsWorks used as a round about way to provision EC2 instances. This is not the purpose of OpsWorks. OpsWorks provides an orchestration mechanism that triggers configuration management events at key events in the life of a virtual machine allowing us to respond to change in our environments … Continue reading The Three ‘Don’ts’ of OpsWorks
Sky Cliffs 