Help Center/ CodeArts Check/ API Reference/ Appendixes/ Actions Supported by Identity Policy-based Authorization

Updated on 2026-02-03 GMT+08:00

View PDF

Actions Supported by Identity Policy-based Authorization

IAM provides system-defined identity policies to define typical cloud service permissions. You can also create custom identity policies using the actions supported by cloud services for more refined access control.

In addition to IAM, the Organizations service also provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to an entity. They only set the permissions boundary for the entity. When SCPs are attached to an organizational unit (OU) or a member account, the SCPs do not directly grant permissions to that OU or member account. Instead, the SCPs only determine what permissions are available for that member account or those member accounts under that OU. The granted permissions can be applied only if they are allowed by the SCPs.

To learn more about how IAM is different from Organizations for access control, see How IAM Is Different from Organizations for Access Control?

This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.

For details about how to use these elements to edit an IAM custom identity policy, see Creating a Custom Identity Policy.
For details about how to use these elements to edit a custom SCP, see Creating an SCP.

Actions

Actions are specific operations that are allowed or denied in an identity policy.

The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
The Resource Type column indicates whether the action supports resource-level permissions.
- You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
- If this column includes a resource type, you must specify the URN in the Resource element of your identity policy statements.
- Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.
For details about the resource types defined by CodeArts Check, see Resources.
The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
- If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
- If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
- If the Condition Key column is empty (-) for an action, the action does not support any condition keys.
For details about the condition keys defined by CodeArts Check, see Conditions.
The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.

The following table lists the actions that you can define in identity policy statements for CodeArts Check.

**Table 1** Actions supported by CodeArts Check
Action	Description	Access Level	Resource Type (*: required)	Condition Key	Alias
codeartscheck:task:create	Grants permission to create a codearts check task.	Write	task *	-	-
codeartscheck:task:create	Grants permission to create a codearts check task.	Write	-	codeartscheck:ProjectId	-
codeartscheck:task:update	Grants permission to update a codearts check task.	Write	task *	-	-
codeartscheck:task:update	Grants permission to update a codearts check task.	Write	-	codeartscheck:ProjectId	-
codeartscheck:task:delete	Grants permission to delete a codearts check task.	Write	task *	-	-
codeartscheck:task:delete	Grants permission to delete a codearts check task.	Write	-	codeartscheck:ProjectId	-
codeartscheck:task:get	Grants permission to get a codearts check task.	Read	task *	-	-
codeartscheck:task:get	Grants permission to get a codearts check task.	Read	-	codeartscheck:ProjectId	-
codeartscheck:task:execute	Grants permission to execute a codearts check task.	Write	task *	-	-
codeartscheck:task:execute	Grants permission to execute a codearts check task.	Write	-	codeartscheck:ProjectId	-
codeartscheck:task:list	Grants permission to list codearts check project tasks.	List	task *	-	-
codeartscheck:task:list	Grants permission to list codearts check project tasks.	List	-	codeartscheck:ProjectId	-
codeartscheck::listAllTasks	Grants permission to list all codearts check tasks.	List	-	-	-
codeartscheck:task:getReport	Grants permission to get a codearts check task report.	Read	task *	-	-
codeartscheck:task:getReport	Grants permission to get a codearts check task report.	Read	-	codeartscheck:ProjectId	-
codeartscheck:task:updateReportStatus	Grants permission to update a codearts check task report status.	Write	task *	-	-
codeartscheck:task:updateReportStatus		Write	-	codeartscheck:ProjectId	-
codeartscheck::createRuleSet	Grants permission to create a ruleset.	Write	-	-	-
codeartscheck::updateRuleSet	Grants permission to update a ruleset.	Write	-	-	-
codeartscheck::deleteRuleSet	Grants permission to delete a ruleset.	Write	-	-	-
codeartscheck::getRuleSet	Grants permission to view a ruleset.	Read	-	-	-
codeartscheck::listRuleSets	Grants permission to view the ruleset list.	List	-	-	-
codeartscheck::setDefaultRuleSet	Grants permission to set a project default ruleset.	Write	-	codeartscheck:ProjectId	-
codeartscheck::createRule	Grants permission to create the custom rule.	Write	-	-	-
codeartscheck::updateRule	Grants permission to update the custom rule.	Write	-	-	-
codeartscheck::getRule	Grants permission to get rule.	Read	-	-	-
codeartscheck::deleteRule	Grants permission to delete custom rule.	Write	-	-	-
codeartscheck::listRules	Grants permission to list rules.	List	-	-	-
codeartscheck::getModelSet	Grants permission to get model-set.	Read	-	-	-
codeartscheck::createModelSet	Grants permission to create the model-set.	Write	-	-	-
codeartscheck::updateModelSet	Grants permission to update the model-set.	Write	-	-	-
codeartscheck::deleteModelSet	Grants permission to delete the model-set.	Write	-	-	-
codeartscheck::getModel	Grants permission to get model.	Read	-	-	-
codeartscheck::createModel	Grants permission to create the model.	Write	-	-	-
codeartscheck::updateModel	Grants permission to update the model.	Write	-	-	-
codeartscheck::deleteModel	Grants permission to delete the model-set.	Write	-	-	-
codeartscheck::getProjectConfig	Grants permission to get project config.	Read	-	codeartscheck:ProjectId	-
codeartscheck::updateProjectConfig	Grants permission to update project config.	Write	-	codeartscheck:ProjectId	-
codeartscheck::getConfig	Grants permission to get tenant config.	Read	-	-	-
codeartscheck::updateConfig	Grants permission to update tenant config.	Write	-	-	-

Each API of CodeArts Check usually supports one or more actions. Table 2 lists the supported actions and dependencies.

**Table 2** Actions and dependencies supported by CodeArts Check APIs
API	Action	Dependencies
GET /v2/{project_id}/tasks/{task_id}/ruleset/{ruleset_id}/check-parameters	codeartscheck:task:get	-
GET /v3/{project_id}/tasks/{task_id}/ruleset/{ruleset_id}/check-parameters	codeartscheck:task:get	-
DELETE /v2/tasks/{task_id}	codeartscheck:task:delete	-
POST /v2/{project_id}/tasks/{task_id}/config-parameters	codeartscheck:task:update	-
GET /v2/{project_id}/tasks/{task_id}/rulesets	codeartscheck:task:get	-
GET /v2/{project_id}/tasks/{task_id}/log-detail	codeartscheck:task:get	-
GET /v2/{project_id}/tasks/{task_id}/listpathtree	codeartscheck:task:get	-
GET /v2/{project_id}/tasks/{task_id}/settings	codeartscheck:task:get	-
GET /v3/{project_id}/tasks/{task_id}/rulesets	codeartscheck:task:get	-
POST /v2/{project_id}/tasks/{task_id}/config-ignorepath	codeartscheck:task:update	-
PUT /v2/tasks/{task_id}/ruleset	codeartscheck:task:update	-
POST /v2/{project_id}/tasks/{task_id}/settings	codeartscheck:task:update	-
GET /v1/tasks/{task_id}/resource-pool	codeartscheck:task:get	-
PUT /v1/tasks/{task_id}/resource-pool	codeartscheck:task:update	-
GET /v4/tasks/{task_id}/jobs	codeartscheck:task:get	-
PUT /v2/pipeline-task/{task_id}	codeartscheck:task:update	-
GET /v1/task/notification/{task_id}	codeartscheck:task:get	-
GET /v1/tasks/code-sum-measures	codeartscheck::listAllTasks	-
GET /v4/task/{task_id}/code-health-svg	codeartscheck:task:get	-
GET /v4/tasks/{task_id}/all-files	codeartscheck:task:get	-
GET /v4/tasks/{task_id}/file-list	codeartscheck:task:get	-
GET /v1/tasks/{task_id}/owner-matching-switch	codeartscheck:task:get	-
PUT /v1/tasks/{task_id}/owner-matching-switch	codeartscheck:task:update	-
PUT /v1/tasks/{task_id}/stop	codeartscheck:task:execute	-
GET /v4/tasks/{task_id}/task-webhook-info	codeartscheck:task:get	-
GET /v4/tasks/{task_id}/branches	codeartscheck:task:get	-
GET /v1/tasks/{task_id}/detect-language	codeartscheck:task:get	-
GET /v4/projects/{project_id}/task-groups	codeartscheck:task:list	-
GET /v1/vpcep-authorization	codeartscheck:task:get	-
GET /v1/tasks/{task_id}/taskcron	codeartscheck:task:get	-
GET /v4/codehub/repo-list	codeartscheck:task:get	-
PUT /v1/jobs/{job_id}/result/refresh	codeartscheck:task:getReport	-
GET /v4/template-tasks	codeartscheck:task:list	-
GET /v4/tasks/{task_id}/last-jobs	codeartscheck:task:get	-
GET /v1/tasks/{task_id}/pre-check-script	codeartscheck:task:get	-
GET /v1/tasks	codeartscheck:task:list	-
PUT /v4/tasks/{task_id}/webhook	codeartscheck:task:update	-
PUT /v1/task/code-gate	codeartscheck:task:update	-
PUT /v4/task/{task_id}/ignore-files	codeartscheck:task:update	-
PUT /v1/task/check-mode	codeartscheck:task:update	-
DELETE /v3/task/{task_id}	codeartscheck:task:delete	-
GET /v3/task/{task_id}	codeartscheck:task:get	-
POST /v1/jobs	codeartscheck:task:execute	-
POST /v4/tasks/{task_id}/batch/async-copy	codeartscheck:task:create	-
GET /v4/task/{task_id}/check-list	codeartscheck:task:get	-
POST /v3/task	codeartscheck:task:create	-
GET /v2/plugins	codeartscheck:task:get	-
GET /v2/transmission/notification	codeartscheck::getProjectConfig	-
GET /v2/transmission/review-data	codeartscheck::getProjectConfig	-
GET /v1/simple-query/{id}	codeartscheck::getProjectConfig	-
POST /v2/{project_id}/task	codeartscheck:task:create	-
GET /v2/{project_id}/tasks	codeartscheck:task:get	-
POST /v2/tasks/{task_id}/run	codeartscheck:task:execute	-
POST /v2/tasks/{task_id}/stop	codeartscheck:task:execute	-
GET /v2/tasks/{task_id}/progress	codeartscheck:task:get	-
GET /v3/{project_id}/tasks/{task_id}/branches	codeartscheck:task:get	-
GET /v2/{domain_id}/checkers-version	codeartscheck::getConfig	-
GET /v2/{project_id}/tasks/{task_id}/metrics-summary	codeartscheck:task:getReport	-
GET /v2/tasks/{task_id}/defects-detail	codeartscheck:task:getReport	-
GET /v2/tasks/{task_id}/defects-statistic	codeartscheck:task:getReport	-
GET /v2/tasks/{task_id}/defects-summary	codeartscheck:task:getReport	-
PUT /v2/tasks/{task_id}/defect-status	codeartscheck:task:updateReportStatus	-
GET /v2/{project_id}/tasks/{task_id}/checkrecord	codeartscheck:task:getReport	-
POST /v2/ruleset	codeartscheck::createRuleSet	-
DELETE /v2/{project_id}/ruleset/{ruleset_id}	codeartscheck::deleteRuleSet	-
GET /v2/{project_id}/rulesets	codeartscheck::listRuleSets	-
GET /v2/rules	codeartscheck::listRules	-
GET /v2/{project_id}/ruleset/{ruleset_id}/rules	codeartscheck::getRuleSet	-
POST /v2/{project_id}/ruleset/{ruleset_id}/{language}/default	codeartscheck::setDefaultRuleSet	-
GET /v3/{project_id}/rulesets	codeartscheck::listRuleSets	-
PUT /v1/tasks/{task_id}/pdf-async-job	codeartscheck:task:getReport	-
GET /v1/tasks/{task_id}/async-job/{async_job_id}	codeartscheck:task:getReport	-
GET /v2/async-job	codeartscheck:task:getReport	-
GET /v1/tasks/{task_id}/pdf-file	codeartscheck:task:getReport	-
POST /v1/defect/issue-status	codeartscheck:task:updateReportStatus	-
POST /v1/defect/issue-list-by-filter	codeartscheck:task:getReport	-
POST /v1/defect/issue-filter	codeartscheck:task:getReport	-
GET /v1/defects/task-statistics	codeartscheck:task:getReport	-
GET /v1/history/defect-metric-trend	codeartscheck:task:getReport	-
GET /v1/defect	codeartscheck:task:getReport	-
POST /v1/measure/measure-total	codeartscheck:task:getReport	-
GET /v1/defects/task-measures	codeartscheck:task:getReport	-
GET /v1/tasks/{task_id}/measure-list	codeartscheck:task:getReport	-
GET /v1/tasks/{task_id}/related-duplicate-blocks	codeartscheck:task:getReport	-
POST /v2/measure/measure-list	codeartscheck:task:getReport	-
POST /v1/measure/measure-duplication-info	codeartscheck:task:getReport	-
POST /v2/related-duplicate-blocks	codeartscheck:task:getReport	-
PUT /v1/defects/file-content	codeartscheck:task:getReport	-
GET /v1/defects/file-content	codeartscheck:task:getReport	-
POST /v1/defects/assistant-analysis/task-summary	codeartscheck:task:getReport	-
GET /v1/criterionset/get-default-sets	codeartscheck:getProjectConfig	-
GET /v1/criterionsets/language	codeartscheck::listRuleSets	-
GET /v1/rule/criterion-rule/query/{criterion_rule_id}	codeartscheck::getRule	-
POST /v1/config-items	codeartscheck::getRuleSet	-
POST /v1/config-items	codeartscheck::getRuleSet	-
POST /v1/criterionsets/batch	codeartscheck::listRuleSets	-
GET /v2/excute/all-thirdtools	codeartscheck::getRule	-
GET /v1/criterionsets/{set_id}	codeartscheck::getRuleSet	-
GET /v2/all-criterionsets	codeartscheck::listRuleSets	-
GET /v1/criterion-filters	codeartscheck::listRules	-
GET /v2/criterions	codeartscheck::listRules	-
POST /v1/relations	codeartscheck::updateRuleSet	-
GET /v1/console-log	codeartscheck:task:get	-
GET /v1/log-file	codeartscheck:task:get	-

Resources

A resource type indicates the resources that an identity policy applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the identity policy applies to all resources. You can also set condition keys in an identity policy to define resource types.

The following table lists the resource types that you can define in identity policy statements for CodeArts Check.

**Table 3** Resource types supported by CodeArts Check
Resource Type	URN
task	codeartscheck:<region>:<account-id>:task:<task-id>

Conditions

Condition Key Overview

A Condition element lets you specify conditions for when an identity policy is in effect. It contains condition keys and operators.

The condition key that you specify can be a global condition key or a service-specific condition key.
- Global condition keys (with the g: prefix) apply to all actions. Cloud services do not need to provide user identity information. Instead, the system automatically obtains such information and authenticates users. For details, see Global Condition Keys.
- Service-specific condition keys (with the abbreviation of a service name plus a colon as the prefix, for example, codearts check) apply only to operations of the xx service. For details, see Table 4.
- The number of values associated with a condition key in the request context of an API call makes the condition key single-valued or multivalued. Single-valued condition keys have at most one value in the request context of an API call. Multivalued condition keys can have multiple values in the request context of an API call. For example, a request can originate from at most one VPC endpoint, so g:SourceVpce is a single-valued condition key. You can tag resources and include multiple tag key-value pairs in a request, so g:TagKeys is a multivalued condition key.
A condition operator, condition key, and a condition value together constitute a complete condition statement. An identity policy can be applied only when its request conditions are met. For supported condition operators, see operators.

Service-specific condition keys supported by CodeArts Check

The following table lists the condition keys that you can define in identity policies for CodeArts Check. You can include these condition keys to specify conditions for when your identity policy is in effect.