Creates a rule.
Operation Description
This topic provides an example on how to create a managed rule named required-tags. The returned result indicates that the rule is created and the ID of the rule is cr-5772ba41209e007b****
.
Limits
You can use a common account to create up to 200 rules.
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action
policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- The required resource types are displayed in bold characters.
- If the permissions cannot be granted at the resource level,
All Resources
is used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
Operation | Access level | Resource type | Condition key | Association operation |
---|---|---|---|---|
config:CreateConfigRule | Read |
|
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
ConfigRuleName | string | Yes | The name of the rule. | |
Description | string | No | The description of the rule. | |
InputParameters | object | No | The input parameter of the rule. | |
ConfigRuleTriggerTypes | string | Yes | The trigger type of the rule. Valid values:
NoteIf a rule supports the preceding trigger types, separate the types with a comma (,). | ConfigurationItemChangeNotification |
MaximumExecutionFrequency | string | No | The intervals at which the rule is triggered. Valid values:
NoteThis parameter is required if the ConfigRuleTriggerTypes parameter is set to ScheduledNotification. | One_Hour |
ResourceTypesScope | array | Yes | The type of the resource to be evaluated by the rule. Separate multiple resource types with commas (,). | |
string | No | ACS::ECS::Instance | ||
RiskLevel | integer | Yes | The risk level of the resources that are not compliant with the rule. Valid values:
| 1 |
ClientToken | string | No | The client token that you want to use to ensure the idempotency of the request. You can use the client to generate the value, but you must make sure that the value is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length.`` | 1594295238-f9361358-5843-4294-8d30-b5183fac**** |
RegionIdsScope | string | No | The ID of the region to which the rule applies. Separate multiple region IDs with commas (,). NoteThis parameter applies only to managed rules. | cn-hangzhou |
ExcludeResourceIdsScope | string | No | The ID of the resource to be excluded from the compliance evaluations performed by the rule. Separate multiple resource IDs with commas (,). NoteThis parameter applies only to managed rules. | lb-t4nbowvtbkss7t326**** |
ResourceGroupIdsScope | string | No | The ID of the resource group to which the rule applies. Separate multiple resource group IDs with commas (,). NoteThis parameter applies only to managed rules. | rg-aekzc7r7rhx**** |
TagKeyScope | string | No | The tag key used to filter resources. The rule applies only to the resources with a specified tag key. NoteThis parameter applies only to managed rules. You must configure the TagKeyScope and TagValueScope parameters at the same time. | ECS |
TagValueScope | string | No | The tag key used to filter resources. The rule applies only to the resources with the specified tag key. NoteThis parameter applies only to managed rules. You must configure the TagKeyScope and TagValueScope parameters at the same time. | test |
SourceOwner | string | Yes | The type of the rule Valid values:
| ALIYUN |
SourceIdentifier | string | Yes | The ID of the rule.
For more information about how to query the name of a managed rule, see Managed rules. | required-tags |
TagKeyLogicScope | string | No | The logical relationship among the tag keys if you specify multiple tag keys for the
| AND |
For more information about common request parameters, see Common parameters.
Response parameters
Examples
Sample success responses
JSON
format
{
"ConfigRuleId": "cr-5772ba41209e007b****",
"RequestId": "6EC7AED1-172F-42AE-9C12-295BC2ADB751"
}
Error codes
HTTP status code | Error code | Error message | Description |
---|---|---|---|
400 | ExceedMaxRuleCount | The maximum number of rules is exceeded. | The maximum number of rules is exceeded. |
400 | ConfigRuleNotExists | The ConfigRule does not exist. | The rule does not exist. |
400 | ConfigRuleExists | The ConfigRule already exists. | The config rule already exists. |
404 | AccountNotExisted | Your account does not exist. | The specified account does not exist. |
503 | ServiceUnavailable | The request has failed due to a temporary failure of the server. | The request has failed due to a temporary failure of the server. |
For a list of error codes, visit the Service error codes.