@aws-sdk/client-config-service 3.121.0 → 3.123.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.123.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.122.0...v3.123.0) (2022-07-05)
+
+**Note:** Version bump only for package @aws-sdk/client-config-service
+
+
+
+
+
 # [3.121.0](https://github.com/aws/aws-sdk-js-v3/compare/v3.120.0...v3.121.0) (2022-06-30)
 
 

package/dist-types/ConfigService.d.ts

@@ -526,10 +526,25 @@ export declare class ConfigService extends ConfigServiceClient {
      * <p>Returns a list of organization Config rules. </p>
      *
      * 		       <note>
-     *             <p>When you specify the limit and the next token, you receive a paginated response.
-     * 			Limit and next token are not applicable if you specify organization Config rule names.
+     *             <p>When you specify the limit and the next token, you receive a paginated response.</p>
+     * 			         <p>Limit and next token are not applicable if you specify organization Config rule names.
      * 			It is only applicable, when you request all the organization Config rules.</p>
-     *          </note>
+     *
+     * 			         <p>
+     *                <i>For accounts within an organzation</i>
+     *             </p>
+     *
+     * 			         <p>If you deploy an organizational rule or conformance pack in an organization
+     * 				administrator account, and then establish a delegated administrator and deploy an
+     * 				organizational rule or conformance pack in the delegated administrator account, you
+     * 				won't be able to see the organizational rule or conformance pack in the organization
+     * 				administrator account from the delegated administrator account or see the organizational
+     * 				rule or conformance pack in the delegated administrator account from organization
+     * 				administrator account. The <code>DescribeOrganizationConfigRules</code> and
+     * 				<code>DescribeOrganizationConformancePacks</code> APIs can only see and interact with
+     * 				the organization-related resource that were deployed from within the account calling
+     * 				those APIs.</p>
+     * 		       </note>
      */
     describeOrganizationConfigRules(args: DescribeOrganizationConfigRulesCommandInput, options?: __HttpHandlerOptions): Promise<DescribeOrganizationConfigRulesCommandOutput>;
     describeOrganizationConfigRules(args: DescribeOrganizationConfigRulesCommandInput, cb: (err: any, data?: DescribeOrganizationConfigRulesCommandOutput) => void): void;
@@ -554,7 +569,22 @@ export declare class ConfigService extends ConfigServiceClient {
      *             <p>When you specify the limit and the next token, you receive a paginated response. </p>
      * 			         <p>Limit and next token are not applicable if you specify organization conformance packs names. They are only applicable,
      * 			when you request all the organization conformance packs. </p>
-     *          </note>
+     *
+     * 			         <p>
+     *                <i>For accounts within an organzation</i>
+     *             </p>
+     *
+     * 			         <p>If you deploy an organizational rule or conformance pack in an organization
+     * 				administrator account, and then establish a delegated administrator and deploy an
+     * 				organizational rule or conformance pack in the delegated administrator account, you
+     * 				won't be able to see the organizational rule or conformance pack in the organization
+     * 				administrator account from the delegated administrator account or see the organizational
+     * 				rule or conformance pack in the delegated administrator account from organization
+     * 				administrator account. The <code>DescribeOrganizationConfigRules</code> and
+     * 				<code>DescribeOrganizationConformancePacks</code> APIs can only see and interact with
+     * 				the organization-related resource that were deployed from within the account calling
+     * 				those APIs.</p>
+     * 		       </note>
      */
     describeOrganizationConformancePacks(args: DescribeOrganizationConformancePacksCommandInput, options?: __HttpHandlerOptions): Promise<DescribeOrganizationConformancePacksCommandOutput>;
     describeOrganizationConformancePacks(args: DescribeOrganizationConformancePacksCommandInput, cb: (err: any, data?: DescribeOrganizationConformancePacksCommandOutput) => void): void;
@@ -1043,10 +1073,13 @@ export declare class ConfigService extends ConfigServiceClient {
     putOrganizationConfigRule(args: PutOrganizationConfigRuleCommandInput, cb: (err: any, data?: PutOrganizationConfigRuleCommandOutput) => void): void;
     putOrganizationConfigRule(args: PutOrganizationConfigRuleCommandInput, options: __HttpHandlerOptions, cb: (err: any, data?: PutOrganizationConfigRuleCommandOutput) => void): void;
     /**
-     * <p>Deploys conformance packs across member accounts in an Amazon Web Services Organization.</p>
+     * <p>Deploys conformance packs across member accounts in an Amazon Web Services Organization. For information on how many organization conformance packs and 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>Only a master 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.</p>
+     * 			<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.
@@ -1062,7 +1095,6 @@ export declare class ConfigService extends ConfigServiceClient {
      * 			If you provide both Config uses the <code>TemplateS3Uri</code> parameter and ignores the <code>TemplateBody</code> parameter.</p>
      * 			         <p>Config sets the state of a conformance pack to CREATE_IN_PROGRESS and UPDATE_IN_PROGRESS until the conformance pack is created or updated.
      * 				You cannot update a conformance pack while it is in this state.</p>
-     * 			         <p>You can create 50 conformance packs with 25 Config rules in each pack and 3 delegated administrator per organization. </p>
      *          </note>
      */
     putOrganizationConformancePack(args: PutOrganizationConformancePackCommandInput, options?: __HttpHandlerOptions): Promise<PutOrganizationConformancePackCommandOutput>;
@@ -1080,6 +1112,10 @@ export declare class ConfigService extends ConfigServiceClient {
      * 			         <p>This API does not support adding remediation configurations for service-linked Config Rules such as Organization Config rules,
      * 				the rules deployed by conformance packs, and rules deployed by Amazon Web Services Security Hub.</p>
      *          </note>
+     * 		       <note>
+     *             <p>For manual remediation configuration, you need to provide a value for <code>automationAssumeRole</code> or use a value in the <code>assumeRole</code>field  to remediate your resources. The SSM automation document can use either as long as it maps to a valid parameter.</p>
+     * 			         <p>However, for automatic remediation configuration, the only valid <code>assumeRole</code> field value is <code>AutomationAssumeRole</code> and you need to provide a value for <code>AutomationAssumeRole</code> to remediate your resources.</p>
+     * 		       </note>
      */
     putRemediationConfigurations(args: PutRemediationConfigurationsCommandInput, options?: __HttpHandlerOptions): Promise<PutRemediationConfigurationsCommandOutput>;
     putRemediationConfigurations(args: PutRemediationConfigurationsCommandInput, cb: (err: any, data?: PutRemediationConfigurationsCommandOutput) => void): void;

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

@@ -10,10 +10,25 @@ export interface DescribeOrganizationConfigRulesCommandOutput extends DescribeOr
  * <p>Returns a list of organization Config rules. </p>
  *
  * 		       <note>
- *             <p>When you specify the limit and the next token, you receive a paginated response.
- * 			Limit and next token are not applicable if you specify organization Config rule names.
+ *             <p>When you specify the limit and the next token, you receive a paginated response.</p>
+ * 			         <p>Limit and next token are not applicable if you specify organization Config rule names.
  * 			It is only applicable, when you request all the organization Config rules.</p>
- *          </note>
+ *
+ * 			         <p>
+ *                <i>For accounts within an organzation</i>
+ *             </p>
+ *
+ * 			         <p>If you deploy an organizational rule or conformance pack in an organization
+ * 				administrator account, and then establish a delegated administrator and deploy an
+ * 				organizational rule or conformance pack in the delegated administrator account, you
+ * 				won't be able to see the organizational rule or conformance pack in the organization
+ * 				administrator account from the delegated administrator account or see the organizational
+ * 				rule or conformance pack in the delegated administrator account from organization
+ * 				administrator account. The <code>DescribeOrganizationConfigRules</code> and
+ * 				<code>DescribeOrganizationConformancePacks</code> APIs can only see and interact with
+ * 				the organization-related resource that were deployed from within the account calling
+ * 				those APIs.</p>
+ * 		       </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -12,7 +12,22 @@ export interface DescribeOrganizationConformancePacksCommandOutput extends Descr
  *             <p>When you specify the limit and the next token, you receive a paginated response. </p>
  * 			         <p>Limit and next token are not applicable if you specify organization conformance packs names. They are only applicable,
  * 			when you request all the organization conformance packs. </p>
- *          </note>
+ *
+ * 			         <p>
+ *                <i>For accounts within an organzation</i>
+ *             </p>
+ *
+ * 			         <p>If you deploy an organizational rule or conformance pack in an organization
+ * 				administrator account, and then establish a delegated administrator and deploy an
+ * 				organizational rule or conformance pack in the delegated administrator account, you
+ * 				won't be able to see the organizational rule or conformance pack in the organization
+ * 				administrator account from the delegated administrator account or see the organizational
+ * 				rule or conformance pack in the delegated administrator account from organization
+ * 				administrator account. The <code>DescribeOrganizationConfigRules</code> and
+ * 				<code>DescribeOrganizationConformancePacks</code> APIs can only see and interact with
+ * 				the organization-related resource that were deployed from within the account calling
+ * 				those APIs.</p>
+ * 		       </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.
  * ```javascript

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

@@ -7,10 +7,13 @@ export interface PutOrganizationConformancePackCommandInput extends PutOrganizat
 export interface PutOrganizationConformancePackCommandOutput extends PutOrganizationConformancePackResponse, __MetadataBearer {
 }
 /**
- * <p>Deploys conformance packs across member accounts in an Amazon Web Services Organization.</p>
+ * <p>Deploys conformance packs across member accounts in an Amazon Web Services Organization. For information on how many organization conformance packs and 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>Only a master 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.</p>
+ * 			<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.
@@ -26,7 +29,6 @@ export interface PutOrganizationConformancePackCommandOutput extends PutOrganiza
  * 			If you provide both Config uses the <code>TemplateS3Uri</code> parameter and ignores the <code>TemplateBody</code> parameter.</p>
  * 			         <p>Config sets the state of a conformance pack to CREATE_IN_PROGRESS and UPDATE_IN_PROGRESS until the conformance pack is created or updated.
  * 				You cannot update a conformance pack while it is in this state.</p>
- * 			         <p>You can create 50 conformance packs with 25 Config rules in each pack and 3 delegated administrator per organization. </p>
  *          </note>
  * @example
  * Use a bare-bones client and the command you need to make an API call.

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

@@ -18,6 +18,10 @@ export interface PutRemediationConfigurationsCommandOutput extends PutRemediatio
  * 			         <p>This API does not support adding remediation configurations for service-linked Config Rules such as Organization Config rules,
  * 				the rules deployed by conformance packs, and rules deployed by Amazon Web Services Security Hub.</p>
  *          </note>
+ * 		       <note>
+ *             <p>For manual remediation configuration, you need to provide a value for <code>automationAssumeRole</code> or use a value in the <code>assumeRole</code>field  to remediate your resources. The SSM automation document can use either as long as it maps to a valid parameter.</p>
+ * 			         <p>However, for automatic remediation configuration, the only valid <code>assumeRole</code> field value is <code>AutomationAssumeRole</code> and you need to provide a value for <code>AutomationAssumeRole</code> to remediate your resources.</p>
+ * 		       </note>
  * @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

@@ -1309,7 +1309,7 @@ export interface ConfigRule {
      * 				<code>MaximumExecutionFrequency</code> when:</p>
      * 		       <ul>
      *             <li>
-     * 				           <p>You are using an Config managed rule that is triggered at
+     * 				           <p>This is for an Config managed rule that is triggered at
      * 					a periodic frequency.</p>
      * 			         </li>
      *             <li>
@@ -1950,6 +1950,9 @@ export interface ConfigurationRecorder {
     /**
      * <p>Amazon Resource Name (ARN) of the IAM role used to describe the
      * 			Amazon Web Services resources associated with the account.</p>
+     * 		       <note>
+     *             <p>While the API model does not require this field, the server will reject a request without a defined roleARN for the configuration recorder.</p>
+     *          </note>
      */
     roleARN?: string;
     /**
@@ -3867,7 +3870,7 @@ export interface OrganizationManagedRuleMetadata {
      */
     InputParameters?: string;
     /**
-     * <p>The maximum frequency with which Config runs evaluations for a rule. You are using an Config managed rule that is triggered at a periodic frequency.</p>
+     * <p>The maximum frequency with which Config runs evaluations for a rule. This is for an Config managed rule that is triggered at a periodic frequency.</p>
      * 		       <note>
      *             <p>By default, rules with a periodic trigger are evaluated every 24 hours. To change the frequency, specify a valid
      * 			value for the <code>MaximumExecutionFrequency</code> parameter.</p>

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

@@ -191,6 +191,10 @@ export interface PutResourceConfigRequest {
     Configuration: string | undefined;
     /**
      * <p>Tags associated with the resource.</p>
+     * 		       <note>
+     *             <p>This field is not to be confused with the Amazon Web Services-wide tag feature for Amazon Web Services resources.
+     * 			Tags for <code>PutResourceConfig</code> are tags that you supply for the configuration items of your custom resources.</p>
+     *          </note>
      */
     Tags?: Record<string, string>;
 }

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.121.0",
+  "version": "3.123.0",
   "scripts": {
     "build": "concurrently 'yarn:build:cjs' 'yarn:build:es' 'yarn:build:types'",
     "build:cjs": "tsc -p tsconfig.cjs.json",