@aws-sdk/client-config-service 3.848.0 → 3.854.0

package/dist-types/commands/DeleteConfigRuleCommand.d.ts

@@ -38,27 +38,15 @@ declare const DeleteConfigRuleCommand_base: {
  * 				<code>DescribeConfigRules</code> request.</p>
  *          <note>
  *             <p>
- *                <b>Recommendation: Stop recording resource compliance before deleting rules</b>
+ *                <b>Recommendation: Consider excluding the <code>AWS::Config::ResourceCompliance</code> resource type from recording before deleting rules</b>
  *             </p>
- *             <p>It is highly recommended that you stop recording for the <code>AWS::Config::ResourceCompliance</code> resource type before you delete rules in your account.
- * 				Deleting rules creates CIs for <code>AWS::Config::ResourceCompliance</code> and can affect your Config <a href="https://docs.aws.amazon.com/config/latest/developerguide/stop-start-recorder.html">configuration recorder</a> costs.
- *
- * 				If you are deleting rules which evaluate a large number of resource types,
+ *             <p>Deleting rules creates configuration items (CIs) for <code>AWS::Config::ResourceCompliance</code>
+ * 				that can affect your costs for the configuration recorder. If you are deleting rules which evaluate a large number of resource types,
  * 				this can lead to a spike in the number of CIs recorded.</p>
- *             <p>Best practice:</p>
- *             <ol>
- *                <li>
- *                   <p>Stop recording <code>AWS::Config::ResourceCompliance</code>
- *                   </p>
- *                </li>
- *                <li>
- *                   <p>Delete rule(s)</p>
- *                </li>
- *                <li>
- *                   <p>Turn on recording for <code>AWS::Config::ResourceCompliance</code>
- *                   </p>
- *                </li>
- *             </ol>
+ *             <p>To avoid the associated costs, you can opt to disable recording
+ * 				for the <code>AWS::Config::ResourceCompliance</code> resource type before deleting rules, and re-enable recording after the rules have been deleted.</p>
+ *             <p>However, since deleting rules is an asynchronous process, it might take an hour or more to complete. During the time
+ * 				when recording is disabled for <code>AWS::Config::ResourceCompliance</code>, rule evaluations will not be recorded in the associated resource’s history.</p>
  *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

package/dist-types/commands/DeleteConformancePackCommand.d.ts

@@ -31,6 +31,18 @@ declare const DeleteConformancePackCommand_base: {
  * 			conformance pack.</p>
  *          <p>Config sets the conformance pack to <code>DELETE_IN_PROGRESS</code> until the deletion is complete.
  * 			You cannot update a conformance pack while it is in this state.</p>
+ *          <note>
+ *             <p>
+ *                <b>Recommendation: Consider excluding the <code>AWS::Config::ResourceCompliance</code> resource type from recording before deleting rules</b>
+ *             </p>
+ *             <p>Deleting rules creates configuration items (CIs) for <code>AWS::Config::ResourceCompliance</code>
+ * 				that can affect your costs for the configuration recorder. If you are deleting rules which evaluate a large number of resource types,
+ * 				this can lead to a spike in the number of CIs recorded.</p>
+ *             <p>To avoid the associated costs, you can opt to disable recording
+ * 				for the <code>AWS::Config::ResourceCompliance</code> resource type before deleting rules, and re-enable recording after the rules have been deleted.</p>
+ *             <p>However, since deleting rules is an asynchronous process, it might take an hour or more to complete. During the time
+ * 				when recording is disabled for <code>AWS::Config::ResourceCompliance</code>, rule evaluations will not be recorded in the associated resource’s history.</p>
+ *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/DeleteOrganizationConfigRuleCommand.d.ts

@@ -33,6 +33,18 @@ declare const DeleteOrganizationConfigRuleCommand_base: {
  * 			<code>ListDelegatedAdministrator</code> permissions are added.</p>
  *          <p>Config sets the state of a rule to DELETE_IN_PROGRESS until the deletion is complete.
  * 			You cannot update a rule while it is in this state.</p>
+ *          <note>
+ *             <p>
+ *                <b>Recommendation: Consider excluding the <code>AWS::Config::ResourceCompliance</code> resource type from recording before deleting rules</b>
+ *             </p>
+ *             <p>Deleting rules creates configuration items (CIs) for <code>AWS::Config::ResourceCompliance</code>
+ * 				that can affect your costs for the configuration recorder. If you are deleting rules which evaluate a large number of resource types,
+ * 				this can lead to a spike in the number of CIs recorded.</p>
+ *             <p>To avoid the associated costs, you can opt to disable recording
+ * 				for the <code>AWS::Config::ResourceCompliance</code> resource type before deleting rules, and re-enable recording after the rules have been deleted.</p>
+ *             <p>However, since deleting rules is an asynchronous process, it might take an hour or more to complete. During the time
+ * 				when recording is disabled for <code>AWS::Config::ResourceCompliance</code>, rule evaluations will not be recorded in the associated resource’s history.</p>
+ *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/DeleteOrganizationConformancePackCommand.d.ts

@@ -34,6 +34,18 @@ declare const DeleteOrganizationConformancePackCommand_base: {
  * 		<code>ListDelegatedAdministrator</code> permissions are added.</p>
  *          <p>Config sets the state of a conformance pack to DELETE_IN_PROGRESS until the deletion is complete.
  * 				You cannot update a conformance pack while it is in this state. </p>
+ *          <note>
+ *             <p>
+ *                <b>Recommendation: Consider excluding the <code>AWS::Config::ResourceCompliance</code> resource type from recording before deleting rules</b>
+ *             </p>
+ *             <p>Deleting rules creates configuration items (CIs) for <code>AWS::Config::ResourceCompliance</code>
+ * 				that can affect your costs for the configuration recorder. If you are deleting rules which evaluate a large number of resource types,
+ * 				this can lead to a spike in the number of CIs recorded.</p>
+ *             <p>To avoid the associated costs, you can opt to disable recording
+ * 				for the <code>AWS::Config::ResourceCompliance</code> resource type before deleting rules, and re-enable recording after the rules have been deleted.</p>
+ *             <p>However, since deleting rules is an asynchronous process, it might take an hour or more to complete. During the time
+ * 				when recording is disabled for <code>AWS::Config::ResourceCompliance</code>, rule evaluations will not be recorded in the associated resource’s history.</p>
+ *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/GetResourceConfigHistoryCommand.d.ts

@@ -28,16 +28,22 @@ declare const GetResourceConfigHistoryCommand_base: {
 };
 /**
  * <important>
- *             <p>For accurate reporting on the compliance status, you must record the <code>AWS::Config::ResourceCompliance</code> resource type.
- * 			For more information, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/select-resources.html">Selecting Which Resources Config Records</a>.</p>
+ *             <p>For accurate reporting on the compliance status, you must record the <code>AWS::Config::ResourceCompliance</code> resource type.</p>
+ *             <p>For more information, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/select-resources.html">Recording Amazon Web Services Resources</a> in the <i>Config Resources Developer Guide</i>.</p>
  *          </important>
- *          <p>Returns a list of <code>ConfigurationItems</code> for the specified resource.
- * 			The list contains details about each state of the resource
+ *          <p>Returns a list of configurations items (CIs) for the specified resource.</p>
+ *          <p>
+ *             <b>Contents</b>
+ *          </p>
+ *          <p>The list contains details about each state of the resource
  * 			during the specified time interval. If you specified a retention
- * 			period to retain your <code>ConfigurationItems</code> between a
+ * 			period to retain your CIs between a
  * 			minimum of 30 days and a maximum of 7 years (2557 days), Config
- * 			returns the <code>ConfigurationItems</code> for the specified
+ * 			returns the CIs for the specified
  * 			retention period. </p>
+ *          <p>
+ *             <b>Pagination</b>
+ *          </p>
  *          <p>The response is paginated. By default, Config returns a
  * 			limit of 10 configuration items per page. You can customize this
  * 			number with the <code>limit</code> parameter. The response includes

package/dist-types/commands/ListDiscoveredResourcesCommand.d.ts

@@ -27,23 +27,61 @@ declare const ListDiscoveredResourcesCommand_base: {
     getEndpointParameterInstructions(): import("@smithy/middleware-endpoint").EndpointParameterInstructions;
 };
 /**
- * <p>Accepts a resource type and returns a list of resource
- * 			identifiers for the resources of that type. A resource identifier
+ * <p>Returns a list of resource
+ * 			resource identifiers for the specified resource types for the resources of that type. A <i>resource identifier</i>
  * 			includes the resource type, ID, and (if available) the custom
- * 			resource name. The results consist of resources that Config has
- * 			discovered, including those that Config is not currently
+ * 			resource name.</p>
+ *          <p>The results consist of resources that Config has
+ * 			<i>discovered</i>, including those that Config is not currently
  * 			recording. You can narrow the results to include only resources that
  * 			have specific resource IDs or a resource name.</p>
  *          <note>
  *             <p>You can specify either resource IDs or a resource name, but
  * 				not both, in the same request.</p>
  *          </note>
- *          <p>The response is paginated. By default, Config lists 100
- * 			resource identifiers on each page. You can customize this number
- * 			with the <code>limit</code> parameter. The response includes a
- * 				<code>nextToken</code> string. To get the next page of results,
- * 			run the request again and specify the string for the
- * 				<code>nextToken</code> parameter.</p>
+ *          <important>
+ *             <p>
+ *                <i>CloudFormation stack recording behavior in Config</i>
+ *             </p>
+ *             <p>When a CloudFormation stack fails to create (for example, it enters the <code>ROLLBACK_FAILED</code> state),
+ * 				Config does not record a configuration item (CI) for that stack. Configuration items are only recorded for stacks that reach
+ * 				the following states:</p>
+ *             <ul>
+ *                <li>
+ *                   <p>
+ *                      <code>CREATE_COMPLETE</code>
+ *                   </p>
+ *                </li>
+ *                <li>
+ *                   <p>
+ *                      <code>UPDATE_COMPLETE</code>
+ *                   </p>
+ *                </li>
+ *                <li>
+ *                   <p>
+ *                      <code>UPDATE_ROLLBACK_COMPLETE</code>
+ *                   </p>
+ *                </li>
+ *                <li>
+ *                   <p>
+ *                      <code>UPDATE_ROLLBACK_FAILED</code>
+ *                   </p>
+ *                </li>
+ *                <li>
+ *                   <p>
+ *                      <code>DELETE_FAILED</code>
+ *                   </p>
+ *                </li>
+ *                <li>
+ *                   <p>
+ *                      <code>DELETE_COMPLETE</code>
+ *                   </p>
+ *                </li>
+ *             </ul>
+ *             <p>Because no CI is created for a failed stack creation, you won't see configuration history
+ * 				for that stack in Config, even after the stack is deleted. This helps make sure that Config only
+ * 				tracks resources that were successfully provisioned.</p>
+ *          </important>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

package/dist-types/commands/PutConfigurationRecorderCommand.d.ts

@@ -113,8 +113,7 @@ declare const PutConfigurationRecorderCommand_base: {
  * @see {@link ConfigServiceClientResolvedConfig | config} for ConfigServiceClient's `config` shape.
  *
  * @throws {@link InvalidConfigurationRecorderNameException} (client fault)
- *  <p>You have provided a name for the customer managed configuration recorder that is not
- * 			valid.</p>
+ *  <p>The configuration recorder name is not valid. The prefix "<code>AWSConfigurationRecorderFor</code>" is reserved for service-linked configuration recorders.</p>
  *
  * @throws {@link InvalidRecordingGroupException} (client fault)
  *  <p>One of the following errors:</p>

package/dist-types/commands/PutConformancePackCommand.d.ts

@@ -32,6 +32,17 @@ declare const PutConformancePackCommand_base: {
  * 			see <a href="https://docs.aws.amazon.com/config/latest/developerguide/configlimits.html">
  *                <b>Service Limits</b>
  *             </a> in the <i>Config Developer Guide</i>.</p>
+ *          <important>
+ *             <p>When you use <code>PutConformancePack</code> to deploy conformance packs in your account,
+ * 				the operation can create Config rules and remediation actions without
+ * 				requiring <code>config:PutConfigRule</code> or
+ * 					<code>config:PutRemediationConfigurations</code> permissions in your account IAM
+ * 				policies.</p>
+ *             <p>This API uses the <code>AWSServiceRoleForConfigConforms</code> service-linked role in your
+ * 				account to create conformance pack resources. This service-linked role includes the
+ * 				permissions to create Config rules and remediation configurations, even
+ * 				if your account IAM policies explicitly deny these actions.</p>
+ *          </important>
  *          <p>This API creates a service-linked role <code>AWSServiceRoleForConfigConforms</code> in your account.
  * 		The service-linked role is created only when the role does not exist in your account. </p>
  *          <note>

package/dist-types/commands/PutOrganizationConformancePackCommand.d.ts

@@ -34,6 +34,18 @@ declare const PutOrganizationConformancePackCommand_base: {
  *          <p>Only a management account and a delegated administrator can call this API.
  * 			When calling this API with a delegated administrator, you must ensure Organizations
  * 			<code>ListDelegatedAdministrator</code> permissions are added. An organization can have up to 3 delegated administrators.</p>
+ *          <important>
+ *             <p>When you use <code>PutOrganizationConformancePack</code> to deploy conformance packs across
+ * 				member accounts, the operation can create Config rules and remediation
+ * 				actions without requiring <code>config:PutConfigRule</code> or
+ * 					<code>config:PutRemediationConfigurations</code> permissions in member account
+ * 				IAM policies.</p>
+ *             <p>This API uses the <code>AWSServiceRoleForConfigConforms</code> service-linked role in each
+ * 				member account to create conformance pack resources. This service-linked role
+ * 				includes the permissions to create Config rules and remediation
+ * 				configurations, even if member account IAM policies explicitly deny these
+ * 				actions.</p>
+ *          </important>
  *          <p>This API enables organization service access for <code>config-multiaccountsetup.amazonaws.com</code>
  * 			through the <code>EnableAWSServiceAccess</code> action and creates a
  * 			service-linked role <code>AWSServiceRoleForConfigMultiAccountSetup</code> in the management or delegated administrator account of your organization.

package/dist-types/commands/PutServiceLinkedConfigurationRecorderCommand.d.ts

@@ -29,7 +29,7 @@ declare const PutServiceLinkedConfigurationRecorderCommand_base: {
 /**
  * <p>Creates a service-linked configuration recorder that is linked to a specific Amazon Web Services service based on the <code>ServicePrincipal</code> you specify.</p>
  *          <p>The configuration recorder's <code>name</code>, <code>recordingGroup</code>, <code>recordingMode</code>, and <code>recordingScope</code> is set by the service that is linked to the configuration recorder.</p>
- *          <p>For more information, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/stop-start-recorder.html">
+ *          <p>For more information and a list of supported services/service principals, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/stop-start-recorder.html">
  *                <b>Working with the Configuration Recorder</b>
  *             </a> in the <i>Config Developer Guide</i>.</p>
  *          <p>This API creates a service-linked role <code>AWSServiceRoleForConfig</code> in your account. The service-linked role is created only when the role does not exist in your account.</p>

package/dist-types/models/models_0.d.ts

@@ -1586,7 +1586,7 @@ export interface ConfigurationRecorder {
     /**
      * <p>The name of the configuration recorder.</p>
      *          <p>For customer managed configuration recorders, Config automatically assigns the name of "default" when creating a configuration recorder if you do not specify a name at creation time.</p>
-     *          <p>For service-linked configuration recorders, Config automatically assigns a name that has the prefix "<code>AWS</code>" to a new service-linked configuration recorder.</p>
+     *          <p>For service-linked configuration recorders, Config automatically assigns a name that has the prefix "<code>AWSConfigurationRecorderFor</code>" to a new service-linked configuration recorder.</p>
      *          <note>
      *             <p>
      *                <b>Changing the name of a configuration recorder</b>
@@ -1882,19 +1882,26 @@ export interface BaseConfigurationItem {
      */
     resourceCreationTime?: Date | undefined;
     /**
-     * <p>The description of the resource configuration.</p>
+     * <p>A JSON-encoded string that contains the contents for the resource configuration. This string needs to be deserialized using <code>json.loads()</code> before you can access the contents.
+     * </p>
      * @public
      */
     configuration?: string | undefined;
     /**
-     * <p>Configuration attributes that Config returns for certain
+     * <p>A string to string map that contains additional contents for the resource configuration.Config returns this field for certain
      * 			resource types to supplement the information returned for the
-     * 			configuration parameter.</p>
+     * 			<code>configuration</code> field.</p>
+     *          <p>This string needs to be deserialized using <code>json.loads()</code> before you can access the contents.</p>
      * @public
      */
     supplementaryConfiguration?: Record<string, string> | undefined;
     /**
      * <p>The recording frequency that Config uses to record configuration changes for the resource.</p>
+     *          <note>
+     *             <p>This field only appears in the API response when <code>DAILY</code> recording is enabled for a resource type.
+     * 				If this field is not present, <code>CONTINUOUS</code> recording is enabled for that resource type. For more information on daily recording and continuous recording, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/select-resources.html#select-resources-recording-frequency">Recording Frequency</a> in the <i>Config
+     * 						Developer Guide</i>.</p>
+     *          </note>
      * @public
      */
     recordingFrequency?: RecordingFrequency | undefined;
@@ -2458,9 +2465,6 @@ export interface ConfigRule {
      * 			trigger an evaluation for the rule. If you do not specify a scope,
      * 			evaluations are triggered when any resource in the recording group
      * 			changes.</p>
-     *          <note>
-     *             <p>The scope can be empty. </p>
-     *          </note>
      * @public
      */
     Scope?: Scope | undefined;
@@ -3023,19 +3027,25 @@ export interface ConfigurationItem {
      */
     relationships?: Relationship[] | undefined;
     /**
-     * <p>The description of the resource configuration.</p>
+     * <p>A JSON-encoded string that contains the contents for the resource configuration. This string needs to be deserialized using <code>json.loads()</code> before you can access the contents.</p>
      * @public
      */
     configuration?: string | undefined;
     /**
-     * <p>Configuration attributes that Config returns for certain
+     * <p>A string to string map that contains additional contents for the resource configuration.Config returns this field for certain
      * 			resource types to supplement the information returned for the
-     * 				<code>configuration</code> parameter.</p>
+     * 			<code>configuration</code> field.</p>
+     *          <p>This string to string map needs to be deserialized using <code>json.loads()</code> before you can accessing the contents.</p>
      * @public
      */
     supplementaryConfiguration?: Record<string, string> | undefined;
     /**
      * <p>The recording frequency that Config uses to record configuration changes for the resource.</p>
+     *          <note>
+     *             <p>This field only appears in the API response when <code>DAILY</code> recording is enabled for a resource type.
+     * 				If this field is not present, <code>CONTINUOUS</code> recording is enabled for that resource type. For more information on daily recording and continuous recording, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/select-resources.html#select-resources-recording-frequency">Recording Frequency</a> in the <i>Config
+     * 						Developer Guide</i>.</p>
+     *          </note>
      * @public
      */
     recordingFrequency?: RecordingFrequency | undefined;
@@ -3044,7 +3054,8 @@ export interface ConfigurationItem {
      *          <note>
      *             <p>This field is optional and is not guaranteed to be present in a configuration item  (CI). If you are using daily recording,
      * 			this field will be populated. However, if you are using continuous recording,
-     * 			this field will be omitted since the delivery time is instantaneous as the CI is available right away. For more information on daily recording and continuous recording, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/select-resources.html#select-resources-recording-frequency">Recording Frequency</a> in the <i>Config
+     * 			this field will be omitted since the delivery time is instantaneous as the CI is available right away.</p>
+     *             <p>For more information on daily recording and continuous recording, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/select-resources.html#select-resources-recording-frequency">Recording Frequency</a> in the <i>Config
      * 					Developer Guide</i>.</p>
      *          </note>
      * @public
@@ -4642,6 +4653,9 @@ export interface DescribeConfigurationAggregatorSourcesStatusResponse {
 export interface DescribeConfigurationRecordersRequest {
     /**
      * <p>A list of names of the configuration recorders that you want to specify.</p>
+     *          <note>
+     *             <p>When making a request to this operation, you can only specify one configuration recorder.</p>
+     *          </note>
      * @public
      */
     ConfigurationRecorderNames?: string[] | undefined;
@@ -4676,7 +4690,7 @@ export interface DescribeConfigurationRecordersResponse {
 export interface DescribeConfigurationRecorderStatusRequest {
     /**
      * <p>The name of the configuration recorder. If the name is not
-     * 			specified, the opertation returns the status for the customer managed configuration recorder configured for the
+     * 			specified, the operation returns the status for the customer managed configuration recorder configured for the
      * 			account, if applicable.</p>
      *          <note>
      *             <p>When making a request to this operation, you can only specify one configuration recorder.</p>
@@ -7441,7 +7455,7 @@ export interface GetResourceConfigHistoryRequest {
  */
 export interface GetResourceConfigHistoryResponse {
     /**
-     * <p>A list that contains the configuration history of one or more
+     * <p>An array of <code>ConfigurationItems</code> Objects. Contatins the configuration history for one or more
      * 			resources.</p>
      * @public
      */
@@ -7644,8 +7658,7 @@ export declare class InsufficientDeliveryPolicyException extends __BaseException
     constructor(opts: __ExceptionOptionType<InsufficientDeliveryPolicyException, __BaseException>);
 }
 /**
- * <p>You have provided a name for the customer managed configuration recorder that is not
- * 			valid.</p>
+ * <p>The configuration recorder name is not valid. The prefix "<code>AWSConfigurationRecorderFor</code>" is reserved for service-linked configuration recorders.</p>
  * @public
  */
 export declare class InvalidConfigurationRecorderNameException extends __BaseException {

package/dist-types/models/models_1.d.ts

@@ -825,7 +825,7 @@ export interface PutConformancePackRequest {
      */
     TemplateS3Uri?: string | undefined;
     /**
-     * <p>A string containing the full conformance pack template body. The structure containing the template body has a minimum length of 1 byte and a maximum length of 51,200 bytes.</p>
+     * <p>A string that contains the full conformance pack template body. The structure containing the template body has a minimum length of 1 byte and a maximum length of 51,200 bytes.</p>
      *          <note>
      *             <p>You can use a YAML template with two resource types: Config rule (<code>AWS::Config::ConfigRule</code>) and remediation action (<code>AWS::Config::RemediationConfiguration</code>).</p>
      *          </note>
@@ -1014,7 +1014,7 @@ export interface PutOrganizationConformancePackRequest {
      */
     TemplateS3Uri?: string | undefined;
     /**
-     * <p>A string containing full conformance pack template body. Structure containing the template body
+     * <p>A string that contains the full conformance pack template body. Structure containing the template body
      * 			with a minimum length of 1 byte and a maximum length of 51,200 bytes.</p>
      * @public
      */
@@ -1207,7 +1207,7 @@ export interface PutServiceLinkedConfigurationRecorderResponse {
     Arn?: string | undefined;
     /**
      * <p>The name of the specified configuration recorder.</p>
-     *          <p>For service-linked configuration recorders, Config automatically assigns a name that has the prefix "<code>AWS</code>" to the new service-linked configuration recorder.</p>
+     *          <p>For service-linked configuration recorders, Config automatically assigns a name that has the prefix "<code>AWSConfigurationRecorderFor</code>" to the new service-linked configuration recorder.</p>
      * @public
      */
     Name?: string | undefined;
@@ -1446,7 +1446,10 @@ export interface StartResourceEvaluationRequest {
      */
     EvaluationContext?: EvaluationContext | undefined;
     /**
-     * <p>The mode of an evaluation. The valid values for this API are <code>DETECTIVE</code> and <code>PROACTIVE</code>.</p>
+     * <p>The mode of an evaluation.</p>
+     *          <note>
+     *             <p>The only valid value for this API is <code>PROACTIVE</code>.</p>
+     *          </note>
      * @public
      */
     EvaluationMode: EvaluationMode | undefined;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@aws-sdk/client-config-service",
   "description": "AWS SDK for JavaScript Config Service Client for Node.js, Browser and React Native",
-  "version": "3.848.0",
+  "version": "3.854.0",
   "scripts": {
     "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
     "build:cjs": "node ../../scripts/compilation/inline client-config-service",