You can use this action for customer managed Config rules and AWS managed Config rules. A customer managed Config rule is a custom rule that you develop and maintain. An AWS managed Config rule is a customizable, predefined rule that is provided by AWS Config.
If you are adding a new customer managed Config rule, you must first create the AWS
Lambda function that the rule invokes to evaluate your resources. When you use the
PutConfigRule action to add the rule to AWS Config, you must specify
the Amazon Resource Name (ARN) that AWS Lambda assigns to the function. Specify the
ARN for the
SourceIdentifier key. This key is part of the
object, which is part of the
If you are adding a new AWS managed Config rule, specify the rule's identifier for
SourceIdentifier key. To reference AWS managed Config rule identifiers,
AWS Managed Config Rules.
For any new rule that you add, specify the
ConfigRuleName in the
object. Do not specify the
ConfigRuleArn or the
These values are generated by AWS Config for new rules.
If you are updating a rule that you have added previously, specify the rule's
ConfigRuleArn in the
data type that you use in this request.
The maximum number of rules that AWS Config supports is 25.
For more information about developing and using AWS Config rules, see Evaluating AWS Resource Configurations with AWS Config in the AWS Config Developer Guide.
Version: (assembly version)
public abstract PutConfigRuleResponse PutConfigRule( PutConfigRuleRequest request )
Container for the necessary parameters to execute the PutConfigRule service method.
|InsufficientPermissionsException||Indicates one of the following errors: The rule cannot be created because the IAM role assigned to AWS Config lacks permissions to perform the config:Put* action.The AWS Lambda function cannot be invoked. Check the function ARN, and check the function's permissions.|
|InvalidParameterValueException||One or more of the specified parameters are invalid. Verify that your parameters are valid and try again.|
|MaxNumberOfConfigRulesExceededException||Failed to add the AWS Config rule because the account already contains the maximum number of 25 rules. Consider deleting any deactivated rules before adding new rules.|
|ResourceInUseException||The rule is currently being deleted. Wait for a while and try again.|
Supported in: 4.5, 4.0, 3.5