Drift Detection Status Change event detail - AWS CloudFormation

Drift Detection Status Change event detail

Below are the detail fields for stack drift detection events.

The source and detail-type fields are included because they contain specific values for AWS CloudFormation events.

{ . . ., "detail-type":"CloudFormation Drift Detection Status Change", "source":"aws.cloudformation", . . ., "detail":{ "stack-id":"string", "stack-drift-detection-id":"string", "status-details":{ "stack-drift-status":"string", "detection-status":"string" }, "drift-detection-details":{ "drifted-stack-resource-count":integer }, "client-request-token":"string" } }

Identifies the type of event.

For stack drift detection events, this value is CloudFormation Drift Detection Status Change.


Identifies the service that generated the event. For CloudFormation events, this value is aws.cloudformation.


A JSON object that contains information about the event. The service generating the event determines the content of this field.

For stack drift detection events, this data includes:


The unique stack ID that's associated with the stack.


The stack drift detection Id.


Drift status of the stack.


Status of drift detection operation.


Number of resources drifted. When the value is -1, the drift detection is in progress. All other non--negative integers represent the actual number of drifted resources.


An access token used to call the API. All events that are initiated by a given stack operation are assigned the same client request token, which you can use to track operations. Stack operations that are initiated from the console use the token format Console-StackOperation-ID, which helps you to easily identify the stack operation. For example, if you create a stack using the console, each resulting stack event would be assigned the same token in the following format: Console-CreateStack-7f59c3cf-00d2-40c7-b2ff-e75db0987002.

Example: Stack Drift Detection event

The following is an example Stack Drift Detection event. This event details that CloudFormation has completed drift detection on the specified stack, and that the stack currently has a drift status of DRIFTED due to one drifted resource.

{ "version":"0", "id":"6a7e8feb-b491-4cf7-a9f1-bf3703467718", "detail-type":"CloudFormation Drift Detection Status Change", "source":"aws.cloudformation", "account":"111122223333", "time":"2017-12-22T18:43:48Z", "region":"us-west-1", "resources": ["string"], "detail":{ "stack-id":"arn:aws:cloudformation:us-west-1:111122223333:stack/teststack", "stack-drift-detection-id":"624af370-311a-11e8-b6b7-500cexample", "status-details":{ "stack-drift-status":"DRIFTED", "detection-status":"DETECTION_COMPLETE" }, "drift-detection-details":{ "drifted-stack-resource-count":1 }, "client-request-token":"" } }