# Cloud Custodian runs YAML policies against live AWS, Azure and Google Cloud resources, and can remediate after the fact

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Cloud Custodian is an Apache 2.0 rules engine that reads YAML policies and acts on existing AWS, Azure and Google Cloud resources, either on a schedule or from cloud events. It is a CNCF incubating project. Release 0.9.53.0 is marked latest on the page read on 16 Nov 2026. Its dryrun mode lists matches without acting.

## Cloud Custodian described by eight fields, read 16 Nov 2026

| Field | Value |
| --- | --- |
| What it evaluates | Cloud resources (the README names EC2, ASG, Redshift, CosmosDB and Pub/Sub topics) through filters; the README also says it can run policies on infrastructure-as-code assets |
| Where it runs | As a cron job on a server, locally, or serverless with cloud event sources: AWS CloudWatch Events and Config rules, Azure EventGrid, GCP audit log and Pub/Sub |
| Policy language | YAML: each policy sets a resource type, filters, actions and a mode |
| Clouds and targets | AWS, Azure and Google Cloud; Kubernetes, Tencent Cloud and OpenStack in beta per cloudcustodian.io |
| License | Apache License 2.0 (LICENSE file, read 16 Nov 2026) |
| Maintainer | The Cloud Custodian community, a CNCF incubating project: accepted 25 Jun 2020, incubating since 14 Sep 2022 |
| Tested before enforcement | `custodian validate` checks the file and `custodian run --dryrun` shows which resources match, with no actions executed |
| Current version | 0.9.53.0, marked Latest; the releases page shows 01 Oct 22:58 with no year, read 16 Nov 2026 |

## Custodian acts on resources that exist, so it is corrective more often than preventive

The README says Custodian can enforce policies in real time by integrating with each provider's serverless features, or run as a cron job against large existing fleets. The Custodian documentation has separate mode pages for AWS, Azure and GCP. Its first example policy removes cross-account statements from S3 buckets. Its second runs on a CloudTrail RunInstances event and terminates any new EC2 instance whose volumes are not encrypted.

That second policy is a guardrail in effect, but the instance is created first and removed after. This differs from a deny in a [service control policy](/mechanisms/scp/) or an Azure Policy deny effect, where the request fails. The README also lists Terraform support for policies on infrastructure-as-code, and cloudcustodian.io labels that feature Alpha.

## Dryrun is the test step, and it runs against live data

The README shows three commands in order: validate the file, run with --dryrun and an output directory to see which resources match each policy without executing actions, then run. Because dryrun evaluates real resources, it shows the actual blast radius of a filter before an action such as terminate is allowed to run.

A native unit test framework for policies, comparable to `opa test` or `cfn-guard test`: none found on 16 Nov 2026 in the pages read.

## Event-mode policies need cloud-side setup that the engine provisions

The README says Custodian automatically provisions serverless functions and event sources. The quickstart policy names an IAM role, CloudCustodian-QuickStart, for its CloudTrail mode. That means the engine deploys code into the account it governs, and the identity it runs under becomes a privileged part of the account.

Multi-account use is listed as supported. How a team limits that identity per account is a deployment decision; the pages read give the capability and not a recommended boundary.

## Pair it with preventive guardrails rather than treating it as one

A common split is a preventive object for the rules that must never be broken, such as [Deny member accounts leaving the organization](/guardrails/aws-scp-deny-leave-org/), and Custodian for the rules that can be corrected after the fact. See [preventive vs detective controls](/guides/preventive-vs-detective-controls/) for that decision, [policy as code examples](/policy-as-code-examples/) for the YAML shape, and [policy as code tools](/policy-as-code-tools/) for the other engines.

## Related pages

- [Kyverno: fields, version and testing](/engines/kyverno/)
- [CloudFormation Guard: fields, version and testing](/engines/cloudformation-guard/)
- [AWS SCP examples explained: what each pattern blocks and breaks](/guides/aws-scp-examples-explained/)
- [All of them](/guides/)

## Sources

- GitHub: cloud-custodian/cloud-custodian: https://github.com/cloud-custodian/cloud-custodian (read 16 Nov 2026)
- GitHub: Cloud Custodian releases: https://github.com/cloud-custodian/cloud-custodian/releases (read 16 Nov 2026)
- GitHub: Cloud Custodian LICENSE: https://raw.githubusercontent.com/cloud-custodian/cloud-custodian/main/LICENSE (read 16 Nov 2026)
- Cloud Custodian home page: https://www.cloudcustodian.io/ (read 16 Nov 2026)
- CNCF: Cloud Custodian: https://www.cncf.io/projects/cloud-custodian/ (read 16 Nov 2026)
- Cloud Custodian: quick start: https://cloudcustodian.io/docs/quickstart/index.html (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudgovernancetools.com/engines/cloud-custodian/
