If the resource has all the specified tags, the evaluation result is Compliant.
Scenarios
An enterprise may require that cloud resources have specific tags, which can facilitate resource management in scenarios like permission isolation, expense splitting, and automatic O&M.
Risk level
Default risk level: high.
When you apply this rule, you can change the risk level based on your business requirements.
Compliance evaluation logic
- If the resource has all the specified tags, the evaluation result is Compliant.
- If the resource does not have all the specified tags, the evaluation result is Incompliant. For more information about how to remediate an incompliant configuration, see the "Incompliance remediation" section of this topic.
Rule details
Item | Description |
---|---|
Rule name | contains-all-tag |
Rule identifier | contains-all-tag |
Tag | Tag |
Automatic remediation | Not supported |
Trigger type | Configuration change |
Supported resource type |
|
Input parameter |
Note You can define up to six tags. Each tag must contain a key and a value. The keys and values are case-sensitive. You can use asterisks ( * ) and question marks (? ) as wildcard characters. Only a single tag key can be specified for each tag, but multiple tag values can be specified for a single tag. Separate multiple tag values with commas (,). The system considers it a match if the resource has one of the values corresponding to a key that has multiple values. |
Incompliance remediation
Attach all the specified tags to the resource. For more information, see Add a custom tag.