AWS Config

UpOpen Sourcecloud by Amazon Web Services★62· JavaScript· MIT

AWS Config API records AWS resource configuration history — compliance audit, change tracking, and rule-based auto-alerts.

Visit site ↗Source ↗Health checked 12h ago

Use it when

Complete config history for 200+ resource types

Watch for

Charged by recording count and rule evaluations — enabling all regions can get expensive

First check

PutConfigurationRecorder to enable the recorder. PutConfigRule to add compliance rules. View results in Config Dashboard.

Auth

—

CORS

HTTPS

Yes

Signup

Latency

42 ms

Protocol

REST

Pricing

—

Stars

Uptime · 30-day window

Probes: 30Uptime: 100%Avg latency: 48ms

GitHub activity

★ 62JavaScriptMIT17 open issuesLast commit 155d ago

About this API

AWS Config is a configuration management database — treats all your AWS resource configurations as "objects" with continuous recording and versioning on every change. Foundation for compliance and audit: regulator requires "all S3 buckets must be encrypted", Config continuously monitors every S3 bucket company-wide, alerting on violations; after a security incident, "who changed that security group yesterday" — Config provides full change timeline. Two rule types: managed rules (AWS-written, covering common compliance) and custom rules (your Lambda implementing business rules). Combined with Systems Manager Automation or Config remediation, supports auto-remediation — e.g. detect unencrypted S3 bucket, auto-enable encryption. Essential for enterprise AWS governance.

What you can build

1Compliance audit (all S3 buckets must be encrypted)
2Resource config change tracking (who changed which security group when)
3Rule-based auto-alerts (immediate alert on 0.0.0.0/0 inbound)
4Periodic compliance reporting

Strengths & limitations

Strengths

Complete config history for 200+ resource types
Built-in 100+ compliance rules (HIPAA, PCI, CIS, and other baselines)
Custom rules supported (Lambda)
Can pair with auto-remediation

Limitations

Charged by recording count and rule evaluations — enabling all regions can get expensive
Rule evaluations have latency (not real-time)

Getting started

PutConfigurationRecorder to enable the recorder. PutConfigRule to add compliance rules. View results in Config Dashboard.

FAQ

How expensive is Config?+

By recordings (~$0.003 per resource per change) + rule evaluations (~$0.001 per 1k). Full coverage all regions/types can cost $100-500/month for small companies.

Config vs. CloudTrail?+

CloudTrail records API calls (who called what); Config records resource state (what does the resource look like now). Complementary.