Resource Types Supported by COC

A resource is an object that is contained in a service. Table 1 lists the resources supported by COC. You can specify resource paths to select specific resources when creating a custom policy.

**Table 1** COC resources and their paths
Resource Type	Resource Name	Path
instance	ECS	Format: *ecs:::instance:*ECS instance ID [Description] For ECS resources, IAM automatically generates the prefix *ecs:::instance:* of the resource path. You can use ECS ID to specify a resource path. Wildcards () are supported. The following is an example: ecs:::instance: indicates any ECS ID.
	BMSs	Format: *bms:::instance:*BMS ID [Description] For BMS resources, IAM automatically generates the prefix *bms:::instance:* of the resource path. You can use a BMS instance ID to specify the resource path. The wildcard () is supported. The following is an example: bms:::instance: indicates any BMS ID.
	GaussDB instance	Format: *GaussDB:::instance:*GaussDB instance ID [Description] For GaussDB instance resources, IAM automatically generates the prefix (gaussdb:::instance:) of the resource path. GaussDB instance ID can be used to specify a resource path. The wildcard () is supported. The following is an example: gaussdb:::instance: indicates any GaussDB instance ID.
	RDS instance	Format: *rds:::instance:*RDS instance ID [Description] For RDS instance resources, IAM automatically generates the prefix (*rds:::instance:) of the resource path. You can use an RDS instance ID to specify the resource path. The wildcard () is supported. The following is an example: rds:::instance:* indicates any RDS DB instance ID.
document	Document	Format: *coc:::document:*document name [Description] For document resources, IAM automatically generates the resource path prefix *coc:::document:. You can use a document name to specify the resource path. The wildcard () is supported. The following is an example: coc:::document:* indicates any document.
application	Application	Format: *coc:::application:*application code [Description] For application resources, IAM automatically generates the resource path prefix *coc:::application:. You can use an application code to specify the resource path. The wildcard () is supported. The following is an example: coc:::application:* indicates any application.
resourceView	Resource views	Format: *coc:::resourceView:*application code [Description] For resource view resources, IAM automatically generates the resource path prefix *coc:::resourceView:. You can use a resource view ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::resourceView:* indicates any resource view.
schedule	Scheduled O&M	Format: *coc:::schedule:*scheduled task ID [Description] For scheduled O&M resources, IAM automatically generates the resource path prefix *coc:::schedule. You can use a scheduled task ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::schedule:* indicates any scheduled O&M.
job	Task	Format: *coc:::job:*task ID [Description] For task resources, IAM automatically generates the resource path prefix *coc:::job:. You can use a task ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::job:* indicates any task.
faultMode	Fault modes	Format: *coc:::faultMode:*failure mode ID [Description] For failure mode resources, IAM automatically generates the resource path prefix *coc:::faultMode:. Use a failure mode ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::faultMode:* indicates any failure mode.
contingencyPlan	Contingency plans	Format: *coc:::contingencyPlan:*contingency plan ID [Description] For contingency plan resources, IAM automatically generates the resource path prefix *coc:::schedule:. You can use a contingency plan ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::schedule:* indicates any contingency plan.
attackTask	Attack task	Format: *coc:::attackTask:*attack task name [Description] For attack task resources, IAM automatically generates the resource path prefix coc:::attackTask:. You can use an attack task name to specify the resource path. The wildcard () is supported. The following is an example: coc:::attackTask: indicates any attack task.
attackRecord	Attack record	Format: *coc:::attackRecord:*attack record ID [Description] For attack record resources, IAM automatically generates the resource path prefix *coc:::attackRecord:. You can use an attack record ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::attackRecord:* indicates any attack record.
drillTask	Drill task	Format: *coc:::drillTask:*drill task ID [Description] For drill task resources, IAM automatically generates the resource path prefix *coc:::drillTask:. You can use a drill task ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::drillTask:* indicates any drill task.
attackTargetRecord	Attack target record of an attack task	Format: *coc:::attackTargetRecord:* attack target record ID of an attack task [Description] For the attack target record resource of an attack task, IAM automatically generates the resource path prefix *coc:::attackTargetRecord:. You can use an attack target record ID of an attack task to specify a resource path. The wildcard () is supported. The following is an example: coc:::attackTargetRecord:* indicates the attack target record of any attack task.
drillRecord	Drill record	Format: *coc:::drillRecord:*drill record ID [Description] For drill record resources, IAM automatically generates the resource path prefix *coc:::drillRecord:. You can use a drill record ID to specify a resource path. The wildcard () is supported. The following is an example: coc:::drillRecord:* indicates any drill record.
drillPlan	Drill plans	Format: *coc:::drillPlan: drill plan ID* [Description] For drill plan resources, IAM automatically generates the resource path prefix *coc:::drillPlan:. You can use a drill plan ID to specify a resource path. The wildcard () is supported. The following is an example: coc:::drillPlan:* indicates any drill plan.
slaTemplate	SLA templates	Format: *coc:::slaTemplate:*SLA template ID [Description] For SLA template resources, IAM automatically generates the resource path prefix *coc:::slaTemplate:. You can use an SLA template ID to specify the resource path. The wildcard () is supported. The following is an example: In the preceding command, coc:::slaTemplate:* indicates any SLA template.
parameter	Configuration item	Format: *coc:::parameter:*configuration item name. [Description] For configuration item resources, IAM automatically generates the resource path prefix *coc:::parameter:. You can use a configuration item name to specify the resource path. The wildcard () is supported. The following is an example: coc:::parameter:* indicates any configuration item.
accountBaseline	Account baselines	Format: *coc:::accountBaseline:*account baseline ID [Description] For account baseline resources, IAM automatically generates the resource path prefix *coc:::accountBaseline:. You can use an account baseline ID to specify a resource path. The wildcard () is supported. The following is an example: coc:::accountBaseline:* indicates any account baseline.
provisionedProduct	Product instances	Format: *coc:::provisionedProduct:*product instance ID [Description] For product instance resources, IAM automatically generates the resource path prefix *coc:::provisionedProduct:. You can use a product instance ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::provisionedProduct:* indicates any product instance.
product	Product	Format: *coc:::product:*product ID [Description] For product resources, IAM automatically generates the prefix *coc:::product:* of the resource path. You can use a product ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::product: indicates any product.
portfolio	Product portfolio	Format: *coc:::portfolio:*product portfolio ID [Description] For product portfolio resources, IAM automatically generates the resource path prefix *coc:::portfolio:. You can use a product portfolio ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::portfolio:* indicates any product combination.
sloDiagram	SLO architecture design diagram	Format: *coc:::sloDiagram:*SLO architecture design diagram ID [Description] For SLO architecture design diagram resources, IAM automatically generates the resource path prefix *coc:::sloDiagram:. You can use an SLO architecture design diagram ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::sloDiagram:* indicates any SLO architecture design diagram.
template	Template	Format: *coc:::template:*template ID [Description] For template resources, IAM automatically generates the resource path prefix *coc:::template:. You can use a template ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::template:* indicates any template.
templateInstance	Template instance	Format: *coc:::templateInstance:*template instance ID [Description] For template instance resources, IAM automatically generates the prefix *coc:::templateInstance:* of the resource path. You can use a template instance ID to specify the resource path. The wildcard () is supported. The following is an example: coc:::templateInstance: indicates any chart instance.