Skip to content
Cloud Governance Tools

Deny enabling and disabling AWS Config

Deny enabling and disabling AWS Config is an AWS guardrail written in service control policies. Denies stopping or deleting AWS Config recorders, delivery channels, rules and aggregators, and putting new configuration, unless the caller is the privileged role. Copied from a licensed open source set and read on 10 Nov 2026.

More logging and monitoring guardrails ยท About Service control policies

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Deny",
      "Action": [
        "config:DeleteConfigurationAggregator",
        "config:DeleteConfigurationRecorder",
        "config:DeleteDeliveryChannel",
        "config:PutConfigRule",
        "config:DeleteConfigRule",
        "config:DeleteOrganizationConfigRule",
        "config:DeleteRetentionConfiguration",
        "config:PutConfigurationAggregator",
        "config:PutConfigurationRecorder",
        "config:PutDeliveryChannel",
        "config:PutRetentionConfiguration",
        "config:StopConfigurationRecorder",
        "config:DeliverConfigSnapshot",
        "config:DeleteAggregationAuthorization",
        "config:DeleteEvaluationResults",
        "config:PutOrganizationConfigRule",
        "config:PutRemediationConfigurations",
        "config:DeleteRemediationConfiguration",
        "config:DeleteServiceLinkedConfigurationRecorder",
        "config:DeleteRemediationExceptions",
        "config:DeletePendingAggregationRequest"
      ],
      "Resource": "*",
      "Condition": {
        "ArnNotLike": {
          "aws:PrincipalARN": "arn:aws:iam::${Account}:role/[PRIVILEGED_ROLE]"
        }
      }
    }
  ]
}
Blocks
Denies stopping or deleting AWS Config recorders, delivery channels, rules and aggregators, and putting new configuration, unless the caller is the privileged role.
Breaks
Teams cannot add or change their own Config rules or recorders outside the privileged role; the README notes AWS Control Tower already applies a similar default control. (source)
Test before applying
As for every Service control policies guardrail: how to test before enforcing
Mechanism
Service control policies (SCPs): IAM users, IAM roles and the root user in member accounts; not the management account and not service-linked roles.
Taken from
open source set, MIT-0 (README states MIT-0; LICENSE file fetched, MIT-0 text, Copyright Amazon.com, Inc.): https://raw.githubusercontent.com/aws-samples/service-control-policy-examples/main/LICENSE

What the policy text names

It names 21 actions or patterns: config:DeleteConfigurationAggregator, config:DeleteConfigurationRecorder, config:DeleteDeliveryChannel, config:PutConfigRule, config:DeleteConfigRule, config:DeleteOrganizationConfigRule, config:DeleteRetentionConfiguration, config:PutConfigurationAggregator, and more. Its conditions test aws:PrincipalARN.

What the source says

config:StopConfigurationRecorder (read 10 Nov 2026).

On what it breaks: "Restrict enabling/disabling AWS Config to a privileged role."

Sources

  1. Deny enabling and disabling AWS Config, read 10 Nov 2026
  2. What it breaks, read 10 Nov 2026
  3. How to test it first, read 10 Nov 2026

Last reviewed 16 Nov 2026.