Study guide

13.1 AWS Config Managed Rules & Automated Remediation with SSM

AWS Certified DevOps Engineer – Professional Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CI/CD Pipeline Architecture & Source Integration

1.1 Multi-Stage & Multi-Account CodePipeline Design 1.2 CodeBuild Projects, Build Environments & Pipeline Secrets 1.3 Source Control Workflows, Webhooks & Branching Models

2 Chapter 2: Automated Testing, Test Gates & Quality Verification

2.1 Automated Unit, Integration & Acceptance Testing in Pipelines 2.2 Load Testing, Performance Benchmarking & Synthetic Canaries 2.3 Security Scanning, SAST/DAST & Approval Gates

3 Chapter 3: Artifact Management & Multi-Platform Deployment Strategies

3.1 Artifact Lifecycle Management with CodeArtifact, ECR & S3 3.2 Automated Image Baking with EC2 Image Builder 3.3 In-Place, Rolling & Immutable Deployments on EC2 3.4 Blue/Green & Canary Deployments for ECS, EKS & Lambda

4 Chapter 4: CloudFormation, CDK & Reusable IaC Components

4.1 Advanced CloudFormation: Nested Stacks, Change Sets & Custom Resources 4.2 Cross-Account & Multi-Region StackSets & Drift Detection 4.3 Modern IaC: AWS CDK, SAM & Service Catalog Governance

5 Chapter 5: Multi-Account Architecture, Organizations & Control Tower

5.1 AWS Organizations Hierarchy, OUs & Account Provisioning 5.2 Service Control Policies (SCPs) & Multi-Account Guardrails 5.3 AWS Control Tower, Account Factory & Landing Zone Automation

6 Chapter 6: Systems Manager & Large-Scale Fleet Configuration

6.1 SSM Agent, Hybrid Activation & Session Manager 6.2 Systems Manager Run Command, State Manager & Associations 6.3 Patch Manager, Parameter Store vs Secrets Manager & AppConfig

7 Chapter 7: High Availability & Multi-Region Resiliency

7.1 Designing Resilient Multi-AZ & Multi-Region Architectures 7.2 Route 53 Traffic Flow, Health Checks & DNS Failover 7.3 Data Replication: Aurora Global DB, DynamoDB Global Tables & S3 CRR

8 Chapter 8: Scalability, Auto Scaling & Disaster Recovery Automation

8.1 EC2 Auto Scaling Policies, Lifecycle Hooks & Warm Pools 8.2 Container & Serverless Scalability: ECS Capacity Providers, EKS & API Gateway 8.3 Disaster Recovery Strategies: RTO, RPO & Architecture Tiers 8.4 Automated Backup & Recovery with AWS Backup & Elastic Disaster Recovery

9 Chapter 9: CloudWatch Metrics, Agent Collection & Log Aggregation

9.1 CloudWatch Metrics, Dimensions, Metric Math & High Resolution 9.2 Unified CloudWatch Agent & Custom Metric Collection 9.3 Centralized Log Aggregation, Retention & Cross-Account Subscriptions

10 Chapter 10: Log Analysis, Dashboards & Distributed Tracing with X-Ray

10.1 CloudWatch Logs Insights, Filter Syntax & Query Optimization 10.2 CloudWatch Dashboards, Composite Alarms & Anomaly Detection 10.3 Distributed Tracing with AWS X-Ray & Service Maps

11 Chapter 11: Automated Observability & Event-Driven Monitoring

11.1 Application & Infrastructure Health Checks with Route 53 & ALB 11.2 Centralized Observability with Amazon OpenSearch & Athena 11.3 Synthetic Monitoring with CloudWatch Synthetics Canaries

12 Chapter 12: Event-Driven Incident Detection & Notification Pipelines

12.1 AWS Health, CloudTrail Events & Operational Notification 12.2 EventBridge Event Routing, Patterns & Multi-Account Buses 12.3 Asynchronous Event Processing: SNS, SQS Queues & Dead-Letter Handling

13 Chapter 13: Automated Remediation & Deployment Troubleshooting

13.1 AWS Config Managed Rules & Automated Remediation with SSM 13.2 Event-Driven Infrastructure Self-Healing with Lambda & Step Functions 13.3 Troubleshooting CI/CD Pipeline & Deployment Failures 13.4 Root Cause Analysis for Auto Scaling & Container Failures

14 Chapter 14: Identity, Access Management & Secrets at Scale

14.1 IAM Policy Evaluation Logic, NotAction & Explicit Denies 14.2 IAM Permissions Boundaries & Delegated Administration 14.3 IAM Identity Center, Cross-Account Roles & STS Session Policies 14.4 Automated Secrets Management & Secret Rotation with Secrets Manager

15 Chapter 15: Security Automation, Data Protection & Compliance Auditing

15.1 Network Security Automation: Security Groups, NACLs, Network Firewall & WAF 15.2 Cryptographic Controls & Key Management with AWS KMS & ACM 15.3 Automated Threat Detection: GuardDuty, Inspector & Security Hub 15.4 Continuous Compliance Auditing & Log Integrity with CloudTrail & Config

13.1 AWS Config Managed Rules & Automated Remediation with SSM

Key Takeaways Explain This Topic AI

AWS Config rules evaluate resource compliance using either AWS Managed Rules (pre-built evaluation logic) or Custom Rules (AWS Lambda functions invoking PutEvaluations).

Config rule evaluation triggers operate either on Configuration Changes (near-real-time evaluation upon resource mutation) or Periodic schedules (fixed intervals such as 1, 3, 6, 12, or 24 hours).

AWS Config supports Detective evaluation (post-provisioning compliance tracking) and Proactive evaluation (pre-deployment validation via StartResourceEvaluation and CloudFormation Hooks).

Automated remediation couples Config rules with AWS Systems Manager (SSM) Automation documents, utilizing dedicated remediation execution roles, retry parameters (MaximumAutomaticAttempts, RetryAttemptSeconds), and target parameter mapping.

AWS Config Conformance Packs package rules and automated remediation configurations into unified YAML templates, enabling immutable organization-wide deployment from a delegated administrator account.

Last updated: September 2026

AWS Config Architecture: Configuration Items, Recorders & Rule Types

AWS Config is a fully managed service that provides resource inventory, configuration history, and compliance monitoring across AWS environments. For the AWS Certified DevOps Engineer - Professional (DOP-C02) exam, candidates must master how AWS Config continuously evaluates resource state, detects configuration drift, and executes automated self-healing workflows via AWS Systems Manager (SSM) Automation.

Core Components of AWS Config

Configuration Item (CI) : A standardized JSON document representing the state of an AWS resource at a specific point in time. A CI encapsulates resource metadata, configuration attributes, relationship mappings to other resources, and CloudTrail event IDs associated with the state change.

Configuration Recorder : Captures changes for specified resource types in each AWS Region. It must be explicitly enabled and assigned an IAM service-linked role with permissions to read resource configurations.

Configuration Stream & History : Delivers real-time CI updates to an Amazon Kinesis Data Stream and writes scheduled configuration history snapshots (hourly/daily) to an Amazon S3 bucket, accompanied by Amazon SNS state-change notifications. Resource Mutation (API Call)

  • │
  • ▼
  • [ Configuration Recorder ] ──> Generates Configuration Item (CI)
  • │
  • ├──> Amazon S3 Bucket (Configuration History Snapshot)
  • ├──> Amazon SNS Topic (Configuration State Changes)
  • ▼
  • [ AWS Config Rules Engine ] ──> Evaluates Compliance (Compliant / Non-Compliant)
  • │
  • ▼ (If Non-Compliant & Auto-Remediation Configured)
  • [ AWS Systems Manager Automation Document ] ──> Self-Healing Action Executed
  • Managed Rules vs. Custom Lambda Rules

AWS Config provides two primary mechanisms for evaluating resource compliance:

Evaluation Dimension AWS Managed Rules Custom Lambda Rules

Implementation Logic Pre-built, maintained, and patched by AWS Authored by customers in AWS Lambda (Python, Node.js, Java, Go)

Rule Identifier Standardized rule identifier (e.g., S3_BUCKET_SERVER_SIDE_ENCRYPTION_ENABLED , RESTRICTED_SSH ) ARN of the backing AWS Lambda function ( arn:aws:lambda:... )

Maintenance Overhead Minimal; parameters configured via console or CloudFormation Requires testing, Lambda runtime upgrades, and execution role management

Evaluation Reporting Internal managed engine updates Config compliance store Lambda function must explicitly call the config:PutEvaluations API

Customization Configured via predefined input parameters Full programmatic flexibility; can evaluate complex, cross-service multi-resource logic

Guard DSL Support Not applicable Native support via CloudFormation Guard rules without writing imperative Lambda code

For custom Lambda rules, AWS Config invokes the function with an event payload containing the CI and an evaluation token. The Lambda function inspects the CI attributes and must invoke config:PutEvaluations before its own function timeout expires, supplying the ComplianceType ( COMPLIANT , NON_COMPLIANT , or NOT_APPLICABLE ), the EvaluationToken , and the resource identity ( OrderingTimestamp , ComplianceResourceId , ComplianceResourceType ).

Trigger Types: Configuration Changes vs. Periodic Schedules

Config rules are triggered according to two distinct evaluation models based on the nature of the check:

1. Configuration Change Triggered Rules

Change-triggered rules evaluate resources in near-real-time whenever an affected resource is created, updated, or deleted. When the Configuration Recorder detects an API mutation, it generates a CI and immediately passes it to the associated rule.

Best Suited For : Security boundaries and resource configuration properties that can be immediately evaluated from the CI payload (e.g., verifying if an S3 bucket has public access blocked, if an EBS volume is encrypted upon creation, or if a Security Group allows port 22 to 0.0.0.0/0 ).

Scope of Changes : Can be restricted to specific resource types (e.g., AWS::EC2::SecurityGroup ), specific resource IDs, or specific resource tags.

2. Periodic Triggered Rules

Periodic rules evaluate compliance at recurring time intervals regardless of whether a configuration mutation occurred.

Supported Frequencies : 1 hour, 3 hours, 6 hours, 12 hours, or 24 hours.

Best Suited For : Rules that evaluate dynamic, external, or time-decay attributes that do not emit CI change notifications. Classic examples include:

access-keys-rotated : Evaluates whether active IAM access keys have exceeded a maximum age (e.g., 90 days).

iam-user-unused-credentials-check : Identifies passwords or access keys inactive for more than 45 days.

ebs-snapshot-public-restorable-check : Queries external snapshot permissions.

Evaluation Modes: Detective vs. Proactive

A critical DOP-C02 concept is the distinction between Detective and Proactive evaluation modes: Developer / CI/CD Pipeline

  • │
  • ├──> [ Proactive Mode ] ──> StartResourceEvaluation API / CloudFormation Hooks
  • │ │ (Pre-deployment check: Passes or Fails Build)
  • │ ▼
  • └──> [ Resource Provisioned ] ──> Detective Mode (AWS Config Recorder captures CI)
  • │ (Post-deployment continuous audit)
  • ▼
  • Compliance Dashboard / Remediation
  • Detective Mode

Operates after resources are provisioned.

Continuously audits live infrastructure recorded by the Configuration Recorder.

When a violation is identified, the resource is flagged as NON_COMPLIANT in the AWS Config dashboard, an SNS event is emitted, and automated SSM remediation is triggered if configured.

Limitation : The non-compliant resource exists in the production environment for a transient period until remediation completes.

Proactive Mode

Operates before resources are provisioned into the live environment.

Evaluates CloudFormation template resource definitions or Terraform configurations prior to deployment using the config:StartResourceEvaluation API or AWS CloudFormation Guard Hooks.

If a template resource violates a proactive Config rule (e.g., an S3 bucket lacking encryption), the deployment pipeline blocks the deployment entirely, preventing security regressions from entering production.

Can evaluate both AWS Managed Rules and Custom Guard Rules that support proactive evaluation.

Loading diagram... AWS Config Rule Evaluation and Automated SSM Remediation Lifecycle

Automated Remediation with Systems Manager Automation Documents

AWS Config allows engineers to attach automated remediation actions to any managed or custom rule using AWS Systems Manager (SSM) Automation documents. When a resource is flagged as NON_COMPLIANT , Config automatically initiates the configured SSM Automation document without requiring manual operator intervention.

Remediation Configuration Specification ( AWS::Config::RemediationConfiguration )

A remediation configuration specifies how Config invokes SSM Automation: Type: AWS::Config::RemediationConfiguration

Properties:

  • ConfigRuleName: restricted-ssh
  • TargetType: SSM_DOCUMENT
  • TargetId: AWS-DisablePublicAccessForSecurityGroup
  • TargetVersion: '1'
  • Automatic: true
  • MaximumAutomaticAttempts: 5
  • RetryAttemptSeconds: 60

Parameters:

GroupId:

ResourceValue:

Value: RESOURCE_ID

AutomationAssumeRole:

StaticValue:

Values:

  • !GetAtt RemediationExecutionRole.Arn
  • Key Remediation Execution Parameters

Automatic : Boolean ( true or false ). When set to true , remediation executes immediately upon non-compliance detection. When set to false , an operator must manually trigger remediation via the console or CLI ( aws configservice start-remediation-execution ).

MaximumAutomaticAttempts : Specifies how many times AWS Config attempts automatic remediation before marking the remediation as failed. Valid range is 1 to 25 attempts .

RetryAttemptSeconds : The backoff time in seconds that AWS Config waits before retrying a failed remediation execution. Valid range is 1 to 2,678,400 seconds (31 days) .

Parameters : Mappings passed into the SSM Automation document:

ResourceValue ( RESOURCE_ID ) : Dynamically extracts the non-compliant resource identifier (e.g., GroupId , BucketName , InstanceId ) directly from the evaluation finding.

StaticValue : Hardcoded parameters, such as the AutomationAssumeRole ARN or default encryption keys.

Widely Tested AWS-Managed Remediation Documents

SSM Automation Document Target Config Rule Operational Self-Healing Action

AWS-DisablePublicAccessForSecurityGroup restricted-ssh , restricted-common-ports Scans ingress rules of the target security group and revokes any rule exposing sensitive ports (22, 3389) to 0.0.0.0/0 or ::/0 .

AWS-EnableS3BucketEncryption s3-bucket-server-side-encryption-enabled Enables default AES-256 (SSE-S3) or AWS KMS (SSE-KMS) server-side encryption on the non-compliant S3 bucket.

AWS-RevokeUnusedIAMUserCredentials iam-user-unused-credentials-check Deactivates inactive access keys or deletes login profiles for IAM users whose credentials have been unused for a specified threshold.

AWS-PublishSNSNotification Any non-compliant resource Publishes structured JSON alert containing resource details to an Amazon SNS topic for ticketing or ChatOps alerting.

AWS-ConfigureS3BucketPublicAccessBlock s3-bucket-public-read-prohibited Applies S3 Block Public Access settings ( BlockPublicAcls , IgnorePublicAcls , BlockPublicPolicy , RestrictPublicBuckets ) to true.

Remediation Execution Role: Trust Policy & Least Privilege

A frequent source of exam errors involves confusing the AWS Config service role with the Remediation Execution Role :

The AWS Config Service Role allows Config to describe resources, record CIs, and publish to S3/SNS. Its trust principal is config.amazonaws.com .

The Remediation Execution Role ( AutomationAssumeRole ) is assumed by AWS Systems Manager , NOT AWS Config directly. Therefore, its IAM trust policy MUST allow ssm.amazonaws.com : {

  • "Version": "2012-10-17",
  • "Statement": [
  • {
  • "Effect": "Allow",
  • "Principal": {
  • "Service": "ssm.amazonaws.com"
  • },
  • "Action": "sts:AssumeRole"
  • }
  • ]
  • }

The permissions policy attached to this role must grant least-privilege access for the specific actions performed by the SSM document (e.g., ec2:RevokeSecurityGroupIngress , s3:PutEncryptionConfiguration , iam:UpdateAccessKey ).

AWS Config Conformance Packs & Multi-Account Governance

A Conformance Pack is a collection of AWS Config rules and associated remediation actions packaged into a single, version-controlled YAML template. Conformance packs simplify compliance tracking against industry frameworks (e.g., CIS AWS Foundations Benchmark, NIST 800-53, PCI-DSS, HIPAA).

Multi-Account Deployment via AWS Organizations

In enterprise environments, managing Config rules account-by-account is unsustainable. Organization Conformance Packs solve this:

Delegated Administration : The organization management account delegates Config administration to a dedicated audit or security tooling account using AWS Organizations: aws organizations register-delegated-administrator \

  • -account-id 111122223333 \
  • -service-principal config-multiaccountsetup.amazonaws.com

Template Authoring : The DevOps team writes a conformance pack YAML template defining rules, parameters, and AWS::Config::RemediationConfiguration resources.

Centralized Deployment : The delegated administrator deploys the pack across the entire AWS Organization using PutOrganizationConformancePack : aws configservice put-organization-conformance-pack \

  • -organization-conformance-pack-name CIS-Benchmark-Pack \
  • -template-s3-uri "s3://central-sec-compliance/conformance-packs/cis-v3.yaml" \
  • -delivery-s3-bucket central-sec-compliance

Immutability & Tamper Resistance : Once deployed across the organization, member accounts cannot modify, disable, or delete the organizational conformance pack or its constituent rules. Even member account root credentials cannot alter organization-managed Config rules.

Multi-Account Aggregators : A centralized AWS Config Aggregator deployed in the security account aggregates compliance data and inventory from all member accounts across all AWS Regions, providing a unified compliance posture.