Implementing Cookbooks for AWS OpsWorks Stacks
Important
AWS OpsWorks Stacks is no longer accepting new customers. Existing customers will be able to use the OpsWorks console, API, CLI, and CloudFormation resources as normal until May 26, 2024, at which time they will be discontinued. To prepare for this transition, we recommend you transition your stacks to AWS Systems Manager as soon as possible. For more information, see AWS OpsWorks Stacks End of Life FAQs and Migrating your AWS OpsWorks Stacks applications to AWS Systems Manager Application Manager.
Cookbook Basics introduced you to cookbooks and recipes. The examples in that section were simple by design and will work on any instance that supports Chef, including AWS OpsWorks Stacks instances. To implement more sophisticated cookbooks for AWS OpsWorks Stacks, you typically need to take full advantage of the AWS OpsWorks Stacks environment, which differs from standard Chef in a number of ways.
This topic describes the basics of implementing recipes for AWS OpsWorks Stacks instances.
Note
If you are not familiar with how to implement cookbooks, you should start with Cookbook Basics.
Topics
- Running a Recipe on an AWS OpsWorks Stacks Linux Instance
- Running a Recipe on a Windows Instance
- Running a Windows PowerShell Script
- Mocking the Stack Configuration and Deployment Attributes on Vagrant
- Using Stack Configuration and Deployment Attribute Values
- Using an External Cookbook on a Linux Instance: Berkshelf
- Using the SDK for Ruby: Downloading Files from Amazon S3
- Installing Windows Software
- Overriding Built-In Attributes
- Overriding Built-In Templates