OpsWorks + Windows: Alternate user identity execute support

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


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

OpsWorks + Auto-scaling Windows Stacks

AWS has multiple ways of enabling Auto-scaling of EC2 instances. Two of which are Auto-Scaling Groups and OpsWorks. When setting up a stack in OpsWorks you’ll notice that you can add Load-based instances to scale the stack beyond the fixed instances you establish. The scale configuration that you specify on the below screen should be … Continue reading OpsWorks + Auto-scaling Windows Stacks