Reviewing your stack on the AWS CloudFormation console - AWS CloudFormation

Reviewing your stack on the AWS CloudFormation console

The final step before your stack is launched is to review the values entered while creating the stack.

  1. On the Review page, review the details of your stack.

    If you need to change any of the values before launching the stack, choose Edit on the appropriate section to go back to the page that has the setting that you want to change.

  2. After you review the stack creation settings, choose Create stack to launch your stack.

    Note

    As this point, you can also choose to create a new change set rather than a new stack. To do so, click Create change set instead of Create stack. For more information, see Creating stacks using change sets

    CloudFormation displays the Events pane of the Stack details page for your new stack. From here, you can view your stack's events, data, or resources. CloudFormation automatically refreshes the stack events every minute. Additionally, CloudFormation displays the New events available badge when new stack events occur; choose the refresh icon to load these events into the list. By viewing stack creation events, you can understand the sequence of events that lead to your stack's creation (or failure, if you are debugging your stack).

    While your stack is being created, it's listed on the Stacks page with a status of CREATE_IN_PROGRESS.

    After your stack has been successfully created, its status changes to CREATE_COMPLETE. You can then choose the Outputs tab to view your stack's outputs if you have defined any in the template.

Determining root cause for failures

If your stack fails to be created, AWS CloudFormation can help you to determine the event that is likely the root cause for the stack failure. To do this, in the list of stacks select the failed stack and then select Detect root cause.


    Events tab of stack info details before running Detect root cause

CloudFormation will analyze the failure and indicate the event that is the likely root cause for the failure.


    Events tab of stack info details indicating the event that is the likely root cause for the stack
     failure.