Next Steps - AWS OpsWorks

Next Steps

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.

This chapter walked you through the basics of how to implement Chef cookbooks, but there's much more:

  • The examples showed you how to use some of the more commonly used resources, but there are many more.

    For the resources that were covered, the examples used only some of the available attributes and actions. For a complete reference, see About Resources and Providers.

  • The examples used only the core cookbook elements: recipes, attributes, files, and templates.

    Cookbooks can also include a variety of other elements, such as libraries, definitions, and specs. For more information, see the Chef documentation.

  • The examples used Test Kitchen only as a convenient way to start instances, run recipes, and log in to instances.

    Test Kitchen is primarily a testing platform that you can use to run a variety of tests on your recipes. If you haven't done so already, go through the rest of the Test Kitchen walkthrough, which introduces you to its testing features.

  • Implementing Cookbooks for AWS OpsWorks Stacks provides some more advanced examples, and shows how to implement cookbooks for AWS OpsWorks Stacks.