@aws-sdk/client-config-service 3.138.0 → 3.141.0

package/CHANGELOG.md

@@ -3,6 +3,14 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [3.141.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.140.0...v3.141.0) (2022-08-01)
+
+**Note:** Version bump only for package @aws-sdk/client-config-service
+
+
+
+
+
 # [3.138.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.137.0...v3.138.0) (2022-07-27)
 
 

package/README.md

@@ -187,7 +187,7 @@ try {
   const data = await client.send(command);
   // process data.
 } catch (error) {
-  const { requestId, cfId, extendedRequestId } = error.$metadata;
+  const { requestId, cfId, extendedRequestId } = error.$$metadata;
   console.log({ requestId, cfId, extendedRequestId });
   /**
    * The keys within exceptions are also parsed.

package/dist-types/ConfigService.d.ts

@@ -880,7 +880,10 @@ export declare class ConfigService extends ConfigServiceClient {
      * <p>Returns a list of conformance pack compliance scores.
      * 			A compliance score is the percentage of the number of compliant rule-resource combinations in a conformance pack compared to the number of total possible rule-resource combinations in the conformance pack.
      * 			This metric provides you with a high-level view of the compliance state of your conformance packs, and can be used to identify, investigate, and understand
-     * 			compliance deviations in your conformance packs.</p>
+     * 			the level of compliance in your conformance packs.</p>
+     * 		       <note>
+     *             <p>Conformance packs with no evaluation results will have a compliance score of <code>INSUFFICIENT_DATA</code>.</p>
+     *          </note>
      */
     listConformancePackComplianceScores(args: ListConformancePackComplianceScoresCommandInput, options?: __HttpHandlerOptions): Promise<ListConformancePackComplianceScoresCommandOutput>;
     listConformancePackComplianceScores(args: ListConformancePackComplianceScoresCommandInput, cb: (err: any, data?: ListConformancePackComplianceScoresCommandOutput) => void): void;
@@ -927,23 +930,33 @@ export declare class ConfigService extends ConfigServiceClient {
     putAggregationAuthorization(args: PutAggregationAuthorizationCommandInput, cb: (err: any, data?: PutAggregationAuthorizationCommandOutput) => void): void;
     putAggregationAuthorization(args: PutAggregationAuthorizationCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: PutAggregationAuthorizationCommandOutput) => void): void;
     /**
-     * <p>Adds or updates an Config rule for evaluating whether your
-     * 			Amazon Web Services resources comply with your desired configurations.</p>
-     * 		       <p>You can use this action for Config custom rules and Config
-     * 			managed rules. A Config custom rule is a rule that you
-     * 			develop and maintain. An Config managed rule is a customizable,
-     * 			predefined rule that Config provides.</p>
-     * 		       <p>If you are adding a new Config custom rule, you must first
-     * 			create the Lambda function that the rule invokes to evaluate
-     * 			your resources. When you use the <code>PutConfigRule</code> action
-     * 			to add the rule to Config, you must specify the Amazon Resource
-     * 			Name (ARN) that Lambda assigns to the function. Specify the ARN
-     * 			for the <code>SourceIdentifier</code> key. This key is part of the
-     * 				<code>Source</code> object, which is part of the
-     * 				<code>ConfigRule</code> object. </p>
-     * 		       <p>If you are adding an Config managed rule, specify the
-     * 			rule's identifier for the <code>SourceIdentifier</code> key. To
-     * 			reference Config managed rule identifiers, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config_use-managed-rules.html">About Config managed rules</a>.</p>
+     * <p>Adds or updates an Config rule to evaluate if your
+     * 			Amazon Web Services resources comply with your desired configurations. For information on how many Config rules you can have per account,
+     * 			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>
+     *
+     * 		       <p>There are two types of rules: Config Custom Rules and Config Managed Rules.
+     * 			You can use <code>PutConfigRule</code> to create both Config custom rules and Config managed rules.</p>
+     *
+     * 		       <p>Custom rules are rules that you can create using either Guard or Lambda functions.
+     * 			Guard (<a href="https://github.com/aws-cloudformation/cloudformation-guard">Guard GitHub
+     * 				Repository</a>) is a policy-as-code language that allows you to write policies that
+     * 			are enforced by Config Custom Policy rules. Lambda uses custom code that you upload to
+     * 			evaluate a custom rule. If you are adding a new Custom Lambda rule,
+     * 			you first need to create an Lambda function that the rule invokes to evaluate
+     * 			your resources. When you use <code>PutConfigRule</code> to add a Custom Lambda rule to Config, you must specify the Amazon Resource
+     * 			Name (ARN) that Lambda assigns to the function. You specify the ARN
+     * 			in the <code>SourceIdentifier</code> key. This key is part of the
+     * 			<code>Source</code> object, which is part of the
+     * 			<code>ConfigRule</code> object. </p>
+     *
+     * 		       <p>Managed rules are predefined,
+     * 			customizable rules created by Config. For a list of managed rules, see
+     * 			<a href="https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html">List of Config
+     * 				Managed Rules</a>. If you are adding an Config managed rule, you must specify the
+     * 			rule's identifier for the <code>SourceIdentifier</code> key.</p>
+     *
      * 		       <p>For any new rule that you add, specify the
      * 				<code>ConfigRuleName</code> in the <code>ConfigRule</code>
      * 			object. Do not specify the <code>ConfigRuleArn</code> or the
@@ -953,10 +966,6 @@ export declare class ConfigService extends ConfigServiceClient {
      * 				<code>ConfigRuleId</code>, or <code>ConfigRuleArn</code> in the
      * 				<code>ConfigRule</code> data type that you use in this
      * 			request.</p>
-     * 		       <p>For information on how many Config rules you can have per account,
-     * 			see <a href="https://docs.aws.amazon.com/config/latest/developerguide/configlimits.html">
-     *                <b>Service Limits</b>
-     *             </a> in the Config Developer Guide.</p>
      *
      * 		       <p>For more information about developing and using Config
      * 			rules, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html">Evaluating Amazon Web Services resource Configurations with Config</a>
@@ -980,7 +989,7 @@ export declare class ConfigService extends ConfigServiceClient {
      * 			         <p>If your source type is an organization, you must be signed in to the management account or a registered delegated administrator and all the features must be enabled in your organization.
      * 				If the caller is a management account, Config calls <code>EnableAwsServiceAccess</code> API to enable integration between Config and Organizations.
      * 				If the caller is a registered delegated administrator, Config calls <code>ListDelegatedAdministrators</code> API to verify whether the caller is a valid delegated administrator.</p>
-     * 			         <p>To register a delegated administrator, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/set-up-aggregator-cli.html#register-a-delegated-administrator-cli">Register a Delegated Administrator</a> in the Config developer guide. </p>
+     * 			         <p>To register a delegated administrator, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/set-up-aggregator-cli.html#register-a-delegated-administrator-cli">Register a Delegated Administrator</a> in the <i>Config developer guide</i>. </p>
      * 		       </note>
      */
     putConfigurationAggregator(args: PutConfigurationAggregatorCommandInput, options?: __HttpHandlerOptions): Promise<PutConfigurationAggregatorCommandOutput>;
@@ -1011,8 +1020,8 @@ export declare class ConfigService extends ConfigServiceClient {
      * 			see <a href="https://docs.aws.amazon.com/config/latest/developerguide/configlimits.html">
      *                <b>Service Limits</b>
      *             </a> in the Config Developer Guide.</p>
-     * 		       <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>
+     * 		       <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>
      *             <p>You must specify either the <code>TemplateS3Uri</code> or the <code>TemplateBody</code> parameter, but not both.
      * 			If you provide both Config uses the <code>TemplateS3Uri</code> parameter and ignores the <code>TemplateBody</code> parameter.</p>
@@ -1059,29 +1068,42 @@ export declare class ConfigService extends ConfigServiceClient {
     putExternalEvaluation(args: PutExternalEvaluationCommandInput, cb: (err: any, data?: PutExternalEvaluationCommandOutput) => void): void;
     putExternalEvaluation(args: PutExternalEvaluationCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: PutExternalEvaluationCommandOutput) => void): void;
     /**
-     * <p>Adds or updates organization Config rule for your entire organization evaluating whether your Amazon Web Services resources comply with your
+     * <p>Adds or updates an Config rule for your entire organization to evaluate if your Amazon Web Services resources comply with your
      * 			desired configurations. For information on how many organization Config rules you can have per account,
      * 			see <a href="https://docs.aws.amazon.com/config/latest/developerguide/configlimits.html">
      *                <b>Service Limits</b>
-     *             </a> in the Config Developer Guide.</p>
+     *             </a> in the <i>Config Developer Guide</i>.</p>
      * 	        <p> Only a master account and a delegated administrator can create or update an organization Config rule.
      * 		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>
-     * 		       <p>This API enables organization service access through the <code>EnableAWSServiceAccess</code> action and creates a service linked
+     * 		       <p>This API enables organization service access through the <code>EnableAWSServiceAccess</code> action and creates a service-linked
      * 			role <code>AWSServiceRoleForConfigMultiAccountSetup</code> in the master or delegated administrator account of your organization.
-     * 			The service linked role is created only when the role does not exist in the caller account.
+     * 			The service-linked role is created only when the role does not exist in the caller account.
      * 			Config verifies the existence of role with <code>GetRole</code> action.</p>
      * 		       <p>To use this API with delegated administrator, register a delegated administrator by calling Amazon Web Services Organization
      * 			<code>register-delegated-administrator</code> for <code>config-multiaccountsetup.amazonaws.com</code>. </p>
-     * 		       <p>You can use this action to create both Config custom rules and Config managed rules.
-     * 			If you are adding a new Config custom rule, you must first create Lambda function in the master account or a delegated
-     * 			administrator that the rule invokes to evaluate your resources. You also need to create an IAM role in the managed-account that can be assumed by the Lambda function.
-     * 			When you use the <code>PutOrganizationConfigRule</code> action to add the rule to Config, you must
-     * 			specify the Amazon Resource Name (ARN) that Lambda assigns to the function.
-     * 			If you are adding an Config managed rule, specify the rule's identifier for the <code>RuleIdentifier</code> key.</p>
+     *
+     * 		       <p>There are two types of rules: Config Custom Rules and Config Managed Rules.
+     * 			You can use <code>PutOrganizationConfigRule</code> to create both Config custom rules and Config managed rules.</p>
+     *
+     * 		       <p>Custom rules are rules that you can create using either Guard or Lambda functions.
+     * 			Guard (<a href="https://github.com/aws-cloudformation/cloudformation-guard">Guard GitHub
+     * 				Repository</a>) is a policy-as-code language that allows you to write policies that
+     * 			are enforced by Config Custom Policy rules. Lambda uses custom code that you upload to
+     * 			evaluate a custom rule. If you are adding a new Custom Lambda rule, you first need to create an Lambda function in the master account or a delegated
+     * 		administrator that the rule invokes to evaluate your resources. You also need to create an IAM role in the managed account that can be assumed by the Lambda function.
+     * 		When you use <code>PutOrganizationConfigRule</code> to add a Custom Lambda rule to Config, you must
+     * 			specify the Amazon Resource Name (ARN) that Lambda assigns to the function.</p>
+     *
+     * 		       <p>Managed rules are predefined,
+     * 			customizable rules created by Config. For a list of managed rules, see
+     * 			<a href="https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html">List of Config
+     * 				Managed Rules</a>. If you are adding an Config managed rule, you must specify the rule's identifier for the <code>RuleIdentifier</code> key.</p>
+     *
+     *
      * 		       <note>
      *             <p>Prerequisite: Ensure you call <code>EnableAllFeatures</code> API to enable all features in an organization.</p>
-     * 			         <p>Specify either <code>OrganizationCustomRuleMetadata</code> or <code>OrganizationManagedRuleMetadata</code>.</p>
+     * 			         <p>Make sure to specify one of either <code>OrganizationCustomPolicyRuleMetadata</code> for Custom Policy rules, <code>OrganizationCustomRuleMetadata</code> for Custom Lambda rules, or <code>OrganizationManagedRuleMetadata</code> for managed rules.</p>
      * 			      </note>
      */
     putOrganizationConfigRule(args: PutOrganizationConfigRuleCommandInput, options?: __HttpHandlerOptions): Promise<PutOrganizationConfigRuleCommandOutput>;
@@ -1097,8 +1119,8 @@ export declare class ConfigService extends ConfigServiceClient {
      * 			<code>ListDelegatedAdministrator</code> permissions are added. An organization can have up to 3 delegated administrators.</p>
      * 		       <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 master or delegated administrator account of your organization.
-     * 			The service linked role is created only when the role does not exist in the caller account.
+     * 			service-linked role <code>AWSServiceRoleForConfigMultiAccountSetup</code> in the master or delegated administrator account of your organization.
+     * 			The service-linked role is created only when the role does not exist in the caller account.
      * 			To use this API with delegated administrator, register a delegated administrator by calling Amazon Web Services Organization
      * 			<code>register-delegate-admin</code> for <code>config-multiaccountsetup.amazonaws.com</code>.</p>
      *
@@ -1208,7 +1230,7 @@ export declare class ConfigService extends ConfigServiceClient {
      * 		       <p>For more information about query components, see the
      * 			<a href="https://docs.aws.amazon.com/config/latest/developerguide/query-components.html">
      *                <b>Query Components</b>
-     *             </a> section in the Config Developer Guide.</p>
+     *             </a> section in the <i>Config Developer Guide</i>.</p>
      */
     selectResourceConfig(args: SelectResourceConfigCommandInput, options?: __HttpHandlerOptions): Promise<SelectResourceConfigCommandOutput>;
     selectResourceConfig(args: SelectResourceConfigCommandInput, cb: (err: any, data?: SelectResourceConfigCommandOutput) => void): void;

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

@@ -10,7 +10,10 @@ export interface ListConformancePackComplianceScoresCommandOutput extends ListCo
  * <p>Returns a list of conformance pack compliance scores.
  * 			A compliance score is the percentage of the number of compliant rule-resource combinations in a conformance pack compared to the number of total possible rule-resource combinations in the conformance pack.
  * 			This metric provides you with a high-level view of the compliance state of your conformance packs, and can be used to identify, investigate, and understand
- * 			compliance deviations in your conformance packs.</p>
+ * 			the level of compliance in your conformance packs.</p>
+ * 		       <note>
+ *             <p>Conformance packs with no evaluation results will have a compliance score of <code>INSUFFICIENT_DATA</code>.</p>
+ *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -7,23 +7,33 @@ export interface PutConfigRuleCommandInput extends PutConfigRuleRequest {
 export interface PutConfigRuleCommandOutput extends __MetadataBearer {
 }
 /**
- * <p>Adds or updates an Config rule for evaluating whether your
- * 			Amazon Web Services resources comply with your desired configurations.</p>
- * 		       <p>You can use this action for Config custom rules and Config
- * 			managed rules. A Config custom rule is a rule that you
- * 			develop and maintain. An Config managed rule is a customizable,
- * 			predefined rule that Config provides.</p>
- * 		       <p>If you are adding a new Config custom rule, you must first
- * 			create the Lambda function that the rule invokes to evaluate
- * 			your resources. When you use the <code>PutConfigRule</code> action
- * 			to add the rule to Config, you must specify the Amazon Resource
- * 			Name (ARN) that Lambda assigns to the function. Specify the ARN
- * 			for the <code>SourceIdentifier</code> key. This key is part of the
- * 				<code>Source</code> object, which is part of the
- * 				<code>ConfigRule</code> object. </p>
- * 		       <p>If you are adding an Config managed rule, specify the
- * 			rule's identifier for the <code>SourceIdentifier</code> key. To
- * 			reference Config managed rule identifiers, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config_use-managed-rules.html">About Config managed rules</a>.</p>
+ * <p>Adds or updates an Config rule to evaluate if your
+ * 			Amazon Web Services resources comply with your desired configurations. For information on how many Config rules you can have per account,
+ * 			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>
+ *
+ * 		       <p>There are two types of rules: Config Custom Rules and Config Managed Rules.
+ * 			You can use <code>PutConfigRule</code> to create both Config custom rules and Config managed rules.</p>
+ *
+ * 		       <p>Custom rules are rules that you can create using either Guard or Lambda functions.
+ * 			Guard (<a href="https://github.com/aws-cloudformation/cloudformation-guard">Guard GitHub
+ * 				Repository</a>) is a policy-as-code language that allows you to write policies that
+ * 			are enforced by Config Custom Policy rules. Lambda uses custom code that you upload to
+ * 			evaluate a custom rule. If you are adding a new Custom Lambda rule,
+ * 			you first need to create an Lambda function that the rule invokes to evaluate
+ * 			your resources. When you use <code>PutConfigRule</code> to add a Custom Lambda rule to Config, you must specify the Amazon Resource
+ * 			Name (ARN) that Lambda assigns to the function. You specify the ARN
+ * 			in the <code>SourceIdentifier</code> key. This key is part of the
+ * 			<code>Source</code> object, which is part of the
+ * 			<code>ConfigRule</code> object. </p>
+ *
+ * 		       <p>Managed rules are predefined,
+ * 			customizable rules created by Config. For a list of managed rules, see
+ * 			<a href="https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html">List of Config
+ * 				Managed Rules</a>. If you are adding an Config managed rule, you must specify the
+ * 			rule's identifier for the <code>SourceIdentifier</code> key.</p>
+ *
  * 		       <p>For any new rule that you add, specify the
  * 				<code>ConfigRuleName</code> in the <code>ConfigRule</code>
  * 			object. Do not specify the <code>ConfigRuleArn</code> or the
@@ -33,10 +43,6 @@ export interface PutConfigRuleCommandOutput extends __MetadataBearer {
  * 				<code>ConfigRuleId</code>, or <code>ConfigRuleArn</code> in the
  * 				<code>ConfigRule</code> data type that you use in this
  * 			request.</p>
- * 		       <p>For information on how many Config rules you can have per account,
- * 			see <a href="https://docs.aws.amazon.com/config/latest/developerguide/configlimits.html">
- *                <b>Service Limits</b>
- *             </a> in the Config Developer Guide.</p>
  *
  * 		       <p>For more information about developing and using Config
  * 			rules, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html">Evaluating Amazon Web Services resource Configurations with Config</a>

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

@@ -21,7 +21,7 @@ export interface PutConfigurationAggregatorCommandOutput extends PutConfiguratio
  * 			         <p>If your source type is an organization, you must be signed in to the management account or a registered delegated administrator and all the features must be enabled in your organization.
  * 				If the caller is a management account, Config calls <code>EnableAwsServiceAccess</code> API to enable integration between Config and Organizations.
  * 				If the caller is a registered delegated administrator, Config calls <code>ListDelegatedAdministrators</code> API to verify whether the caller is a valid delegated administrator.</p>
- * 			         <p>To register a delegated administrator, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/set-up-aggregator-cli.html#register-a-delegated-administrator-cli">Register a Delegated Administrator</a> in the Config developer guide. </p>
+ * 			         <p>To register a delegated administrator, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/set-up-aggregator-cli.html#register-a-delegated-administrator-cli">Register a Delegated Administrator</a> in the <i>Config developer guide</i>. </p>
  * 		       </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

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

@@ -13,8 +13,8 @@ export interface PutConformancePackCommandOutput extends PutConformancePackRespo
  * 			see <a href="https://docs.aws.amazon.com/config/latest/developerguide/configlimits.html">
  *                <b>Service Limits</b>
  *             </a> in the Config Developer Guide.</p>
- * 		       <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>
+ * 		       <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>
  *             <p>You must specify either the <code>TemplateS3Uri</code> or the <code>TemplateBody</code> parameter, but not both.
  * 			If you provide both Config uses the <code>TemplateS3Uri</code> parameter and ignores the <code>TemplateBody</code> parameter.</p>

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

@@ -7,29 +7,42 @@ export interface PutOrganizationConfigRuleCommandInput extends PutOrganizationCo
 export interface PutOrganizationConfigRuleCommandOutput extends PutOrganizationConfigRuleResponse, __MetadataBearer {
 }
 /**
- * <p>Adds or updates organization Config rule for your entire organization evaluating whether your Amazon Web Services resources comply with your
+ * <p>Adds or updates an Config rule for your entire organization to evaluate if your Amazon Web Services resources comply with your
  * 			desired configurations. For information on how many organization Config rules you can have per account,
  * 			see <a href="https://docs.aws.amazon.com/config/latest/developerguide/configlimits.html">
  *                <b>Service Limits</b>
- *             </a> in the Config Developer Guide.</p>
+ *             </a> in the <i>Config Developer Guide</i>.</p>
  * 	        <p> Only a master account and a delegated administrator can create or update an organization Config rule.
  * 		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>
- * 		       <p>This API enables organization service access through the <code>EnableAWSServiceAccess</code> action and creates a service linked
+ * 		       <p>This API enables organization service access through the <code>EnableAWSServiceAccess</code> action and creates a service-linked
  * 			role <code>AWSServiceRoleForConfigMultiAccountSetup</code> in the master or delegated administrator account of your organization.
- * 			The service linked role is created only when the role does not exist in the caller account.
+ * 			The service-linked role is created only when the role does not exist in the caller account.
  * 			Config verifies the existence of role with <code>GetRole</code> action.</p>
  * 		       <p>To use this API with delegated administrator, register a delegated administrator by calling Amazon Web Services Organization
  * 			<code>register-delegated-administrator</code> for <code>config-multiaccountsetup.amazonaws.com</code>. </p>
- * 		       <p>You can use this action to create both Config custom rules and Config managed rules.
- * 			If you are adding a new Config custom rule, you must first create Lambda function in the master account or a delegated
- * 			administrator that the rule invokes to evaluate your resources. You also need to create an IAM role in the managed-account that can be assumed by the Lambda function.
- * 			When you use the <code>PutOrganizationConfigRule</code> action to add the rule to Config, you must
- * 			specify the Amazon Resource Name (ARN) that Lambda assigns to the function.
- * 			If you are adding an Config managed rule, specify the rule's identifier for the <code>RuleIdentifier</code> key.</p>
+ *
+ * 		       <p>There are two types of rules: Config Custom Rules and Config Managed Rules.
+ * 			You can use <code>PutOrganizationConfigRule</code> to create both Config custom rules and Config managed rules.</p>
+ *
+ * 		       <p>Custom rules are rules that you can create using either Guard or Lambda functions.
+ * 			Guard (<a href="https://github.com/aws-cloudformation/cloudformation-guard">Guard GitHub
+ * 				Repository</a>) is a policy-as-code language that allows you to write policies that
+ * 			are enforced by Config Custom Policy rules. Lambda uses custom code that you upload to
+ * 			evaluate a custom rule. If you are adding a new Custom Lambda rule, you first need to create an Lambda function in the master account or a delegated
+ * 		administrator that the rule invokes to evaluate your resources. You also need to create an IAM role in the managed account that can be assumed by the Lambda function.
+ * 		When you use <code>PutOrganizationConfigRule</code> to add a Custom Lambda rule to Config, you must
+ * 			specify the Amazon Resource Name (ARN) that Lambda assigns to the function.</p>
+ *
+ * 		       <p>Managed rules are predefined,
+ * 			customizable rules created by Config. For a list of managed rules, see
+ * 			<a href="https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html">List of Config
+ * 				Managed Rules</a>. If you are adding an Config managed rule, you must specify the rule's identifier for the <code>RuleIdentifier</code> key.</p>
+ *
+ *
  * 		       <note>
  *             <p>Prerequisite: Ensure you call <code>EnableAllFeatures</code> API to enable all features in an organization.</p>
- * 			         <p>Specify either <code>OrganizationCustomRuleMetadata</code> or <code>OrganizationManagedRuleMetadata</code>.</p>
+ * 			         <p>Make sure to specify one of either <code>OrganizationCustomPolicyRuleMetadata</code> for Custom Policy rules, <code>OrganizationCustomRuleMetadata</code> for Custom Lambda rules, or <code>OrganizationManagedRuleMetadata</code> for managed rules.</p>
  * 			      </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

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

@@ -16,8 +16,8 @@ export interface PutOrganizationConformancePackCommandOutput extends PutOrganiza
  * 			<code>ListDelegatedAdministrator</code> permissions are added. An organization can have up to 3 delegated administrators.</p>
  * 		       <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 master or delegated administrator account of your organization.
- * 			The service linked role is created only when the role does not exist in the caller account.
+ * 			service-linked role <code>AWSServiceRoleForConfigMultiAccountSetup</code> in the master or delegated administrator account of your organization.
+ * 			The service-linked role is created only when the role does not exist in the caller account.
  * 			To use this API with delegated administrator, register a delegated administrator by calling Amazon Web Services Organization
  * 			<code>register-delegate-admin</code> for <code>config-multiaccountsetup.amazonaws.com</code>.</p>
  *

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

@@ -11,7 +11,7 @@ export interface SelectResourceConfigCommandOutput extends SelectResourceConfigR
  * 		       <p>For more information about query components, see the
  * 			<a href="https://docs.aws.amazon.com/config/latest/developerguide/query-components.html">
  *                <b>Query Components</b>
- *             </a> section in the Config Developer Guide.</p>
+ *             </a> section in the <i>Config Developer Guide</i>.</p>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -1029,7 +1029,7 @@ export interface SourceDetail {
     MaximumExecutionFrequency?: MaximumExecutionFrequency | string;
 }
 /**
- * <p>Provides the CustomPolicyDetails, the rule owner (Amazon Web Services or customer), the rule
+ * <p>Provides the CustomPolicyDetails, the rule owner (<code>Amazon Web Services</code> for managed rules, <code>CUSTOM_POLICY</code> for Custom Policy rules, and <code>CUSTOM_LAMBDA</code> for Custom Lambda rules), the rule
  * 			identifier, and the events that cause the evaluation of your Amazon Web Services
  * 			resources.</p>
  */
@@ -1037,9 +1037,9 @@ export interface Source {
     /**
      * <p>Indicates whether Amazon Web Services or the customer owns and manages the Config rule.</p>
      *
-     * 		       <p>Config Managed Rules are predefined rules owned by Amazon Web Services. For more information, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config_use-managed-rules.html">Config Managed Rules</a> in the Config developer guide.</p>
+     * 		       <p>Config Managed Rules are predefined rules owned by Amazon Web Services. For more information, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config_use-managed-rules.html">Config Managed Rules</a> in the <i>Config developer guide</i>.</p>
      *
-     * 		       <p>Config Custom Rules are rules that you can develop either with Guard (<code>CUSTOM_POLICY</code>) or Lambda (<code>CUSTOM_LAMBDA</code>). For more information, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config_develop-rules.html">Config Custom Rules </a> in the Config developer guide.</p>
+     * 		       <p>Config Custom Rules are rules that you can develop either with Guard (<code>CUSTOM_POLICY</code>) or Lambda (<code>CUSTOM_LAMBDA</code>). For more information, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config_develop-rules.html">Config Custom Rules </a> in the <i>Config developer guide</i>.</p>
      */
     Owner: Owner | string | undefined;
     /**
@@ -1065,22 +1065,28 @@ export interface Source {
     CustomPolicyDetails?: CustomPolicyDetails;
 }
 /**
- * <p>An Config rule represents an Lambda function that you
- * 			create for a custom rule or a predefined function for an Config managed
- * 			rule. The function evaluates configuration items to assess whether
- * 			your Amazon Web Services resources comply with your desired configurations. This
- * 			function can run when Config detects a configuration change to
- * 			an Amazon Web Services resource and at a periodic frequency that you choose (for
- * 			example, every 24 hours).</p>
+ * <p>Config rules evaluate the configuration settings of your Amazon Web Services resources. A rule can run when Config detects a configuration change to
+ * 			an Amazon Web Services resource or at a periodic frequency that you choose (for
+ * 			example, every 24 hours). There are two types of rules: Config Managed Rules and Config Custom Rules.
+ * 			Managed rules are predefined, customizable rules created by Config. For a list of managed rules, see
+ * 				<a href="https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html">List of Config
+ * 					Managed Rules</a>.</p>
+ *
+ * 		       <p>Custom rules are rules that you can create using either Guard or Lambda functions.
+ * 			Guard (<a href="https://github.com/aws-cloudformation/cloudformation-guard">Guard GitHub
+ * 				Repository</a>) is a policy-as-code language that allows you to write policies that
+ * 			are enforced by Config Custom Policy rules. Lambda uses custom code that you upload to
+ * 			evaluate a custom rule. It is invoked by events that are published to it by an event source, which Config invokes when the custom rule is initiated.</p>
+ *
+ * 		       <p>For more information about developing and using Config
+ * 			rules, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html">Evaluating Amazon Web Services resource Configurations with Config</a>
+ * 			in the <i>Config Developer Guide</i>.</p>
  *
  * 		       <note>
  * 			         <p>You can use the Amazon Web Services CLI and Amazon Web Services SDKs if you want to create
  * 				a rule that triggers evaluations for your resources when Config delivers the configuration snapshot. For more
  * 				information, see <a>ConfigSnapshotDeliveryProperties</a>.</p>
  * 		       </note>
- * 		       <p>For more information about developing and using Config
- * 			rules, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html">Evaluating Amazon Web Services resource Configurations with Config</a>
- * 			in the <i>Config Developer Guide</i>.</p>
  */
 export interface ConfigRule {
     /**
@@ -1116,7 +1122,7 @@ export interface ConfigRule {
      */
     Scope?: Scope;
     /**
-     * <p>Provides the rule owner (Amazon Web Services or customer), the rule identifier,
+     * <p>Provides the rule owner (<code>Amazon Web Services</code> for managed rules, <code>CUSTOM_POLICY</code> for Custom Policy rules, and <code>CUSTOM_LAMBDA</code> for Custom Lambda rules), the rule identifier,
      * 			and the notifications that cause the function to evaluate your Amazon Web Services
      * 			resources.</p>
      */
@@ -1177,7 +1183,7 @@ export interface ConfigRule {
      * <p>Service principal name of the service that created the
      * 			rule.</p>
      * 		       <note>
-     * 			         <p>The field is populated only if the service linked rule is
+     * 			         <p>The field is populated only if the service-linked rule is
      * 				created by a service. The field is empty if you create your own
      * 				rule.</p>
      * 		       </note>
@@ -1779,11 +1785,11 @@ export interface ConformancePackComplianceFilters {
 /**
  * <p>A compliance score is the percentage of the number of compliant rule-resource combinations in a conformance pack compared to the number of total possible rule-resource combinations in the conformance pack.
  * 			This metric provides you with a high-level view of the compliance state of your conformance packs, and can be used to identify, investigate, and understand
- * 			compliance deviations in your conformance packs.</p>
+ * 			the level of compliance in your conformance packs.</p>
  */
 export interface ConformancePackComplianceScore {
     /**
-     * <p>Compliance score for the conformance pack.</p>
+     * <p>Compliance score for the conformance pack. Conformance packs with no evaluation results will have a compliance score of <code>INSUFFICIENT_DATA</code>.</p>
      */
     Score?: string;
     /**
@@ -1796,11 +1802,12 @@ export interface ConformancePackComplianceScore {
     LastUpdatedTime?: Date;
 }
 /**
- * <p>A list of filters to apply to the conformance pack compliance score result set.</p>
+ * <p>A list of filters to apply to the conformance pack compliance score result set. </p>
  */
 export interface ConformancePackComplianceScoresFilters {
     /**
-     * <p>The name of a conformance pack whose score should be included in the compliance score result.</p>
+     * <p>The names of the conformance packs whose compliance scores you want to include in the conformance pack compliance score result set.
+     * 			You can include up to 25 conformance packs in the <code>ConformancePackNames</code> array of strings, each with a character limit of 256 characters for the conformance pack name.</p>
      */
     ConformancePackNames: string[] | undefined;
 }
@@ -2289,13 +2296,13 @@ export interface DeleteRemediationConfigurationResponse {
  *                <p>For PutConfigRule, the Lambda function cannot be invoked. Check the function ARN, and check the function's permissions.</p>
  *             </li>
  *             <li>
- *                <p>For PutOrganizationConfigRule, organization Config rule cannot be created because you do not have permissions to call IAM <code>GetRole</code> action or create a service linked role.</p>
+ *                <p>For PutOrganizationConfigRule, organization Config rule cannot be created because you do not have permissions to call IAM <code>GetRole</code> action or create a service-linked role.</p>
  *             </li>
  *             <li>
  *                <p>For PutConformancePack and PutOrganizationConformancePack, a conformance pack cannot be created because you do not have permissions: </p>
  * 				           <ul>
  *                   <li>
- *                      <p>To call IAM <code>GetRole</code> action or create a service linked role.</p>
+ *                      <p>To call IAM <code>GetRole</code> action or create a service-linked role.</p>
  *                   </li>
  *                   <li>
  *                      <p>To read Amazon S3 bucket.</p>
@@ -2483,8 +2490,8 @@ export interface DeliveryChannel {
      * <p>The name of the Amazon S3 bucket to which Config delivers
      * 			configuration snapshots and configuration history files.</p>
      * 		       <p>If you specify a bucket that belongs to another Amazon Web Services account,
-     * 			that bucket must have policies that grant access permissions to Config. For more information, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/s3-bucket-policy.html">Permissions for the Amazon S3 Bucket</a> in the Config
-     * 			Developer Guide.</p>
+     * 			that bucket must have policies that grant access permissions to Config. For more information, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/s3-bucket-policy.html">Permissions for the Amazon S3 Bucket</a> in the <i>Config
+     * 			Developer Guide</i>.</p>
      */
     s3BucketName?: string;
     /**
@@ -2502,8 +2509,8 @@ export interface DeliveryChannel {
      * 			changes.</p>
      * 		       <p>If you choose a topic from another account, the topic must have
      * 			policies that grant access permissions to Config. For more
-     * 			information, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/sns-topic-policy.html">Permissions for the Amazon SNS Topic</a> in the Config
-     * 			Developer Guide.</p>
+     * 			information, see <a href="https://docs.aws.amazon.com/config/latest/developerguide/sns-topic-policy.html">Permissions for the Amazon SNS Topic</a> in the <i>Config
+     * 			Developer Guide</i>.</p>
      */
     snsTopicARN?: string;
     /**
@@ -3750,7 +3757,7 @@ export interface RemediationConfiguration {
      */
     Arn?: string;
     /**
-     * <p>Name of the service that owns the service linked rule, if applicable.</p>
+     * <p>Name of the service that owns the service-linked rule, if applicable.</p>
      */
     CreatedByService?: string;
 }
@@ -5281,10 +5288,12 @@ export interface ListConformancePackComplianceScoresRequest {
     Filters?: ConformancePackComplianceScoresFilters;
     /**
      * <p>Determines the order in which conformance pack compliance scores are sorted. Either in ascending or descending order.</p>
+     * 		       <p>Conformance packs with a compliance score of <code>INSUFFICIENT_DATA</code> will be first when sorting by ascending order and last when sorting by descending order.</p>
      */
     SortOrder?: SortOrder | string;
     /**
      * <p>Sorts your conformance pack compliance scores in either ascending or descending order, depending on <code>SortOrder</code>.</p>
+     * 		       <p>By default, conformance pack compliance scores are sorted in ascending order by compliance score and alphabetically by name of the conformance pack if there is more than one conformance pack with the same compliance score.</p>
      */
     SortBy?: SortBy | string;
     /**
@@ -5302,7 +5311,7 @@ export interface ListConformancePackComplianceScoresResponse {
      */
     NextToken?: string;
     /**
-     * <p>A list of <code>ConformancePackComplianceScore</code> objects</p>
+     * <p>A list of <code>ConformancePackComplianceScore</code> objects.</p>
      */
     ConformancePackComplianceScores: ConformancePackComplianceScore[] | undefined;
 }

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

@@ -78,11 +78,15 @@ export interface PutOrganizationConfigRuleRequest {
      */
     OrganizationConfigRuleName: string | undefined;
     /**
-     * <p>An <code>OrganizationManagedRuleMetadata</code> object. </p>
+     * <p>An <code>OrganizationManagedRuleMetadata</code> object. This object specifies organization
+     * 			managed rule metadata such as resource type and ID of Amazon Web Services resource along with the rule identifier.
+     * 			It also provides the frequency with which you want Config to run evaluations for the rule if the trigger type is periodic.</p>
      */
     OrganizationManagedRuleMetadata?: OrganizationManagedRuleMetadata;
     /**
-     * <p>An <code>OrganizationCustomRuleMetadata</code> object.</p>
+     * <p>An <code>OrganizationCustomRuleMetadata</code> object. This object specifies organization custom rule metadata such as resource type,
+     * 			resource ID of Amazon Web Services resource, Lambda function ARN, and organization trigger types that trigger Config to evaluate your Amazon Web Services resources against a rule.
+     * 			It also provides the frequency with which you want Config to run evaluations for the rule if the trigger type is periodic.</p>
      */
     OrganizationCustomRuleMetadata?: OrganizationCustomRuleMetadata;
     /**
@@ -90,9 +94,9 @@ export interface PutOrganizationConfigRuleRequest {
      */
     ExcludedAccounts?: string[];
     /**
-     * <p>An object that specifies metadata for your organization's Config Custom Policy rule. The metadata includes the runtime system in use, which accounts have debug
+     * <p>An <code>OrganizationCustomPolicyRuleMetadata</code> object. This object specifies metadata for your organization's Config Custom Policy rule. The metadata includes the runtime system in use, which accounts have debug
      * 			logging enabled, and other custom rule metadata, such as resource type, resource ID of
-     * 				Amazon Web Services resource, and organization trigger types that initiate Config to evaluate Amazon Web Services resources against a rule.</p>
+     * 			Amazon Web Services resource, and organization trigger types that initiate Config to evaluate Amazon Web Services resources against a rule.</p>
      */
     OrganizationCustomPolicyRuleMetadata?: OrganizationCustomPolicyRuleMetadata;
 }

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.138.0",
+  "version": "3.141.0",
   "scripts": {
     "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
     "build:cjs": "tsc -p tsconfig.cjs.json",
@@ -18,9 +18,9 @@
   "dependencies": {
     "@aws-crypto/sha256-browser": "2.0.0",
     "@aws-crypto/sha256-js": "2.0.0",
-    "@aws-sdk/client-sts": "3.137.0",
+    "@aws-sdk/client-sts": "3.141.0",
     "@aws-sdk/config-resolver": "3.130.0",
-    "@aws-sdk/credential-provider-node": "3.137.0",
+    "@aws-sdk/credential-provider-node": "3.141.0",
     "@aws-sdk/fetch-http-handler": "3.131.0",
     "@aws-sdk/hash-node": "3.127.0",
     "@aws-sdk/invalid-dependency": "3.127.0",