Monitor stack progress - Amazon CloudFormation
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Monitor stack progress

This section describes how to monitor a stack deployment that is currently in progress. CloudFormation provides a detailed, chronological list of deployment events, showing the progress and any issues encountered during the deployment.

View stack events (console)

To view stack events
  1. Open the Amazon CloudFormation console at https://console.amazonaws.cn/cloudformation.

  2. On the navigation bar at the top of the screen, choose the Amazon Web Services Region you created the stack in.

  3. On the Stacks page of the CloudFormation console, select the stack name. CloudFormation displays the stack details for the selected stack.

  4. Choose the Events tab to view the stack events CloudFormation has generated for your stack.

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.

For more information, see Understand CloudFormation stack creation events and Monitor the progress of a stack update.

View stack events (Amazon CLI)

Alternatively, you can use the describe-stack-events command while the stack is being created to view events as they're reported.

The following describe-stack-events command describes the myteststack stack events.

aws cloudformation describe-stack-events --stack-name myteststack

The following is an example response.

{ "StackEvents": [ { "StackId": "arn:aws:cloudformation:aws-region:123456789012:stack/myteststack/466df9e0-0dff-08e3-8e2f-5088487c4896", "EventId": "af67ef60-0b8f-11e3-8b8a-500150b352e0", "ResourceStatus": "CREATE_COMPLETE", "ResourceType": "AWS::CloudFormation::Stack", "Timestamp": "2013-08-23T01:02:30.070Z", "StackName": "myteststack", "PhysicalResourceId": "arn:aws:cloudformation:aws-region:123456789012:stack/myteststack/a69442d0-0b8f-11e3-8b8a-500150b352e0", "LogicalResourceId": "myteststack" }, { "StackId": "arn:aws:cloudformation:aws-region:123456789012:stack/myteststack/466df9e0-0dff-08e3-8e2f-5088487c4896", "EventId": "S3Bucket-CREATE_COMPLETE-1377219748025", "ResourceStatus": "CREATE_COMPLETE", "ResourceType": "AWS::S3::Bucket", "Timestamp": "2013-08-23T01:02:28.025Z", "StackName": "myteststack", "ResourceProperties": "{\"AccessControl\":\"PublicRead\"}", "PhysicalResourceId": "myteststack-s3bucket-jssofi1zie2w", "LogicalResourceId": "S3Bucket" }, { "StackId": "arn:aws:cloudformation:aws-region:123456789012:stack/myteststack/466df9e0-0dff-08e3-8e2f-5088487c4896", "EventId": "S3Bucket-CREATE_IN_PROGRESS-1377219746688", "ResourceStatus": "CREATE_IN_PROGRESS", "ResourceType": "AWS::S3::Bucket", "Timestamp": "2013-08-23T01:02:26.688Z", "ResourceStatusReason": "Resource creation Initiated", "StackName": "myteststack", "ResourceProperties": "{\"AccessControl\":\"PublicRead\"}", "PhysicalResourceId": "myteststack-s3bucket-jssofi1zie2w", "LogicalResourceId": "S3Bucket" }, { "StackId": "arn:aws:cloudformation:aws-region:123456789012:stack/myteststack/466df9e0-0dff-08e3-8e2f-5088487c4896", "EventId": "S3Bucket-CREATE_IN_PROGRESS-1377219743862", "ResourceStatus": "CREATE_IN_PROGRESS", "ResourceType": "AWS::S3::Bucket", "Timestamp": "2013-08-23T01:02:23.862Z", "StackName": "myteststack", "ResourceProperties": "{\"AccessControl\":\"PublicRead\"}", "PhysicalResourceId": null, "LogicalResourceId": "S3Bucket" }, { "StackId": "arn:aws:cloudformation:aws-region:123456789012:stack/myteststack/466df9e0-0dff-08e3-8e2f-5088487c4896", "EventId": "a69469e0-0b8f-11e3-8b8a-500150b352e0", "ResourceStatus": "CREATE_IN_PROGRESS", "ResourceType": "AWS::CloudFormation::Stack", "Timestamp": "2013-08-23T01:02:15.422Z", "ResourceStatusReason": "User Initiated", "StackName": "myteststack", "PhysicalResourceId": "arn:aws:cloudformation:aws-region:123456789012:stack/myteststack/a69442d0-0b8f-11e3-8b8a-500150b352e0", "LogicalResourceId": "myteststack" } ] }

The most recent events are reported first. The following table describe the fields returned by the describe-stack-events command:

Field Description
EventId

Event identifier.

StackName

Name of the stack that the event corresponds to.

StackId

Identifier of the stack that the event corresponds to.

LogicalResourceId

Logical identifier of the resource.

PhysicalResourceId

Physical identifier of the resource.

ResourceProperties

Properties of the resource.

ResourceType

Type of the resource.

Timestamp

Time when the event occurred.

ResourceStatus

The status of the resource, which can be one of the following status codes: CREATE_COMPLETE | CREATE_FAILED | CREATE_IN_PROGRESS | DELETE_COMPLETE | DELETE_FAILED | DELETE_IN_PROGRESS | DELETE_SKIPPED | IMPORT_COMPLETE | IMPORT_IN_PROGRESS | IMPORT_ROLLBACK_COMPLETE | IMPORT_ROLLBACK_FAILED | IMPORT_ROLLBACK_IN_PROGRESS | REVIEW_IN_PROGRESS | ROLLBACK_COMPLETE | ROLLBACK_FAILED | ROLLBACK_IN_PROGRESS | UPDATE_COMPLETE | UPDATE_COMPLETE_CLEANUP_IN_PROGRESS | UPDATE_FAILED | UPDATE_IN_PROGRESS | UPDATE_ROLLBACK_COMPLETE | UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS | UPDATE_ROLLBACK_FAILED | UPDATE_ROLLBACK_IN_PROGRESS

The DELETE_SKIPPED status applies to resources with a deletion policy attribute of retain.

DetailedStatus

The detailed status of the stack. If CONFIGURATION_COMPLETE is present, the stack resources configuration phase has completed and the stabilization of the resources is in progress.

ResourceStatusReason

More information on the status.

Stack status codes

The following table describes stack status codes:

Stack status and optional detailed status Description

CREATE_COMPLETE

Successful creation of one or more stacks.

CREATE_IN_PROGRESS

Ongoing creation of one or more stacks.

CREATE_FAILED

Unsuccessful creation of one or more stacks. View the stack events to see any associated error messages. Possible reasons for a failed creation include insufficient permissions to work with all resources in the stack, parameter values rejected by an Amazon service, or a timeout during resource creation.

DELETE_COMPLETE

Successful deletion of one or more stacks. Deleted stacks are retained and viewable for 90 days.

DELETE_FAILED

Unsuccessful deletion of one or more stacks. Because the delete failed, you might have some resources that are still running; however, you can't work with or update the stack. Delete the stack again or view the stack events to see any associated error messages.

DELETE_IN_PROGRESS

Ongoing removal of one or more stacks.

REVIEW_IN_PROGRESS

Ongoing creation of one or more stacks with an expected StackId but without any templates or resources.
Important

A stack with this status code counts against the maximum possible number of stacks.

ROLLBACK_COMPLETE

Successful removal of one or more stacks after a failed stack creation or after an explicitly canceled stack creation. The stack returns to the previous working state. Any resources that were created during the create stack operation are deleted.

This status exists only after a failed stack creation. It signifies that all operations from the partially created stack have been appropriately cleaned up. When in this state, only a delete operation can be performed.

ROLLBACK_FAILED

Unsuccessful removal of one or more stacks after a failed stack creation or after an explicitly canceled stack creation. Delete the stack or view the stack events to see any associated error messages.

ROLLBACK_IN_PROGRESS

Ongoing removal of one or more stacks after a failed stack creation or after an explicitly canceled stack creation.

UPDATE_COMPLETE

Successful update of one or more stacks.

UPDATE_COMPLETE_CLEANUP_IN_PROGRESS

Ongoing removal of old resources for one or more stacks after a successful stack update. For stack updates that require resources to be replaced, CloudFormation creates the new resources first and then deletes the old resources to help reduce any interruptions with your stack. In this state, the stack has been updated and is usable, but CloudFormation is still deleting the old resources.

UPDATE_FAILED

Unsuccessful update of one or more stacks. View the stack events to see any associated error messages.

UPDATE_IN_PROGRESS

Ongoing update of one or more stacks.

UPDATE_ROLLBACK_COMPLETE

Successful return of one or more stacks to a previous working state after a failed stack update.

UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS

Ongoing removal of new resources for one or more stacks after a failed stack update. In this state, the stack has been rolled back to its previous working state and is usable, but CloudFormation is still deleting any new resources it created during the stack update.

UPDATE_ROLLBACK_FAILED

Unsuccessful return of one or more stacks to a previous working state after a failed stack update. When in this state, you can delete the stack or continue rollback. You might need to fix errors before your stack can return to a working state. Or, you can contact Amazon Web Services Support to restore the stack to a usable state.

UPDATE_ROLLBACK_IN_PROGRESS

Ongoing return of one or more stacks to the previous working state after failed stack update.

IMPORT_IN_PROGRESS

The import operation is currently in progress.

IMPORT_COMPLETE

The import operation successfully completed for all resources in the stack that support resource import.

IMPORT_ROLLBACK_IN_PROGRESS

Import will roll back to the previous template configuration.

IMPORT_ROLLBACK_FAILED

The import rollback operation failed for at least one resource in the stack. Results will be available for the resources CloudFormation successfully imported.

IMPORT_ROLLBACK_COMPLETE

Import successfully rolled back to the previous template configuration.