L18. AWS Config, Well-Architected & Compliance Automation
Video generating
Check back soon for the video lesson on AWS Config, Well-Architected & Compliance Automation
Course outlineLesson 18 of 18
From point-in-time manual audits to continuous compliance: Config rules, cross-account aggregators, conformance packs, and auto-remediation via SSM Automation.
From Manual Audits to Continuous Evaluation
AWS Config records supported resource configurations within the recorder's configured scope and recording frequency. Enable the required recorder and rules in each account and Region. Rules can be AWS managed or custom, using Lambda functions or Guard policy rules. Evaluation can be change-triggered, periodic, or proactive where supported; it is not an instantaneous check of every resource. Unencrypted EBS volumes and overly permissive security groups are examples of findings.
Seeing Compliance Across Every Account and Region
A single account's Config data only tells part of the story once an organization runs dozens of accounts across multiple regions. Config aggregators solve this by pulling configuration and compliance data from many source accounts and regions into one aggregator account, giving security and compliance teams a single place to see the org-wide picture instead of logging into each account individually. An aggregator is read-only: it does not deploy rules, enable recording, or change resources in source accounts.
Deploying a Whole Compliance Framework at Once
Conformance packs bundle a collection of Config rules, and optionally their remediation actions, into a single deployable template. Instead of enabling dozens of individual rules by hand in every account, a team deploys one conformance pack and gets an entire framework, such as a CIS benchmark or an internal operational best-practice set, rolled out all at once. Combined with a Config aggregator, this is the standard pattern for rolling out and monitoring a compliance standard across a large multi-account environment.
Closing the Loop with Auto-Remediation
Detecting a non-compliant resource is only half the job. Config supports auto-remediation by linking a rule to an SSM Automation document, with explicitly configured permissions, parameters, retry limits, and exceptions. Compliance snapshots can be stale, so the runbook should recheck the live resource before making changes. EBS cannot enable encryption on an existing unencrypted volume in place: a tested replacement workflow copies a snapshot with encryption, creates a new encrypted volume, and replaces the old volume under an approved change plan.
| Stage | Component |
|---|---|
| Detect drift | AWS Config rule (managed, custom Lambda, or Guard) |
| Roll out at scale | Conformance pack |
| See org-wide status | Config aggregator |
| Fix automatically | SSM Automation document |
Where the Well-Architected Tool Fits
The Well-Architected Tool, and specifically its Security Pillar, gives teams a structured framework of best-practice questions to walk through when reviewing a workload's design. It is valuable for catching architectural and process gaps that a point-in-time rule check would never surface, but it is a periodic review exercise, not a continuously running control. It complements tools like Config and Security Hub; it does not replace them, and a workload that scores well on a Well-Architected review can still drift out of compliance the next day if nothing is continuously monitoring it. Exam tip: If a question describes ongoing, automatic detection and correction of misconfigurations, that is Config plus SSM Automation. If it describes a structured, human-led review against best-practice questions, that is the Well-Architected Tool, and the two are complementary, not interchangeable.
References
- AWS: rule types and evaluation triggers
- AWS: auto-remediation and stale compliance data
- AWS: EBS encryption constraints
- AWS: aggregation is read-only
- AWS: conformance packs
- AWS: Well-Architected Tool
- AWS: SCS-C03 exam guide
Continue Learning
Review organization guardrails to distinguish preventive policies from detective rules.
- ✓AWS Config records configuration changes to resources over time and evaluates them against managed or custom (Lambda or Guard) Config rules
- ✓Config aggregators combine configuration and compliance data across multiple accounts and regions into one account for org-wide visibility
- ✓Conformance packs bundle a set of Config rules and optional remediation actions into a single deployable template, useful for rolling out an entire compliance framework at once
- ✓Config supports auto-remediation by linking a non-compliant rule to an SSM Automation document, fixing issues automatically instead of waiting for a manual audit cycle
- ✓The Well-Architected Tool's Security Pillar provides a structured review framework that complements, but does not replace, continuous automated tools like Config and Security Hub
1. A team needs to detect unencrypted EBS volumes and orchestrate a tested encrypted-volume replacement runbook. Which combination supports that workflow?
2. A company operating 50 AWS accounts wants a single place to see compliance status against a CIS benchmark across all of them. What combination of features supports this?
3. What is the relationship between the AWS Well-Architected Tool's Security Pillar and continuous compliance tools like AWS Config or Security Hub?