
AWS Config records configuration state and evaluates compliance. To automatically remediate non-compliant resources, configure remediation actions that AWS Config can invoke through EventBridge, Systems Manager Automation, or Lambda.
- Continuous configuration monitoring and historic change tracking.
- Built-in and custom rule evaluation for compliance and best practices.
- Integration points to automate notifications and remediation workflows.
- Centralized views and aggregate reporting for multi-account, multi-region environments.

- Tracks Configuration Items (CIs) that include metadata, attributes, relationships, and snapshots.
- Records a history of configuration versions so you can perform forensic analysis and audits.
- Triggers events and workflows when resources change or when rules evaluate to non-compliant.

How AWS Config represents resources
- A Configuration Item (CI) includes the resource’s metadata, attributes, relationships, and configuration snapshot.
- Record on every change (recommended) or use periodic snapshots (e.g., every 5 or 10 minutes).
- Use the versioned history to examine prior configurations and detect drift.

- The AWS Config Recorder captures configuration items for supported resource types on create, update, and delete events — or periodically if configured.
- Delivery Channel controls how AWS Config persists data. Typically, AWS Config writes configuration snapshots and history to an S3 bucket.
- When sending notifications (SNS) or invoking other services, verify that the SNS topic and downstream actions (Lambda, EventBridge, Systems Manager) have the required IAM permissions.
When using SNS, EventBridge, Lambda, or Systems Manager for notifications or remediation, ensure IAM policies and SNS publish permissions are configured correctly to avoid failed remediation attempts.

- Resource changes → AWS Config records a CI → Config persists snapshots to S3 and emits events → EventBridge/SNS/Lambda/SSM handle notifications and remediation.

- AWS-managed rules: Prebuilt checks for common best practices (EBS encryption, VPC settings, Auto Scaling, etc.). Fast to deploy and require no code.
- Custom rules: Implement business-specific logic using AWS Lambda functions (any supported runtime), or create custom remediation using Systems Manager Automation documents.


- When a resource is NON_COMPLIANT, AWS Config can:
- Trigger managed remediation actions (predefined by AWS).
- Invoke custom remediation via Lambda functions or Systems Manager Automation runbooks.
- Trigger types:
- Configuration change trigger — evaluate when the resource changes.
- Periodic trigger — evaluate on a schedule.
- Hybrid trigger — combination of change-based and periodic evaluations.
- Typical remediation paths: EventBridge → Systems Manager Automation, or EventBridge/SNS → Lambda → call AWS APIs to remediate.


- Notify operators using SNS, email integrations, or ticketing systems.
- Route the evaluation event via EventBridge to automated remediation workflows: Systems Manager Automation runbooks or Lambda functions.
- Use AWS-managed remediation actions where available, or implement custom remediations with Lambda/SSM.


- Self-healing infrastructure and faster mean time to repair (MTTR).
- Improved consistency and reduced operational risk.
- Scales across accounts and regions when combined with Aggregators and Conformance Packs.
- Can include business logic or safety checks (for example, require manual approval before applying disruptive changes).
- Conformance Packs are YAML bundles that group multiple AWS Config rules and remediation actions.
- Use Conformance Packs to apply consistent control sets across accounts, regions, or an entire AWS Organization.

- AWS Config Aggregator centralizes Config data from multiple accounts and regions into a single aggregated view for centralized governance and auditing.
- Aggregators simplify tracking trends and metrics (resource counts, compliance rates) across an enterprise.


- Enable AWS Config organization-wide (AWS Control Tower can help bootstrap this).
- Persist configuration history and snapshots to S3 for auditability; apply proper bucket access controls and lifecycle rules.
- Use Config Aggregators for cross-account and cross-region visibility.
- Start with managed rules for standard checks, and add custom rules for business-specific controls.
- Automate safe remediation where appropriate, and include approvals or scoped execution for risky changes.
- Integrate AWS Config findings with Security Hub and ticketing/alerting systems for centralized incident handling.

- AWS Config delivers continuous configuration monitoring, versioned history, and rule-based evaluations to support governance and compliance.
- Use managed rules for common checks, custom rules for specialized logic, Conformance Packs to package policies, and Aggregators to centralize data across accounts and regions.
- Combine Config with EventBridge, SNS, Lambda, and Systems Manager Automation for notifications and automated remediation to achieve self-healing infrastructure.