Config - put_configuration_recorder leaves old resource type overrides

[ryanash999]

Describe the bug

After using client.put_configuration_recorder to push frequency overrides we tried to remove the settings with a similar call. The second call is using the below settings to remove the existing resource type overrides.
'recordingMode': { 'recordingFrequency': 'CONTINUOUS', 'recordingModeOverrides': [] }

Expected Behavior

I expect the existing overrides to be removed because an empty list was provided.

Current Behavior

The overrides remain but are set back to "CONTINUOUS" as expected. I.e we still the overrides for the 3 resource types even if the frequency is now correct.

Reproduction Steps

1. use put_configuration_recorder to update an exiting recorder with an override to DAILY for a resource type
2. use put_configuration_recorder with empty list for "recordingModeOverrides"
3. Expectation as I see it is removal of the overrides.

Possible Solution

unknown

Additional Information/Context

n/a

SDK version used

1.34.30

Environment details (OS name and version, etc.)

Mac

[tim-finnigan]

Hi there - thanks for your patience. Here is the documentation for the command you referenced: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/config/client/put_configuration_recorder.html. I noticed that you're using an older version of Boto3 — the latest is 1.34.101 per the CHANGELOG. We recommend updating your version of Boto3 to have access to the latest updates/fixes.

Please also note that the Boto3 command involves a call to the underlying PutConfigurationRecorder API, so if there are any issues with the API then we would need to escalate those to the ConfigService team.

For us to investigate further, can you share a code snippet for reproducing the issue? And could you share debug logs (with sensitive info redacted) by adding boto3.set_stream_logger('') to your script?

[github-actions[bot]]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.