opsworks-example-cookbooks | AWS OpsWorks cookbooks used with the sample applications | AWS library

From the screenshot above, it looks like your stack's state is still in CREATE_IN_PROGRESS. One of your resources (probably your AWS::OpsWorks::Instance?) did not get created correctly. To troubleshoot, you can try logging into the instance, checking the OpsWorks Chef Logs, or looking at output logs on the instance (/var/log/cfn-init.log and /var/log/cloud-init-output.log) to find the underlying cause/error.

More generally, refer to the AWS Knowledge Center article, How do I troubleshoot an AWS CloudFormation stack that is stuck with a status of CREATE_IN_PROGRESS or UPDATE_IN_PROGRESS?:

Short Description

This condition typically occurs when there are problems with the resource that is being created or updated, causing the stack to eventually fail. If there is no timeout parameter specified for the stack, it will take longer for the stack to reach the CREATE_FAILED or UPDATE_FAILED state.

Resolution

• If possible, check the exact resource that CloudFormation is stuck creating. Auto Scaling often provides clear error messages to describe events that prevent instances from launching.
• Ensure that you are not exceeding the AWS limits for the resources that you want to create. For example, if the CloudFormation template specifies two EC2 instances but your instance count is currently at 19 with an upper limit of 20, the stack creation fails.

See also Monitoring the Progress of a Stack Update section of the documentation.