ConfigRuleId, or ConfigRuleArn in the
* ConfigRule data type that you use in this
* request.
- * The maximum number of rules that Config supports is 150.
- * - *For information about requesting a rule limit increase, see - * Config Limits in the Amazon Web Services General - * Reference Guide.
+ *For information on how many Config rules you can have per account, + * see + * Service Limits + * in the Config Developer Guide.
* *For more information about developing and using Config * rules, see Evaluating Amazon Web Services resource Configurations with Config @@ -3162,7 +3161,11 @@ export class ConfigService extends ConfigServiceClient { } /** - *
Creates or updates a conformance pack. A conformance pack is a collection of Config rules that can be easily deployed in an account and a region and across Amazon Web Services Organization.
+ *Creates or updates a conformance pack. A conformance pack is a collection of Config rules that can be easily deployed in an account and a region and across Amazon Web Services Organization. + * For information on how many conformance packs you can have per account, + * see + * Service Limits + * in the Config Developer Guide.
*This API creates a service linked role AWSServiceRoleForConfigConforms in your account.
* The service linked role is created only when the role does not exist in your account.
Adds or updates organization Config rule for your entire organization evaluating whether your Amazon Web Services resources comply with your - * desired configurations.
+ * desired configurations. For information on how many organization Config rules you can have per account, + * see + * Service Limits + * in the Config Developer Guide. * 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
- * ListDelegatedAdministrator permissions are added.
ListDelegatedAdministrator permissions are added. An organization can have up to 3 delegated administrators.
* This API enables organization service access through the EnableAWSServiceAccess action and creates a service linked
* role AWSServiceRoleForConfigMultiAccountSetup 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.
@@ -3332,7 +3338,6 @@ export class ConfigService extends ConfigServiceClient {
* When you use the PutOrganizationConfigRule 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 RuleIdentifier key.
The maximum number of organization Config rules that Config supports is 150 and 3 delegated administrator per organization.
*Prerequisite: Ensure you call EnableAllFeatures API to enable all features in an organization.
Specify either OrganizationCustomRuleMetadata or OrganizationManagedRuleMetadata.
ConfigRuleId, or ConfigRuleArn in the
* ConfigRule data type that you use in this
* request.
- * The maximum number of rules that Config supports is 150.
- * - *For information about requesting a rule limit increase, see - * Config Limits in the Amazon Web Services General - * Reference Guide.
+ *For information on how many Config rules you can have per account, + * see + * Service Limits + * in the Config Developer Guide.
* *For more information about developing and using Config * rules, see Evaluating Amazon Web Services resource Configurations with Config diff --git a/clients/client-config-service/src/commands/PutConformancePackCommand.ts b/clients/client-config-service/src/commands/PutConformancePackCommand.ts index 67e9363ed58b..b4cd8863cacd 100644 --- a/clients/client-config-service/src/commands/PutConformancePackCommand.ts +++ b/clients/client-config-service/src/commands/PutConformancePackCommand.ts @@ -23,7 +23,11 @@ export interface PutConformancePackCommandInput extends PutConformancePackReques export interface PutConformancePackCommandOutput extends PutConformancePackResponse, __MetadataBearer {} /** - *
Creates or updates a conformance pack. A conformance pack is a collection of Config rules that can be easily deployed in an account and a region and across Amazon Web Services Organization.
+ *Creates or updates a conformance pack. A conformance pack is a collection of Config rules that can be easily deployed in an account and a region and across Amazon Web Services Organization. + * For information on how many conformance packs you can have per account, + * see + * Service Limits + * in the Config Developer Guide.
*This API creates a service linked role AWSServiceRoleForConfigConforms in your account.
* The service linked role is created only when the role does not exist in your account.
Adds or updates organization Config rule for your entire organization evaluating whether your Amazon Web Services resources comply with your - * desired configurations.
+ * desired configurations. For information on how many organization Config rules you can have per account, + * see + * Service Limits + * in the Config Developer Guide. * 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
- * ListDelegatedAdministrator permissions are added.
ListDelegatedAdministrator permissions are added. An organization can have up to 3 delegated administrators.
* This API enables organization service access through the EnableAWSServiceAccess action and creates a service linked
* role AWSServiceRoleForConfigMultiAccountSetup 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.
@@ -40,7 +43,6 @@ export interface PutOrganizationConfigRuleCommandOutput extends PutOrganizationC
* When you use the PutOrganizationConfigRule 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 RuleIdentifier key.
The maximum number of organization Config rules that Config supports is 150 and 3 delegated administrator per organization.
*Prerequisite: Ensure you call EnableAllFeatures API to enable all features in an organization.
Specify either OrganizationCustomRuleMetadata or OrganizationManagedRuleMetadata.
Adds or updates an Config rule for evaluating whether your\n\t\t\tAmazon Web Services resources comply with your desired configurations.
\n\t\tYou can use this action for Config custom rules and Config\n\t\t\tmanaged rules. A Config custom rule is a rule that you\n\t\t\tdevelop and maintain. An Config managed rule is a customizable,\n\t\t\tpredefined rule that Config provides.
\n\t\tIf you are adding a new Config custom rule, you must first\n\t\t\tcreate the Lambda function that the rule invokes to evaluate\n\t\t\tyour resources. When you use the PutConfigRule action\n\t\t\tto add the rule to Config, you must specify the Amazon Resource\n\t\t\tName (ARN) that Lambda assigns to the function. Specify the ARN\n\t\t\tfor the SourceIdentifier key. This key is part of the\n\t\t\t\tSource object, which is part of the\n\t\t\t\tConfigRule object.
If you are adding an Config managed rule, specify the\n\t\t\trule's identifier for the SourceIdentifier key. To\n\t\t\treference Config managed rule identifiers, see About Config managed rules.
For any new rule that you add, specify the\n\t\t\t\tConfigRuleName in the ConfigRule\n\t\t\tobject. Do not specify the ConfigRuleArn or the\n\t\t\tConfigRuleId. These values are generated by Config for new rules.
If you are updating a rule that you added previously, you can\n\t\t\tspecify the rule by ConfigRuleName,\n\t\t\t\tConfigRuleId, or ConfigRuleArn in the\n\t\t\t\tConfigRule data type that you use in this\n\t\t\trequest.
The maximum number of rules that Config supports is 150.
\n\n\t\tFor information about requesting a rule limit increase, see\n\t\t\t\tConfig Limits in the Amazon Web Services General\n\t\t\t\tReference Guide.
\n\n\t\tFor more information about developing and using Config\n\t\t\trules, see Evaluating Amazon Web Services resource Configurations with Config\n\t\t\tin the Config Developer Guide.
" + "smithy.api#documentation": "Adds or updates an Config rule for evaluating whether your\n\t\t\tAmazon Web Services resources comply with your desired configurations.
\n\t\tYou can use this action for Config custom rules and Config\n\t\t\tmanaged rules. A Config custom rule is a rule that you\n\t\t\tdevelop and maintain. An Config managed rule is a customizable,\n\t\t\tpredefined rule that Config provides.
\n\t\tIf you are adding a new Config custom rule, you must first\n\t\t\tcreate the Lambda function that the rule invokes to evaluate\n\t\t\tyour resources. When you use the PutConfigRule action\n\t\t\tto add the rule to Config, you must specify the Amazon Resource\n\t\t\tName (ARN) that Lambda assigns to the function. Specify the ARN\n\t\t\tfor the SourceIdentifier key. This key is part of the\n\t\t\t\tSource object, which is part of the\n\t\t\t\tConfigRule object.
If you are adding an Config managed rule, specify the\n\t\t\trule's identifier for the SourceIdentifier key. To\n\t\t\treference Config managed rule identifiers, see About Config managed rules.
For any new rule that you add, specify the\n\t\t\t\tConfigRuleName in the ConfigRule\n\t\t\tobject. Do not specify the ConfigRuleArn or the\n\t\t\tConfigRuleId. These values are generated by Config for new rules.
If you are updating a rule that you added previously, you can\n\t\t\tspecify the rule by ConfigRuleName,\n\t\t\t\tConfigRuleId, or ConfigRuleArn in the\n\t\t\t\tConfigRule data type that you use in this\n\t\t\trequest.
For information on how many Config rules you can have per account, \n\t\t\tsee \n Service Limits\n in the Config Developer Guide.
\n\n\t\tFor more information about developing and using Config\n\t\t\trules, see Evaluating Amazon Web Services resource Configurations with Config\n\t\t\tin the Config Developer Guide.
" } }, "com.amazonaws.configservice#PutConfigRuleRequest": { @@ -8783,7 +8783,7 @@ } ], "traits": { - "smithy.api#documentation": "Creates or updates a conformance pack. A conformance pack is a collection of Config rules that can be easily deployed in an account and a region and across Amazon Web Services Organization.
\n\t\tThis API creates a service linked role AWSServiceRoleForConfigConforms in your account. \n\t\tThe service linked role is created only when the role does not exist in your account.
You must specify either the TemplateS3Uri or the TemplateBody parameter, but not both. \n\t\t\tIf you provide both Config uses the TemplateS3Uri parameter and ignores the TemplateBody parameter.
Creates or updates a conformance pack. A conformance pack is a collection of Config rules that can be easily deployed in an account and a region and across Amazon Web Services Organization.\n\t\t\tFor information on how many conformance packs you can have per account, \n\t\t\tsee \n Service Limits\n in the Config Developer Guide.
\n\t\tThis API creates a service linked role AWSServiceRoleForConfigConforms in your account. \n\t\tThe service linked role is created only when the role does not exist in your account.
You must specify either the TemplateS3Uri or the TemplateBody parameter, but not both. \n\t\t\tIf you provide both Config uses the TemplateS3Uri parameter and ignores the TemplateBody parameter.
Adds or updates organization Config rule for your entire organization evaluating whether your Amazon Web Services resources comply with your \n\t\t\tdesired configurations.
\n\t Only a master account and a delegated administrator can create or update an organization Config rule.\n\t\tWhen calling this API with a delegated administrator, you must ensure Organizations \n\t\tListDelegatedAdministrator permissions are added.
This API enables organization service access through the EnableAWSServiceAccess action and creates a service linked \n\t\t\trole AWSServiceRoleForConfigMultiAccountSetup in the master or delegated administrator account of your organization. \n\t\t\tThe service linked role is created only when the role does not exist in the caller account. \n\t\t\tConfig verifies the existence of role with GetRole action.
To use this API with delegated administrator, register a delegated administrator by calling Amazon Web Services Organization\n\t\t\tregister-delegated-administrator for config-multiaccountsetup.amazonaws.com.
You can use this action to create both Config custom rules and Config managed rules. \n\t\t\tIf you are adding a new Config custom rule, you must first create Lambda function in the master account or a delegated \n\t\t\tadministrator 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.\n\t\t\tWhen you use the PutOrganizationConfigRule action to add the rule to Config, you must \n\t\t\tspecify the Amazon Resource Name (ARN) that Lambda assigns to the function. \n\t\t\tIf you are adding an Config managed rule, specify the rule's identifier for the RuleIdentifier key.
The maximum number of organization Config rules that Config supports is 150 and 3 delegated administrator per organization.
\n\t\tPrerequisite: Ensure you call EnableAllFeatures API to enable all features in an organization.
Specify either OrganizationCustomRuleMetadata or OrganizationManagedRuleMetadata.
Adds or updates organization Config rule for your entire organization evaluating whether your Amazon Web Services resources comply with your \n\t\t\tdesired configurations. For information on how many organization Config rules you can have per account, \n\t\t\tsee \n Service Limits\n in the Config Developer Guide.
\n\t Only a master account and a delegated administrator can create or update an organization Config rule.\n\t\tWhen calling this API with a delegated administrator, you must ensure Organizations \n\t\tListDelegatedAdministrator permissions are added. An organization can have up to 3 delegated administrators.
This API enables organization service access through the EnableAWSServiceAccess action and creates a service linked \n\t\t\trole AWSServiceRoleForConfigMultiAccountSetup in the master or delegated administrator account of your organization. \n\t\t\tThe service linked role is created only when the role does not exist in the caller account. \n\t\t\tConfig verifies the existence of role with GetRole action.
To use this API with delegated administrator, register a delegated administrator by calling Amazon Web Services Organization\n\t\t\tregister-delegated-administrator for config-multiaccountsetup.amazonaws.com.
You can use this action to create both Config custom rules and Config managed rules. \n\t\t\tIf you are adding a new Config custom rule, you must first create Lambda function in the master account or a delegated \n\t\t\tadministrator 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.\n\t\t\tWhen you use the PutOrganizationConfigRule action to add the rule to Config, you must \n\t\t\tspecify the Amazon Resource Name (ARN) that Lambda assigns to the function. \n\t\t\tIf you are adding an Config managed rule, specify the rule's identifier for the RuleIdentifier key.
Prerequisite: Ensure you call EnableAllFeatures API to enable all features in an organization.
Specify either OrganizationCustomRuleMetadata or OrganizationManagedRuleMetadata.