Na}{

File Content: `put-config-rule.rst`

**To add an AWS managed Config rule**

The following command provides JSON code to add an AWS managed Config rule::

    aws configservice put-config-rule --config-rule file://RequiredTagsForEC2Instances.json

``RequiredTagsForEC2Instances.json`` is a JSON file that contains the rule configuration::

    {
      "ConfigRuleName": "RequiredTagsForEC2Instances",
      "Description": "Checks whether the CostCenter and Owner tags are applied to EC2 instances.",
      "Scope": {
        "ComplianceResourceTypes": [
          "AWS::EC2::Instance"
        ]
      },
      "Source": {
        "Owner": "AWS",
        "SourceIdentifier": "REQUIRED_TAGS"
      },
      "InputParameters": "{\"tag1Key\":\"CostCenter\",\"tag2Key\":\"Owner\"}"
    }

For the ``ComplianceResourceTypes`` attribute, this JSON code limits the scope to resources of the ``AWS::EC2::Instance`` type, so AWS Config will evaluate only EC2 instances against the rule. Because the rule is a managed rule, the ``Owner`` attribute is set to ``AWS``, and the ``SourceIdentifier`` attribute is set to the rule identifier, ``REQUIRED_TAGS``. For the ``InputParameters`` attribute, the tag keys that the rule requires, ``CostCenter`` and ``Owner``, are specified.

If the command succeeds, AWS Config returns no output. To verify the rule configuration, run the `describe-config-rules`__ command, and specify the rule name.

.. __: http://docs.aws.amazon.com/cli/latest/reference/configservice/describe-config-rules.html

**To add a customer managed Config rule**

The following command provides JSON code to add a customer managed Config rule::

    aws configservice put-config-rule --config-rule file://InstanceTypesAreT2micro.json

``InstanceTypesAreT2micro.json`` is a JSON file that contains the rule configuration::

    {
      "ConfigRuleName": "InstanceTypesAreT2micro",
      "Description": "Evaluates whether EC2 instances are the t2.micro type.",
      "Scope": {
        "ComplianceResourceTypes": [
          "AWS::EC2::Instance"
        ]
      },
      "Source": {
        "Owner": "CUSTOM_LAMBDA",
        "SourceIdentifier": "arn:aws:lambda:us-east-1:123456789012:function:InstanceTypeCheck",
        "SourceDetails": [
          {
            "EventSource": "aws.config",
            "MessageType": "ConfigurationItemChangeNotification"
          }
        ]
      },
      "InputParameters": "{\"desiredInstanceType\":\"t2.micro\"}"
    }

For the ``ComplianceResourceTypes`` attribute, this JSON code limits the scope to resources of the ``AWS::EC2::Instance`` type, so AWS Config will evaluate only EC2 instances against the rule. Because this rule is a customer managed rule, the ``Owner`` attribute is set to ``CUSTOM_LAMBDA``, and the ``SourceIdentifier`` attribute is set to the ARN of the AWS Lambda function. The ``SourceDetails`` object is required. The parameters that are specified for the ``InputParameters`` attribute are passed to the AWS Lambda function when AWS Config invokes it to evaluate resources against the rule.

If the command succeeds, AWS Config returns no output. To verify the rule configuration, run the `describe-config-rules`__ command, and specify the rule name.

.. __: http://docs.aws.amazon.com/cli/latest/reference/configservice/describe-config-rules.html

Name	Size	Permission
delete-config-rule.rst	185 bytes	0644
delete-delivery-channel.rst	177 bytes	0644
delete-evaluation-results.rst	260 bytes	0755
deliver-config-snapshot.rst	352 bytes	0644
describe-compliance-by-config-rule.rst	1342 bytes	0644
describe-compliance-by-resource.rst	1413 bytes	0644
describe-config-rule-evaluation-status.rst	695 bytes	0644
describe-config-rules.rst	1392 bytes	0644
describe-configuration-recorder-status.rst	589 bytes	0644
describe-configuration-recorders.rst	625 bytes	0644
describe-delivery-channel-status.rst	953 bytes	0644
describe-delivery-channels.rst	448 bytes	0644
get-compliance-details-by-config-rule.rst	2169 bytes	0644
get-compliance-details-by-resource.rst	1574 bytes	0644
get-compliance-summary-by-config-rule.rst	744 bytes	0644
get-compliance-summary-by-resource-type.rst	1967 bytes	0644
get-resource-config-history.rst	282 bytes	0644
get-status.rst	454 bytes	0644
list-discovered-resources.rst	682 bytes	0644
put-config-rule.rst	3343 bytes	0644
put-configuration-recorder.rst	1753 bytes	0644
put-delivery-channel.rst	2370 bytes	0644
start-config-rules-evaluation.rst	252 bytes	0755
start-configuration-recorder.rst	433 bytes	0644
stop-configuration-recorder.rst	434 bytes	0644
subscribe.rst	1208 bytes	0644

File Content: put-config-rule.rst

File Content: `put-config-rule.rst`