AWS Config enables drift detection in Config Recorder

AWS Config now supports configuration recorder as a configuration item. [Configuration recorder](https://docs.aws.amazon.com/config/latest/developerguide/stop-start-recorder.html) must be enabled before AWS Config can detect changes to your resource configurations and capture these changes as configuration items. With this launch, you can now monitor configuration changes to the configuration recorder in your AWS account. AWS Config enables you to track and assess the configuration of your cloud resources throughout their life cycle. AWS Config console or AWS Command Line Interface (AWS CLI) users can update tracked resources or enable, disable or delete the configuration recorder. The configuration recorder must stay enabled to run compliance evaluations for tracked resources. With this release, AWS allows you to track configuration changes to the configuration recorder’s state, specifically if it is no longer enabled or is uninstalled. This update also enables you to get an up-to-date list of resources that are tracked through AWS Config and run compliance checks for actively tracked resources. This functionality is now available to all AWS Config users as default at no additional charge. AWS Config supports this new functionality in following [AWS Regions](/about-aws/global-infrastructure/regional-product-services/): US East (Ohio), US East (N. Virginia), US West (N. California), US West (Oregon), Asia Pacific (Hong Kong), Asia Pacific (Mumbai), Asia Pacific (Seoul), Asia Pacific (Singapore), Asia Pacific (Sydney), Asia Pacific (Tokyo), Canada (Central), Europe (Stockholm), Europe (Frankfurt), Europe (Ireland), Europe (London), Europe (Paris), Middle East (Bahrain), South America (São Paulo). To learn more about complete list of all supported types, see [supported resource types](https://docs.aws.amazon.com/config/latest/developerguide/resource-config-reference.html) page.