A factory deployed the same AWS Config rule in every Region it uses. Only one Region produces no real compliance result, and the configuration recorder in that Region was never started. What should be started there?
Select an answer to reveal the explanation.
Short Explanation
A referee who never walked onto the field cannot call the game. You get no real compliance result in that Region because the configuration recorder was never started, so start it and let the rule evaluate what it records. The trap is copying the rule somewhere else and expecting this Region to start recording.
Full Explanation
Config rules evaluate configuration items captured by the configuration recorder, and the recorder is regional. In the Region where it was never started, there are no configuration items for the rule to evaluate, which is why that Region produces no real compliance result. Starting the recorder there is what begins recording. Another copy of the rule in a Region that already records does not observe resources in the quiet Region. An organization CloudTrail trail records API calls and does not create Config configuration items or feed the rule. A Macie job classifies sensitive data in stores such as S3 and does not start Config recording. The recorder needs a delivery channel in that Region or the start fails, and resources are recorded from the time recording begins rather than retroactively. Confirm the recorder in that Region is recording, then confirm the rule evaluation lists resources that exist there. The rule cannot backfill the time before recording started, so the first useful result appears only after resources have been captured.