docs(client-config-service): Updating documentation service limits

Author: awstools

clients/client-config-service/src/ConfigService.ts

@@ -1767,10 +1767,25 @@ export 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>
    */
   public describeOrganizationConfigRules(
     args: DescribeOrganizationConfigRulesCommandInput,
@@ -1849,7 +1864,22 @@ export 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>
    */
   public describeOrganizationConformancePacks(
     args: DescribeOrganizationConformancePacksCommandInput,
@@ -3338,10 +3368,13 @@ export class ConfigService extends ConfigServiceClient {
   }
 
   /**
-   * <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.
@@ -3357,7 +3390,6 @@ export 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>
    */
   public putOrganizationConformancePack(
@@ -3401,6 +3433,10 @@ export 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>
    */
   public putRemediationConfigurations(
     args: PutRemediationConfigurationsCommandInput,

clients/client-config-service/src/commands/DescribeOrganizationConfigRulesCommand.ts

@@ -28,10 +28,25 @@ export interface DescribeOrganizationConfigRulesCommandOutput
  * <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

clients/client-config-service/src/commands/DescribeOrganizationConformancePacksCommand.ts

@@ -33,7 +33,22 @@ export interface DescribeOrganizationConformancePacksCommandOutput
  *             <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

clients/client-config-service/src/commands/PutOrganizationConformancePackCommand.ts

@@ -25,10 +25,13 @@ export interface PutOrganizationConformancePackCommandOutput
     __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.
@@ -44,7 +47,6 @@ export interface PutOrganizationConformancePackCommandOutput
  * 			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.

clients/client-config-service/src/commands/PutRemediationConfigurationsCommand.ts

@@ -36,6 +36,10 @@ export interface PutRemediationConfigurationsCommandOutput
  * 			         <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

clients/client-config-service/src/models/models_0.ts

@@ -1565,7 +1565,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>
@@ -2305,6 +2305,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;
 
@@ -4783,7 +4786,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>

clients/client-config-service/src/models/models_1.ts

@@ -258,6 +258,10 @@ export interface PutResourceConfigRequest {
 
   /**
    * <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>;
 }