0
Misconfigurations cataloged
Across IAM, S3, RDS, EKS, networking, encryption, billing, and more.
0
Service groups covered
Generated from the checked-in aws-misconfig-db source of truth.
0
High-severity entries
Prioritized entries where the risk value is highest.
0% free
License
MIT. Mirror it, query it, train on it.
Browse the database

Searchable. Citable. LLM-ready.

Every entry is structured: IDs, severity, business impact, remediation, IaC patches, and an LLM-formatted body you can drop straight into a model context. Filter by service, severity, or compliance framework.

Why it exists

An open standard for AWS misconfigurations.

Every cloud security vendor keeps a private list. We're publishing ours — formatted for the tools you and your models actually use.

01 — For engineers

Citable IDs in every alert

Every BlueArch finding links back to a Hub entry with the same ID — so an alert in your inbox carries the full context, remediation, and compliance mapping. No more "what does this mean?"

Plain-text, version-controlled
02 — For LLMs

MCP-formatted bodies

Entries ship as Model Context Protocol manifests — drop one into Claude, GPT, or your in-house model and it knows the rule, the impact, and the fix. No prompt engineering required.

MCP · JSON · YAML · Markdown
03 — For everyone

Free, forever, MIT

Mirror it. Fork it. Train on it. Run your own queries inside your VPC. We mirror GitHub every 5 minutes — the source of truth is always the repo.

github.com/bluearchio/aws-misconfig-db
"

We replaced three internal "AWS best practice" wikis with the Governance Hub. Every alert in our pager now has a permalink an LLM can read. New engineers ramp in days, not quarters.

RK
R. Kapoor
Principal SRE · Series-C SaaS · ~$4M AWS / yr

Case snapshot

Time to remediate
↓ 71%
Findings auto-triaged
83%
Internal wikis sunset
3
Ramp time, new SRE
8 days
FAQ

Common questions.

If something isn't covered, open an issue on the repo.

Is the database really free?+
Yes. MIT-licensed, hosted on GitHub, mirrored here every 5 minutes. We monetize the commercial products (BlueArch CLI, Tag Manager) that use the Hub — not the Hub itself.
How do I integrate it with my LLM?+
Each entry ships as a Model Context Protocol (MCP) manifest. Point your client at our MCP server, or self-host the repo and load entries as static context. Examples for Claude, GPT, and Bedrock live in the README.
How often is it updated?+
Continuously. The mirror runs every 5 minutes; new AWS services and regions are typically cataloged within 24 hours of GA. Subscribe to the repo for release notifications.
Can I contribute?+
Please do. Open a PR with a YAML entry following the template. Every accepted PR is credited in the repo and on the contributors page.
How does this relate to AWS Config / Security Hub?+
AWS Config rules describe detection; Security Hub aggregates findings. The Governance Hub provides the human + LLM context layer on top — what the misconfig means for your business, how to fix it, and the compliance mappings. Use them together.

Put the Hub in your loop.

Wire it into your terminal, your CI, or your model context. Or pair it with BlueArch CLI to get alerts that already cite Hub entries — with the context, the patch, and the compliance trail attached.