Currently, I am utilizing the aws-cdk to create config rules for approximately 15 rules that we need to monitor and receive notifications on. Below is a snippet of the code for reference:
// Code snippet showing the creation of multiple config rules
My main concern arises when attempting to utilize the configurationChanges parameter and set it to True. My intention is for the config rule to scan the specified resource group upon detecting a change. The reason for avoiding the "frequency" parameter is our client's preference for less frequent scans, ideally every two weeks instead of the default 24-hour interval. With that in mind, I have several questions: 1. Is it possible to configure the config rules to scan less frequently than every 24 hours, perhaps weekly? 2. Can a lambda trigger the config rule to initiate a scan? For instance, checking for the presence of VPC flow logs and triggering an "incompliant" status if missing. 3. Alternatively, can I simply enable configurationChange for all config rules and rely on AWS to manage them accordingly? This query stems from my limited understanding of the config recorder functionality. Any insights or guidance on this matter would be greatly appreciated. Thank you!