Posted On: Oct 1, 2020

AWS CloudFormation Drift Detection now supports CloudFormation Registry resource types, so you can detect unmanaged configuration changes on additional AWS resources, as well as third-party or private ones.  

Drift Detection enables you to detect whether the actual configuration differs, or has drifted, from its expected configuration. The CloudFormation Registry makes it easy to model and automate the management of AWS and third-party resources with the benefits of infrastructure as code. With this release, you can detect drift on resource types registered with the Registry. This includes resource types from third parties as well as private types. This release adds support for over 90 new Registry resource types in addition to the 50 originally supported resource types, including Amazon CloudWatch Alarms, Amazon ECS Clusters, and AWS Config Conformance Packs. Going forward, all new Registry types will be automatically supported by Drift Detection, so that you can detect configuration changes on more of your resources as soon as they are available in the Registry.  

To get started, read the documentation on detecting unmanaged configuration changes to stacks and resources, where you will find details on detecting drift. For an up-to-date list of AWS resource types supported by Drift Detection, refer to the resource types section of the documentation.  

For Drift Detection region availability, refer to the AWS Region Table.