Basic Information
| Field | Value |
|---|---|
| English | AWS Config |
| Full name | AWS Config |
| Chinese | 资源配置记录与合规评估 |
| Japanese | AWS Config（リソース構成記録・コンプライアンス評価） |
| Exam frequency | ⭐⭐⭐⭐⭐ |
| Often confused with | AWS CloudTrail / AWS Audit Manager |
One-line summary
Record resource configuration history and relationships, then continuously evaluate compliance with rules.
Core capabilities and use cases
- The configuration recorder captures supported resource configuration items and relationships.
- The delivery channel sends snapshots and history to designated destinations.
- Managed or custom Config rules evaluate resources on changes or on a schedule.
- Results include COMPLIANT and NON_COMPLIANT and can be aggregated across accounts and Regions.
- Remediation commonly uses Systems Manager Automation and requires carefully scoped permissions.
Exam focus and common pitfalls
- Choose Config for configuration history, drift, and rule-based compliance checks.
- CloudTrail identifies the actor and API; Audit Manager organizes evidence by audit framework.
- A NON_COMPLIANT result does not mean remediation has completed automatically.
Key takeaway
What did the configuration become, and does it comply with the rule? Think AWS Config.