This API is still under active development and subject to non-backward compatible changes or removal in any future version. Use of the API is not recommended in production environments. Experimental APIs are not subject to the Semantic Versioning model.
This module is part of the AWS Cloud Development Kit project.
Supported:
- Config rules
Not supported
- Configuration recoder
- Delivery channel
- Aggregation
To set up a managed rule, define a ManagedRule
and specify its identifier:
new ManagedRule(this, 'AccessKeysRotated', {
identifier: 'ACCESS_KEYS_ROTATED'
});
Available identifiers and parameters are listed in the List of AWS Config Managed Rules.
Higher level constructs for managed rules are available, see Managed Rules. Prefer to use those constructs when available (PRs welcome to add more of those).
To set up a custom rule, define a CustomRule
and specify the Lambda Function to run and the trigger types:
new CustomRule(this, 'CustomRule', {
lambdaFunction: myFn,
configurationChanges: true,
periodic: true
});
By default rules are triggered by changes to all resources. Use the scopeToResource()
, scopeToResources()
or scopeToTag()
methods to restrict the scope of both managed and custom rules:
const sshRule = new ManagedRule(this, 'SSH', {
identifier: 'INCOMING_SSH_DISABLED'
});
// Restrict to a specific security group
rule.scopeToResource('AWS::EC2::SecurityGroup', 'sg-1234567890abcdefgh');
const customRule = new CustomRule(this, 'CustomRule', {
lambdaFunction: myFn,
configurationChanges: true
});
// Restrict to a specific tag
customRule.scopeToTag('Cost Center', 'MyApp');
Only one type of scope restriction can be added to a rule (the last call to scopeToXxx()
sets the scope).
To define Amazon CloudWatch event rules, use the onComplianceChange()
or onReEvaluationStatus()
methods:
const rule = new CloudFormationStackDriftDetectionCheck(this, 'Drift');
rule.onComplianceChange('TopicEvent', {
target: new targets.SnsTopic(topic))
});
Creating custom and managed rules with scope restriction and events: