Use existing AWS Config recorder name to prevent recorder limit exception

[chroju]

Issue #, if available:

The Lambda function was encountering a MaxNumberOfConfigurationRecordersExceededException error when trying to update the AWS Config recorder settings. This occurs because AWS Config has a limit of one configuration recorder per account per region.

Description of changes:

This PR modifies the consumer Lambda to check for existing configuration recorders and reuse the name of any existing recorder instead of always using the hardcoded default name. This prevents the Lambda from attempting to create a new recorder when one already exists.

• Changes
  • Added logic to retrieve the name of any existing configuration recorder
  • Modified the code to use the retrieved name when updating the recorder configuration
  • Preserved all original functionality while fixing the specific exception

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[vsr2158]

Thanks for the input, why do you have more then one config recorder? IN case of control tower deployment there would be only one.

[chroju]

@vsr2158

Thank you for your question.

The issue we encountered wasn't about having multiple recorders simultaneously, but rather the code using a fixed name ( "aws-controltower-BaselineConfigRecorder" ) when trying to update the configuration. If an account already has a config recorder with a different name (which can happen in various scenarios like migrations or pre-existing configurations), the code was attempting to create a new recorder instead of updating the existing one - causing the MaxNumberOfConfigurationRecordersExceededException .

For example, we're following the AWS official procedure for enrolling accounts with existing AWS Config resources into AWS Control Tower, which creates a recorder with names like aws-controltower-BaselineConfigRecorder-customer-created.

[vsr2158]

Looks good.