AWS Config vs Kyverno
AWS Config
aws.amazon.comKyverno
kyverno.ioSide by side
| Figure | AWS Config | Kyverno |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Web | Yes | Yes |
| Windows | — | Yes |
| macOS | — | Yes |
| Linux | — | Yes |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 2 |
| Spec score · Cloud Governance Software | 7.5 (#15) | 8.6 (#5) |
| Integrations | The feature page describes integrations with AWS Organizations, CloudTrail, Security Hub CSPM, Audit Manager, Systems Manager, Firewall Manager, EC2 Dedicated Hosts, and Application Load Balancers. | CNCF lists common integrations with Argo CD, Backstage, Flux and Kubernetes for GitOps and platform governance. |
| Intended users | AWS identifies security and governance teams, administrators in larger organizations, information security experts, compliance users, and infrastructure operators as beneficiaries. | The project describes Kyverno as designed for platform engineering teams and enabling security, compliance, automation, and governance through policy as code. |
| Purpose | AWS Config assesses, audits, and evaluates the configurations of AWS resources. | Kyverno is a Kubernetes-native policy engine for defining and enforcing policy as code. |
Plans
In their own words
AWS Config
AWS Config assesses, audits, and evaluates AWS resource configurations through web and API access. It records configuration changes so teams can inspect earlier states through the console, API, or CLI, and it can cover selected third-party resources such as on-premises servers, SaaS monitoring tools, and version control systems. Prebuilt rules and custom AWS Lambda rules evaluate configurations against policies. Conformance packs combine rules with remediation actions and aggregated compliance reporting. Aggregators centralize configuration metadata and rule compliance across accounts and Regions, while advanced queries use a subset of SQL SELECT syntax to search current state. Integrations described for the service include AWS Organizations, CloudTrail, Security Hub CSPM, Audit Manager, Systems Manager, Firewall Manager, EC2 Dedicated Hosts, and Application Load Balancers. Charges are usage-based for recorded configuration items and rule evaluations; related S3, SNS, and Lambda charges may also apply. Rules report status but do not prevent noncompliant changes.
Kyverno
Kyverno is a free, open-source policy engine for defining and enforcing policy as code in Kubernetes. Its stable policy types can validate, mutate, generate or delete resources, and verify container image signatures and attestations. The Kyverno CLI can test policies against Kubernetes resource manifests in CI before they are applied to a live cluster. Documentation describes use with Helm, YAML manifests, GitHub Actions and GitOps tools such as ArgoCD. Kyverno is installed in a Kubernetes cluster; Helm is recommended for production, and YAML manifests are also available. A standard installation requires an admission controller, while background, reports and cleanup controllers are optional. Production installations should use high availability mode. The project supports CEL-based policy types and describes applying Kubernetes-style policies outside Kubernetes as part of its mission. Its webhooks default to fail-closed, so matching requests can fail if the API server cannot reach Kyverno. The project documents Cosign signatures for images and manifests, and lists CLI binaries for Linux, macOS and Windows.