Package: c7n
Cloud Custodian (c7n)Cloud Custodian, also known as c7n, is a rules engine for managing
public cloud accounts and resources. It allows users to define
policies to enable a well managed cloud infrastructure, that's both
secure and cost optimized. It consolidates many of the adhoc scripts
organizations have into a lightweight and flexible tool, with unified
metrics and reporting.Custodian can be used to manage AWS, Azure, and GCP environments by
ensuring real time compliance to security policies (like encryption and
access requirements), tag policies, and cost management via garbage
collection of unused resources and off-hours resource management.Custodian also supports running policies on infrastructure as code assets
to provide feedback directly on developer workstations or within CI pipelines.Custodian policies are written in simple YAML configuration files that
enable users to specify policies on a resource type (EC2, ASG, Redshift,
CosmosDB, PubSub Topic) and are constructed from a vocabulary of filters
and actions.It integrates with the cloud native serverless capabilities of each
provider to provide for real time enforcement of policies with builtin
provisioning. Or it can be run as a simple cron job on a server to
execute against large existing fleets.Cloud Custodian is a CNCF Incubating project, lead by a community of hundreds
of contributors.FeaturesComprehensive support for public cloud services and resources with a
rich library of actions and filters to build policies with.Run policies on infrastructure as code (terraform, etc) assets.Supports arbitrary filtering on resources with nested boolean
conditions.Dry run any policy to see what it would do.Automatically provisions serverless functions and event sources (
AWS CloudWatchEvents, AWS Config Rules, Azure EventGrid, GCP
AuditLog & Pub/Sub, etc)Cloud provider native metrics outputs on resources that matched a
policyStructured outputs into cloud native object storage of which
resources matched a policy.Intelligent cache usage to minimize api calls.Supports multi-account/subscription/project usage.Battle-tested - in production on some very large cloud environments.LinksHomepageDocsProject RoadmapDeveloper InstallPresentationsYouTube ChannelQuick InstallCustodian is published on pypi as a series of packages with thec7nprefix, its also available as a docker image.$python3-mvenvcustodian
$sourcecustodian/bin/activate(custodian)$pipinstallc7nUsageThe first step to using Cloud Custodian (c7n) is writing a YAML file
containing the policies that you want to run. Each policy specifies
the resource type that the policy will run on, a set of filters which
control resources will be affected by this policy, actions which the policy
with take on the matched resources, and a mode which controls which
how the policy will execute.The best getting started guides are the cloud provider specific tutorials.AWS Getting StartedAzure Getting StartedGCP Getting StartedAs a quick walk through, below are some sample policies for AWS resources.will enforce that no S3 buckets have cross-account access enabled.will terminate any newly launched EC2 instance that do not have an encrypted EBS volume.will tag any EC2 instance that does not have the follow tags
"Environment", "AppId", and either "OwnerContact" or "DeptID" to
be stopped in four days.policies:-name:s3-cross-accountdescription:|Checks S3 for buckets with cross-account access andremoves the cross-account access.resource:aws.s3region:us-east-1filters:-type:cross-accountactions:-type:remove-statementsstatement_ids:matched-name:ec2-require-non-public-and-encrypted-volumesresource:aws.ec2description:|Provision a lambda and cloud watch event targetthat looks at all new instances and terminates those withunencrypted volumes.mode:type:cloudtrailrole:CloudCustodian-QuickStartevents:-RunInstancesfilters:-type:ebskey:Encryptedvalue:falseactions:-terminate-name:tag-complianceresource:aws.ec2description:|Schedule a resource that does not meet tag compliance policies to be stopped in four days. Note a separate policy using the`marked-for-op` filter is required to actually stop the instances after four days.filters:-State.Name:running-"tag:Environment":absent-"tag:AppId":absent-or:-"tag:OwnerContact":absent-"tag:DeptID":absentactions:-type:mark-for-opop:stopdays:4You can validate, test, and run Cloud Custodian with the example policy with these commands:# Validate the configuration (note this happens by default on run)$custodianvalidatepolicy.yml# Dryrun on the policies (no actions executed) to see what resources# match each policy.$custodianrun--dryrun-soutpolicy.yml# Run the policy$custodianrun-soutpolicy.ymlYou can run Cloud Custodian via Docker as well:# Download the image$dockerpullcloudcustodian/c7n
$mkdiroutput# Run the policy## This will run the policy using only the environment variables for authentication$dockerrun-it\-v$(pwd)/output:/home/custodian/output\-v$(pwd)/policy.yml:/home/custodian/policy.yml\--env-file<(env|grep"^AWS\|^AZURE\|^GOOGLE")\cloudcustodian/c7nrun-v-s/home/custodian/output/home/custodian/policy.yml# Run the policy (using AWS's generated credentials from STS)## NOTE: We mount the ``.aws/credentials`` and ``.aws/config`` directories to# the docker container to support authentication to AWS using the same credentials# credentials that are available to the local user if authenticating with STS.$dockerrun-it\-v$(pwd)/output:/home/custodian/output\-v$(pwd)/policy.yml:/home/custodian/policy.yml\-v$(cd~&&pwd)/.aws/credentials:/home/custodian/.aws/credentials\-v$(cd~&&pwd)/.aws/config:/home/custodian/.aws/config\--env-file<(env|grep"^AWS")\cloudcustodian/c7nrun-v-s/home/custodian/output/home/custodian/policy.ymlThecustodian cask
toolis a go binary
that provides a transparent front end to docker that mirors the regular
custodian cli, but automatically takes care of mounting volumes.Consult the documentation for additional information, or reach out on gitter.Cloud Provider Specific HelpFor specific instructions for AWS, Azure, and GCP, visit the relevant getting started page.AWSAzureGCPGet InvolvedGitHub- (This page)Slack- Real time chat if you're looking for help or interested in contributing to Custodian!Gitter- (Older real time chat, we're likely migrating away from this)Mailing List- Our project mailing list, subscribe here for important project announcements, feel free to ask questionsReddit- Our subredditStackOverflow- Q&A site for developers, we keep an eye on thecloudcustodiantagYouTube Channel- We're working on adding tutorials and other useful information, as well as meeting videosCommunity ResourcesWe have a regular community meeting that is open to all users and developers of every skill level.
Joining themailing listwill automatically send you a meeting invite.
See the notes below for more technical information on joining the meeting.Community Meeting VideosCommunity Meeting Notes ArchiveUpcoming Community EventsCloud Custodian Annual Report 2021- Annual health check provided to the CNCF outlining the health of the projectAdditional ToolsThe Custodian project also develops and maintains a suite of additional
tools herehttps://github.com/cloud-custodian/cloud-custodian/tree/master/tools:Org:Multi-account policy execution.ShiftLeft:Shift Left ~ run policies against Infrastructure as Code assets like terraform.PolicyStream:Git history as stream of logical policy changes.Salactus:Scale out s3 scanning.Mailer:A reference implementation of sending messages to users to notify them.Trail Creator:Retroactive tagging of resources creators from CloudTrailTrailDB:Cloudtrail indexing and time series generation for dashboarding.LogExporter:Cloud watch log exporting to s3Cask:Easy custodian exec via dockerGuardian:Automated multi-account Guard Duty setupOmni SSM:EC2 Systems Manager AutomationMugc:A utility used to clean up Cloud Custodian Lambda policies that are deployed in an AWS environment.ContributingSeehttps://cloudcustodian.io/docs/contribute.htmlSecurityIf you've found a security related issue, a vulnerability, or a
potential vulnerability in Cloud Custodian please let the CloudCustodian Security Teamknow with
the details of the vulnerability. We'll send a confirmation email to
acknowledge your report, and we'll send an additional email when we've
identified the issue positively or negatively.Code of ConductThis project adheres to theCNCF Code of ConductBy participating, you are expected to honor this code.