Adds or updates organization config rule for your entire organization evaluating whether your AWS resources comply with your desired configurations. Only a master account can create or update an organization config rule.
configservice_put_organization_config_rule(OrganizationConfigRuleName,
OrganizationManagedRuleMetadata, OrganizationCustomRuleMetadata,
ExcludedAccounts)
[required] The name that you assign to an organization config rule.
An OrganizationManagedRuleMetadata
object.
An OrganizationCustomRuleMetadata
object.
A comma-separated list of accounts that you want to exclude from an organization config rule.
svc$put_organization_config_rule( OrganizationConfigRuleName = "string", OrganizationManagedRuleMetadata = list( Description = "string", RuleIdentifier = "string", InputParameters = "string", MaximumExecutionFrequency = "One_Hour"|"Three_Hours"|"Six_Hours"|"Twelve_Hours"|"TwentyFour_Hours", ResourceTypesScope = list( "string" ), ResourceIdScope = "string", TagKeyScope = "string", TagValueScope = "string" ), OrganizationCustomRuleMetadata = list( Description = "string", LambdaFunctionArn = "string", OrganizationConfigRuleTriggerTypes = list( "ConfigurationItemChangeNotification"|"OversizedConfigurationItemChangeNotification"|"ScheduledNotification" ), InputParameters = "string", MaximumExecutionFrequency = "One_Hour"|"Three_Hours"|"Six_Hours"|"Twelve_Hours"|"TwentyFour_Hours", ResourceTypesScope = list( "string" ), ResourceIdScope = "string", TagKeyScope = "string", TagValueScope = "string" ), ExcludedAccounts = list( "string" ) )
This API enables organization service access through the
EnableAWSServiceAccess
action and creates a service linked role
AWSServiceRoleForConfigMultiAccountSetup
in the master account of your
organization. The service linked role is created only when the role does
not exist in the master account. AWS Config verifies the existence of
role with GetRole
action.
You can use this action to create both custom AWS Config rules and AWS
managed Config rules. If you are adding a new custom AWS Config rule,
you must first create AWS Lambda function in the master account that the
rule invokes to evaluate your resources. When you use the
PutOrganizationConfigRule
action to add the rule to AWS Config, you
must specify the Amazon Resource Name (ARN) that AWS Lambda assigns to
the function. If you are adding an AWS managed Config rule, specify the
rule\'s identifier for the RuleIdentifier
key.
The maximum number of organization config rules that AWS Config supports is 150.
Specify either OrganizationCustomRuleMetadata
or
OrganizationManagedRuleMetadata
.