Study guide
15.2 AWS Config, Conformance Packs & Automated Remediation
AWS Certified Security – Specialty SCS-C03
Track your progress as you read
Finished sections get a check mark.
1 Chapter 0: Getting Started with the SCS-C03 Exam
0.1 SCS-C03 Exam Format, Domains & Study Strategy
2 Chapter 1: Security Monitoring, Alerting & Threat Detection Services
1.1 Workload Monitoring & Health Check Strategies 1.2 Amazon GuardDuty Architecture & Finding Types 1.3 AWS Security Hub & Automated Conformance Assessment 1.4 Amazon Macie & Automated Data Classification
3 Chapter 2: Enterprise Logging Architecture & Analysis
2.1 Multi-Account CloudTrail & Organization Trails 2.2 Amazon Security Lake & OCSF Log Normalization 2.3 Network Telemetry: VPC Flow Logs & Route 53 Resolver Logs 2.4 Troubleshooting Security Telemetry & Log Ingestion 2.5 Analyzing, Normalizing & Correlating Security Logs
4 Chapter 3: Incident Readiness, Response Planning & Automated Runbooks
3.1 Incident Response Planning & Blast Radius Mitigation 3.2 Testing & Validating Incident Response Plans 3.3 Automated Incident Remediation with EventBridge & Step Functions 3.4 Systems Manager OpsCenter & Incident Manager Runbooks
5 Chapter 4: Digital Forensics, Evidence Preservation & Root Cause Analysis
4.1 Forensic Artifact Capture & Chain of Custody 4.2 Threat Containment & Network Quarantine Techniques 4.3 Correlating Events & Root Cause Analysis with Amazon Detective
6 Chapter 5: Edge Protection, WAF & DDoS Mitigation
5.1 CloudFront Security Headers & Origin Access Control 5.2 AWS WAF Architecture & Advanced Rule Sets 5.3 AWS Shield Advanced & DDoS Defense Architectures 5.4 Edge Integrations: Managed Rule Groups, OCSF Ingestion, IoT Policies & CORS
7 Chapter 6: Compute Workload Hardening, Vulnerability Management & GenAI Security
6.1 Golden AMIs & Container Image Hardening Pipelines 6.2 Amazon Inspector Vulnerability Management & Patch Automation 6.3 Generative AI Security: Amazon Bedrock Guardrails & Model Protection 6.4 Instance Profiles, Service Roles & Execution Roles for Compute 6.5 Secure Administrative Access: Session Manager & EC2 Instance Connect
8 Chapter 7: Network Security, Segmentation, Private Connectivity & Encryption in Transit
7.1 Layered Traffic Filtering: SGs, NACLs & AWS Network Firewall 7.2 Hybrid Connectivity Security: VPN, Direct Connect & MACsec 7.3 Zero-Trust Access & Network Access Analysis 7.4 Enforcing Encryption in Transit: ELB Security Policies, TLS & HTTPS-Only Access 7.5 Private Access: VPC Endpoints, PrivateLink, Client VPN & Verified Access 7.6 Inter-Resource Encryption in Transit: Nitro, EMR, EKS & SageMaker AI
9 Chapter 8: Enterprise Authentication, Federation & Directory Services
8.1 AWS IAM Identity Center & Enterprise IdP Integration 8.2 Amazon Cognito User Pools & Identity Pools 8.3 AWS Security Token Service (STS) & Temporary Credential Workflows 8.4 Troubleshooting Identity & Authentication Failures
10 Chapter 9: Advanced Authorization Architecture & Policy Evaluation
9.1 Complete AWS Policy Evaluation Logic & Decision Flow 9.2 Permission Boundaries & Safe Admin Delegation 9.3 Attribute-Based Access Control (ABAC) with IAM Tags
11 Chapter 10: Least Privilege, Policy Validation & External Access Auditing
10.1 IAM Roles Anywhere & Amazon Verified Permissions 10.2 Auditing External & Unused Access with IAM Access Analyzer 10.3 Analyzing Authorization Failures & Policy Simulation
12 Chapter 11: Cryptographic Services: KMS Architecture & Key Governance
11.1 AWS KMS Architecture, Key Policies & Key Types 11.2 KMS Grants, Encryption Context & Multi-Region Keys 11.3 Imported Key Material (BYOK) & CloudHSM Key Stores
13 Chapter 12: Secrets Management, Sensitive Data Masking & PKI
12.1 AWS Secrets Manager & Systems Manager Parameter Store 12.2 Sensitive Data Masking in Telemetry & Messaging 12.3 AWS Certificate Manager (ACM) & Private CA Architecture
14 Chapter 13: Storage Encryption, Integrity, Lifecycle & Backup Protection
13.1 S3 Encryption Modes & S3 Bucket Keys 13.2 Data Integrity Protection: Object Lock, Vault Lock & Code Signing 13.3 Secure Data Lifecycle, Cross-Account Replication & Backup Vault Lock 13.4 Lifecycle, Backup & Secure Replication Beyond S3: EFS, FSx, DLM, DataSync & Air-Gapped Vaults
15 Chapter 14: Multi-Account Architecture, Organizations & Control Tower Governance
14.1 AWS Organizations Structure, Hierarchy & Resource Control 14.2 AWS Control Tower Landing Zone & Guardrail Framework 14.3 Delegated Administrator Architecture & Root User Governance 14.4 Centralized Resource Sharing with RAM & Service Catalog
16 Chapter 15: Compliance Automation, Infrastructure as Code Security & Auditing
15.1 Infrastructure as Code Security & Multi-Account Deployment 15.2 AWS Config, Conformance Packs & Automated Remediation 15.3 Audit Evidence Collection & Well-Architected Security Reviews
15.2 AWS Config, Conformance Packs & Automated Remediation
Key Takeaways Explain This Topic AI
AWS Config continuously records resource configurations, relationships, and state modifications into Configuration Items (CIs), publishing history and snapshots to Amazon S3 and notifications to Amazon SNS.
Config Rules evaluate resource compliance using either configuration change triggers (event-driven evaluation upon CI creation/modification) or periodic triggers (scheduled intervals from 1 to 24 hours).
Multi-Account Multi-Region Configuration Aggregators centralize compliance data across an entire AWS Organization into a dedicated security account, eliminating the need to log into individual member accounts.
Conformance Packs package collections of Config rules and remediation documents into single, version-controlled YAML templates; organization conformance packs deployed centrally are immutable in member accounts.
Automated remediation links non-compliant Config rule evaluations directly to AWS Systems Manager Automation documents, executing corrective actions automatically or manually with configurable retry logic and dynamic resource ID parameter mapping.
Last updated: September 2026
15.2 AWS Config, Conformance Packs & Automated Remediation
Maintaining continuous security compliance across distributed multi-account cloud environments requires continuous monitoring, auditing, and recording of resource configurations. Traditional periodic audits rely on point-in-time manual assessments that fail to detect transient misconfigurations, ephemeral resource exposures, or unauthorized infrastructure alterations. AWS Config addresses this challenge by providing a continuous, fully managed configuration recording and compliance auditing service.
AWS Config tracks the detailed inventory of supported AWS resources, logs configuration history, models inter-resource relationships, and evaluates whether resource configurations conform to internal security baselines and regulatory frameworks. When combined with Conformance Packs and AWS Systems Manager Automated Remediation , AWS Config transitions security governance from passive alerting to active, autonomous self-healing.
AWS Config Core Architecture
The AWS Config operational workflow comprises three fundamental components: the Configuration Recorder , Configuration Items (CIs) , and the Delivery Channel . [Resource State Change] ──> [Configuration Recorder] ──> [Configuration Item (CI)]
- │
- ┌────────────────────────────────────────────┴─────────────────────────────┐
- ▼ ▼
- [Delivery Channel] [Config Rules Engine]
- ├── S3: Configuration History & Snapshots ├── Evaluate Compliance
- └── SNS: Real-time Configuration Streams └── Trigger SSM Remediation
- 1. Configuration Recorder
The Configuration Recorder detects changes in resource states and creates corresponding configuration records. Security engineers configure the recorder to capture:
All Supported Resources : Records every supported AWS resource in the target Region.
Specific Resource Types : Selectively records high-risk services (e.g., AWS::IAM::* , AWS::S3::Bucket , AWS::EC2::SecurityGroup ).
Global Resources : IAM users, groups, roles, and customer-managed policies are global resources. To avoid duplicate Configuration Items and billing charges across multiple Regions, global resources should be recorded in only one Region per account (typically us-east-1 ).
Recording Frequency : Organizations can select Continuous Recording (real-time recording of changes as they occur, essential for incident detection) or Daily Recording (aggregates changes every 24 hours, suitable for cost-sensitive, low-churn environments).
2. Configuration Items (CIs)
A Configuration Item (CI) is a point-in-time JSON document representing the state of an AWS resource. Each CI contains:
Metadata : CI capture time, CI version, AWS account ID, Region, and resource type.
Attributes : Resource ID, resource ARN, resource tags, and creation time.
Configuration : The full serialized configuration payload of the resource (e.g., S3 bucket encryption algorithms, security group inbound/outbound rules).
Relationships : Graph linkages to associated resources (e.g., an EC2 instance CI references its attached EBS volumes, ENIs, and security groups).
3. Delivery Channel
The Delivery Channel exports CIs for long-term retention and real-time processing:
Amazon S3 Bucket : Stores configuration history files (delivered periodically throughout the day) and periodic Configuration Snapshots (complete point-in-time inventories of all recorded resources).
Amazon SNS Topic : Streams configuration change notifications and compliance evaluation status transitions in real time, enabling downstream integration with SIEMs, ticketing systems, or event routers.
AWS Config Rules: Managed vs. Custom
AWS Config Rules represent desired configuration states for specific resource types or entire accounts. Config evaluates resources against these rules to determine whether resources are COMPLIANT , NON_COMPLIANT , or NOT_APPLICABLE .
Evaluation Triggers
Config rules are executed based on one of two trigger mechanisms:
Configuration Changes (Event-Driven) : Evaluated immediately when AWS Config detects a change in the resource's configuration, tags, or deletion. Used for critical security controls requiring immediate detection (e.g., S3 public access, security group rule expansion).
Periodic (Schedule-Driven) : Evaluated at a fixed time frequency (1 hour, 3 hours, 6 hours, 12 hours, or 24 hours). Required for rules that evaluate time-dependent criteria (e.g., checking whether IAM user access keys have remained unrotated for more than 90 days).
Rule Types: Managed vs. Custom Lambda vs. Custom Guard
Rule Classification Architectural Mechanics Maintenance Overhead Operational Flexibility
AWS Managed Rules Pre-built rules authored and maintained by AWS (e.g., s3-bucket-public-read-prohibited , encrypted-volumes , iam-root-access-key-check ). Zero maintenance : Automatically updated by AWS as service APIs evolve. High for standard checks; limited to parameters exposed by AWS.
Custom Rules (Lambda) Evaluates resources by invoking a user-managed AWS Lambda function that queries resource state and returns results via the PutEvaluations API. High maintenance : Requires maintaining Lambda runtime, execution roles, VPC access, and error-handling code. Unlimited flexibility: Can perform complex cross-service lookups, API queries, and external threat intelligence checks.
Custom Rules (Guard) Evaluates resources using CloudFormation Guard DSL rules defined directly within the Config rule without provisioning Lambda functions. Low maintenance : No Lambda function to patch, manage, or monitor; eliminates cold starts. Fast, declarative policy-as-code evaluations for properties present within the Configuration Item.
Lambda Custom Rule Lifecycle & PutEvaluations API
When a configuration change occurs on a resource monitored by a Lambda-based custom rule:
AWS Config invokes the Lambda function asynchronously, passing an event payload containing invokingEvent (containing the Configuration Item) and ruleParameters .
The Lambda function inspects the CI's configuration properties.
The function determines compliance and constructs an evaluation result containing ComplianceResourceType , ComplianceResourceId , ComplianceType ( COMPLIANT or NON_COMPLIANT ), and OrderingTimestamp .
The Lambda function calls the AWS Config API config:PutEvaluations to record the finding in AWS Config. If the function fails to call PutEvaluations , the rule status transitions to EVALUATION_FAILURE .
Loading diagram... AWS Config Multi-Account Compliance Aggregation & Automated SSM Remediation Workflow
Multi-Account Multi-Region Configuration Aggregators
In an enterprise environment spanning dozens or hundreds of AWS accounts and multiple active Regions, reviewing compliance on an account-by-account basis is unworkable. AWS Config provides Configuration Aggregators to centralize inventory tracking and compliance posture.
Aggregator Types
Organization Aggregators : When configured from the AWS Organizations management account or an AWS Config Delegated Administrator account, the aggregator automatically discovers and aggregates configuration and compliance data from all member accounts in the organization across all active Regions . As new accounts join the organization, they are automatically enrolled into the aggregator without configuration changes.
Individual Account Aggregators : Manually configured to aggregate specific account IDs. Requires target accounts to grant authorization via PutConfigurationAggregatorAuthorization .
Organization-Wide Config Rules
Security teams can deploy rules enterprise-wide using Organization Config Rules ( PutOrganizationConfigRule ).
Managed or custom rules are defined once in the management or delegated administrator account.
AWS Config deploys the rule to all current and future member accounts in the Region where you create it (repeat per Region), except accounts you exclude.
Immutability in Member Accounts : Member accounts cannot modify, disable, or delete Organization Config rules. Local administrators attempting to delete the rule receive an AccessDeniedException .
AWS Config Conformance Packs
A Conformance Pack is a packaged collection of AWS Config rules and automated remediation actions authored as a single YAML template. Conformance packs simplify compliance management by providing version-controlled governance blueprints mapped to specific industry standards and regulatory frameworks.
Supported Regulatory Frameworks
AWS provides pre-architected, managed conformance pack templates for major regulatory standards:
NIST SP 800-53 (Rev 4 and Rev 5) : Comprehensive security and privacy controls for federal and enterprise systems.
PCI DSS v4.0 : Controls covering network segmentation, encryption of cardholder data, vulnerability management, and access control.
HIPAA Security Rule : Standards for safeguarding electronic protected health information (ePHI).
CIS AWS Foundations Benchmark : Industry-consensus best practices for identity, logging, monitoring, and networking.
FedRAMP Moderate & High : Federal Risk and Authorization Management Program security baselines.
Organization Conformance Packs
Similar to organization rules, Organization Conformance Packs ( PutOrganizationConformancePack ) deploy entire suites of rules and remediation documents across an AWS Organization:
Deployed centrally from the management account or a delegated administrator account.
Automatically provisioned into new member accounts when they are added to the organization.
Cannot be deleted, modified, or bypassed by IAM principals in member accounts, ensuring an immutable compliance baseline.
Support parameterized templates, allowing organizations to override specific rule parameters (e.g., passing custom KMS key ARNs or retention day thresholds) across different OUs.
Automated Remediation with Systems Manager Automation
Detecting a non-compliant resource satisfies audit visibility, but security defense requires minimizing the window of vulnerability. AWS Config integrates natively with AWS Systems Manager (SSM) Automation Documents to execute automated remedial actions.
Remediation Architecture & Configuration
Security engineers attach a Remediation Configuration to an AWS Config rule using the PutRemediationConfigurations API. The configuration specifies:
Target Document : The SSM Automation document to execute (AWS-managed or custom).
Execution Mode : Automatic Execution (triggers immediately upon non-compliant evaluation) or Manual Execution (operator must review finding and click "Remediate" in the console or CLI).
Parameters : Input parameters passed to the SSM document. Config supports Dynamic Parameters (binding the non-compliant resource's identifier using the RESOURCE_ID token) and Static Parameters (fixed values such as notification ARNs or IAM roles).
Retry Controls : Governs remediation resilience via MaximumAutomaticAttempts (1 to 25 attempts, default 5) and RetryAttemptSeconds (1 to 2,678,000 seconds, default 60 seconds).
Common AWS-Managed Remediation Documents
SSM Automation Document Remedial Action Performed dynamic Parameter Binding
AWSConfigRemediation-ConfigureS3BucketPublicAccessBlock Enables S3 Block Public Access (all four settings) on the non-compliant bucket. BucketName: RESOURCE_ID
AWS-EnableCloudTrail Creates a trail that delivers to a specified S3 bucket and starts logging. TrailName , S3BucketName (static)
AWSConfigRemediation-RemoveUnrestrictedSourceIngressRules Removes ingress rules that allow 0.0.0.0/0 or ::/0 . ( AWS-DisablePublicAccessForSecurityGroup removes open SSH and RDP rules only.) SecurityGroupId: RESOURCE_ID
AWSConfigRemediation-EnableKeyRotation Enables automatic rotation on a customer managed KMS key. KeyId: RESOURCE_ID
AWS-ConfigureS3BucketLogging Configures server access logging delivery to a designated central logging bucket. BucketName: RESOURCE_ID
Remediation Execution Role Permissions
For automated remediation to succeed, the remediation configuration must specify an IAM service role ( AutomationAssumeRole ) that Systems Manager assumes to perform the action:
The role must trust the Systems Manager service principal ( ssm.amazonaws.com ).
The role's policy must grant the exact least-privilege actions executed by the SSM document (e.g., s3:PutBucketPublicAccessBlock for S3 remediation, or ec2:RevokeSecurityGroupIngress for security group remediation).
If remediating across accounts in an Organization Conformance Pack, the execution role must be pre-provisioned in member accounts with identical names and trust relationships.
Specialty Exam Pitfalls & Architectural Traps
Detective Nature of Config vs. Preventive Controls : Believing that AWS Config rules can block a developer from deploying an unencrypted resource. Config is strictly detective ; the resource is created first, a CI is recorded, and Config marks it NON_COMPLIANT . To block creation proactively, use Service Control Policies (SCPs), CloudFormation Hooks, or cfn-guard in CI/CD.
Global Resource Duplication Across Regions : Enabling global resource recording (IAM) in all active Regions. This creates duplicate Configuration Items for the exact same IAM changes, clutters S3 delivery buckets, and inflates AWS Config recording costs. Always record global resources in only one Region per account .
SSM Remediation Role Missing in Spoke Accounts : Deploying an Organization Conformance Pack with automated remediation, but failing to deploy the corresponding SSM Automation execution IAM role into all member accounts. The Config rule will evaluate resources as NON_COMPLIANT , but remediation will fail with ActionExecutionFailed because Systems Manager cannot assume the specified role ARN.
Event-Driven vs. Scheduled Rule Mismatches : Configuring an event-driven trigger for a rule that requires periodic time calculations (e.g., checking for unrotated IAM credentials older than 90 days). Because an inactive IAM user's configuration never changes, no CI is emitted, and the rule will never trigger unless configured with a Periodic schedule.