45 of 50 in All Controls
aws

Centralize AWS Config for Resource Monitoring

IDAWS-SEC-006
Severity
high
Automation
Auto
Category
security
Enforcementmandatory
Complexity / Impact
medium(low impact)
Risk Profile
high likelihood(low residual)
Cloud Scopeaws:root
Environments
all
Target Resources
AWS::Config::ConfigurationRecorderAWS::Config::DeliveryChannelAWS::Config::ConfigurationAggregator
Services
configorganizationss3snsiam
Tags
configuration-managementcomplianceconfigauditlanding-zone
Frameworks
NIST 800-53CIS AWSISO 27001PCI DSSSOC 2AWS FSBP
Depends On
Governance
Cloud Security (quarterly)
Created
2026-05-03
Last Updated
2026-11-20

Specification & Description

Enable AWS Config recording across all AWS Organizations accounts and operational regions, delivering configuration snapshots and history to a centralized S3 bucket and aggregating compliance data in the Security account.

Technical Specifications

AWS Config continuously records resource configurations and configuration changes over time, forming the inventory and compliance evaluation layer for landing zone detective controls.

1. Dual Delegated Administrator Principals

  • AWS Config requires registering both config.amazonaws.com (for organization configuration aggregators) and config-multiaccountsetup.amazonaws.com (for organization Config rules and conformance packs) as delegated administrators in the Security account.

2. Member Account Recorders and Cost Optimization

  • Registering a delegated administrator does not automatically start configuration recorders in member accounts. Deploy configuration recorders and delivery channels across all accounts and regions (via CloudFormation StackSets, Control Tower, or Terraform).
  • Set includeGlobalResourceTypes = true in only one designated home region per account to avoid duplicate recording charges for global IAM resources.

3. Centralized Organization Aggregator

  • Provision an organization aggregator (OrganizationAggregationSource with AllAwsRegions = true) in the Security delegated administrator account using an IAM role with AWSConfigRoleForOrganizations.

Security Rationale

Configuration drift and unapproved resource changes introduce persistent security exposure. Centralized AWS Config recording and aggregation provide the resource inventory and change timeline required for incident response, continuous compliance, and Security Hub standards evaluations.

Business & Security Impact

Without centralized AWS Config recording and aggregation, unauthorized infrastructure changes go undetected and multi-account security posture evaluations lack authoritative resource state.

Operational & Implementation Notes

This control remains in draft status while multi-region recorder rollout patterns (Control Tower vs custom CloudFormation StackSets) are finalized. Note that AWS Config DescribeConfigurationRecorders and DescribeDeliveryChannels return camelCase keys (name, recordingGroup) whereas DescribeConfigurationAggregators returns PascalCase keys (ConfigurationAggregatorName, OrganizationAggregationSource).

Compliance Framework Mappings (6)

Regulatory baselines and industry standards mapped to this control specification.

Beta
Framework / StandardMapped Requirements & ControlsControls
NIST 800-53 Rev 5NIST 800-53
CM-2CM-3CM-6CM-8
4
CIS AWS Foundations Benchmark v3.0CIS AWS
3.3
1
ISO 27001:2022ISO 27001
A.8.9
1
PCI DSS v4.0PCI DSS
2.2.111.5.2
2
SOC 2SOC 2
CC7.1CC8.1
2
AWS Foundational Security Best PracticesAWS FSBP
Config.1
1

* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.

Automated Detection & Rule Logic

Detection Engine: aws-api • Automated: Yes

Verify delegated administrator registrations for both config.amazonaws.com and config-multiaccountsetup.amazonaws.com, confirm an organization aggregator with AllAwsRegions = true exists in the Security account, and verify active configuration recorders and delivery channels across accounts and regions.

AWS CLI: Verify Config Delegated Admins, Aggregator, Recorders, and Delivery Channelsbash
# 1. Verify both AWS Config delegated administrator principals
aws organizations list-delegated-administrators \
  --service-principal config.amazonaws.com \
  --query "DelegatedAdministrators[*].{Id:Id,Name:Name,Status:Status}" \
  --output json

aws organizations list-delegated-administrators \
  --service-principal config-multiaccountsetup.amazonaws.com \
  --query "DelegatedAdministrators[*].{Id:Id,Name:Name,Status:Status}" \
  --output json

# 2. Security account: verify organization configuration aggregator
aws configservice describe-configuration-aggregators \
  --region "$HOME_REGION" \
  --query "ConfigurationAggregators[*].{Name:ConfigurationAggregatorName,AllRegions:OrganizationAggregationSource.AllAwsRegions,RoleArn:OrganizationAggregationSource.RoleArn}" \
  --output json

# 3. Verify local configuration recorder, status, and delivery channel
aws configservice describe-configuration-recorders \
  --region "$HOME_REGION" \
  --query "ConfigurationRecorders[*].{Name:name,AllSupported:recordingGroup.allSupported,IncludeGlobal:recordingGroup.includeGlobalResourceTypes}" \
  --output json

aws configservice describe-configuration-recorder-status \
  --region "$HOME_REGION" \
  --query "ConfigurationRecordersStatus[*].{Name:name,Recording:recording,LastStatus:lastStatus}" \
  --output json

aws configservice describe-delivery-channels \
  --region "$HOME_REGION" \
  --query "DeliveryChannels[*].{Name:name,S3Bucket:s3BucketName,SnsTopic:snsTopicARN}" \
  --output json

Preventative Enforcement Policies

SCP: Prevent AWS Config Disablement and Aggregator Deletionjson
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "ProtectAWSConfigCentralization",
      "Effect": "Deny",
      "Action": [
        "config:DeleteConfigurationRecorder",
        "config:StopConfigurationRecorder",
        "config:DeleteDeliveryChannel",
        "config:DeleteConfigurationAggregator"
      ],
      "Resource": "*",
      "Condition": {
        "ArnNotLike": {
          "aws:PrincipalArn": [
            "arn:aws:iam::*:role/LandingZoneAdminRole"
          ]
        }
      }
    }
  ]
}

Remediation Guide & Automation

Register the Security account as delegated administrator for both `config.amazonaws.com` and `config-multiaccountsetup.amazonaws.com`, deploy an organization-wide configuration aggregator in the Security account, and enable configuration recorders and delivery channels across all member accounts and regions targeting the central Log Archive S3 bucket.

Step-by-Step Instructions

  1. From the Organizations Management account, enable trusted access and register the Security account as delegated administrator for both config.amazonaws.com and config-multiaccountsetup.amazonaws.com.
  2. In the Security delegated administrator account, create an IAM role trusting config.amazonaws.com with AWSConfigRoleForOrganizations and create an organization configuration aggregator covering all AWS regions.
  3. Across all accounts and enabled regions, deploy an AWS Config recorder and delivery channel targeting the central Log Archive S3 bucket (and optional SNS topic).
  4. Enable includeGlobalResourceTypes in only the primary home region per account to avoid duplicate IAM global resource recording charges.
  5. Attach the protective SCP to the Organization Root preventing member accounts from stopping or deleting Config recorders, delivery channels, or aggregators.
AWS CLI: Register Config Delegated Admins, Aggregator, and Recorderbash
# 1. Management account: enable service access and register both Config delegated admin principals
aws organizations enable-aws-service-access \
  --service-principal config.amazonaws.com

aws organizations enable-aws-service-access \
  --service-principal config-multiaccountsetup.amazonaws.com

aws organizations register-delegated-administrator \
  --account-id "$SECURITY_ACCOUNT_ID" \
  --service-principal config.amazonaws.com

aws organizations register-delegated-administrator \
  --account-id "$SECURITY_ACCOUNT_ID" \
  --service-principal config-multiaccountsetup.amazonaws.com

# 2. Security (Delegated Admin) account: create organization aggregator
aws configservice put-configuration-aggregator \
  --configuration-aggregator-name organization-aggregator \
  --organization-aggregation-source "RoleArn=$CONFIG_ORG_ROLE_ARN,AllAwsRegions=true" \
  --region "$HOME_REGION"

# 3. Member account baseline (run per account/region; set includeGlobalResourceTypes=false in non-home regions)
aws configservice put-configuration-recorder \
  --configuration-recorder "name=default,roleARN=$CONFIG_RECORDER_ROLE_ARN" \
  --recording-group "allSupported=true,includeGlobalResourceTypes=true" \
  --region "$HOME_REGION"

aws configservice put-delivery-channel \
  --delivery-channel "name=default,s3BucketName=$LOG_ARCHIVE_BUCKET,snsTopicARN=$CONFIG_SNS_TOPIC_ARN" \
  --region "$HOME_REGION"

aws configservice start-configuration-recorder \
  --configuration-recorder-name default \
  --region "$HOME_REGION"
Terraform: Configure Config Delegated Admins, Aggregator, and Recorderhcl
variable "security_account_id" {
  type        = string
  description = "12-digit AWS account ID of the central Security Tooling account."
}

variable "home_region" {
  type        = string
  description = "Primary AWS Config aggregation and global resource recording region."
}

variable "config_org_role_arn" {
  type        = string
  description = "IAM role ARN trusting config.amazonaws.com with AWSConfigRoleForOrganizations."
}

variable "config_recorder_role_arn" {
  type        = string
  description = "IAM role ARN used by the local AWS Config configuration recorder."
}

variable "log_archive_bucket_name" {
  type        = string
  description = "Central S3 bucket name in Log Archive for AWS Config snapshots and history."
}

variable "config_sns_topic_arn" {
  type        = string
  description = "SNS topic ARN for AWS Config configuration change notifications."
}

provider "aws" {
  alias  = "security"
  region = var.home_region

  assume_role {
    role_arn = "arn:aws:iam::${var.security_account_id}:role/LandingZoneAdminRole"
  }
}

# Management account: register both delegated administrator principals
resource "aws_organizations_delegated_administrator" "config" {
  account_id        = var.security_account_id
  service_principal = "config.amazonaws.com"
}

resource "aws_organizations_delegated_administrator" "config_multiaccount" {
  account_id        = var.security_account_id
  service_principal = "config-multiaccountsetup.amazonaws.com"
}

# Security account: organization-wide configuration aggregator
resource "aws_config_configuration_aggregator" "org" {
  provider = aws.security
  name     = "organization-aggregator"

  organization_aggregation_source {
    all_regions = true
    role_arn    = var.config_org_role_arn
  }

  depends_on = [aws_organizations_delegated_administrator.config]
}

# Account/region baseline recorder and delivery channel (member-account rollout
# across accounts and regions uses CloudFormation StackSets or a per-account
# provider module rather than executing solely against the default Management provider)
resource "aws_config_configuration_recorder" "main" {
  name     = "default"
  role_arn = var.config_recorder_role_arn

  recording_group {
    all_supported                 = true
    include_global_resource_types = true
  }
}

resource "aws_config_delivery_channel" "main" {
  name           = "default"
  s3_bucket_name = var.log_archive_bucket_name
  sns_topic_arn  = var.config_sns_topic_arn

  depends_on = [aws_config_configuration_recorder.main]
}

resource "aws_config_configuration_recorder_status" "main" {
  name       = aws_config_configuration_recorder.main.name
  is_enabled = true

  depends_on = [aws_config_delivery_channel.main]
}

We value your privacy

We use analytics cookies to understand how visitors interact with our site and to improve the user experience. You can choose to accept or decline these cookies.