Management and Governance
CoreAWS Config
Resource configuration history and compliance evidence.
Key points
- AWS Config records resource configuration state and change history and evaluates configurations against rules.
- It supplies governance evidence about resource configuration, not application records or API call history.
Best-known use cases
- Track configuration changes to governed data resources.
- Evaluate resource configurations against compliance rules.
What candidates often confuse it with
- Config answers how a resource's configuration changed; CloudTrail answers which API actor performed an action.
Key takeaway
Choose AWS Config when an investigation or control depends on resource configuration history.
Relevant exam tasks
- D4.5 — Task 4.5: Understand data privacy and governance
- 4.5.4 — Viewing configuration changes that have occurred in an account (for example, AWS Config).