ConfigurationRecorderStatus.lastStatus type does not match actual values

[rickyrattlesnake]

Checkboxes for prior research

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow.
• I've searched for previous similar issues and didn't find any solution.

Describe the bug

Client: config-service

The current type for lastStatus (here) on the response to DescribeConfigurationRecorderStatus command does not match actual values returned.

The types definition is in the RecorderStatus const.

The return response when using the SDK client and the AWS CLI both confirm they are Uppercase strings rather than the TitleCase string in the type definition. e.g.

{
    "ConfigurationRecordersStatus": [
        {
            "arn": "arn:aws:config:us-west-2:<redacted>:configuration-recorder/<redacted>-ConfigRecorder-<redacted>/<redacted>",
            "name": "<redacted>",
            "lastStartTime": "2019-05-07T18:52:09.664000+10:00",
            "recording": true,
            "lastStatus": "SUCCESS",
            "lastStatusChangeTime": "2025-08-25T11:23:25.747000+10:00"
        }
    ]
}

Regression Issue

• Select this option if this issue appears to be a regression.

SDK version number

@aws-sdk/client-config-service@3.864.0

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

v22.15.0

Reproduction Steps

Run the DescribeConfigurationRecordersCommand after setting up a configuration recorder for AWS Config service.

import {
	ConfigServiceClient,
	DescribeConfigurationRecordersCommand
} from "@aws-sdk/client-config-service";
import util from 'node:util';

const client = new ConfigServiceClient(config);
const response = await client.send(new DescribeConfigurationRecordersCommand({}));

console.log(util.inspect(response));

Observed Behavior

• Mismatched types and response from the client SDK call

Expected Behavior

• The type for lastStatus should be SUCCESS | FAILURE etc.

Possible Solution

• Fix the types in the repo if the actual values are correct for all regions

Additional Information/Context

No response