Debugging and Troubleshooting Guide - AWS OpsWorks

Debugging and Troubleshooting Guide


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.

If you need to debug a recipe or troubleshoot a service issue, the best approach generally is to work through the following steps, in order:

  1. Check Common Debugging and Troubleshooting Issues for your specific issue.

  2. Search the AWS OpsWorks Stacks Forum to see if the issue has been discussed there.

    The Forum includes many experienced users and is monitored by the AWS OpsWorks Stacks team.

  3. For issues with recipes, see Debugging Recipes.

  4. Contact AWS OpsWorks Stacks support or post your issue on the AWS OpsWorks Stacks Forum.

The following section provides guidance for debugging recipes. The final section describes common debugging and troubleshooting issues and their solutions.


Each Chef run produces a log, which provides a detailed description of the run and is a valuable troubleshooting resource. To specify the amount of detail in the log, add a Chef::Log.level statement to a custom recipe that specifies the desired log level. The default value is :info. The following example shows how to set the Chef log level to :debug, which provides the most detailed description of the run.

Chef::Log.level = :debug

For more information about viewing and interpreting Chef logs, see Chef Logs.