Actions Supported by Policy-based Authorization
This section describes the actions, resources, and conditions supported by MRS in policy-based authorization.
Actions
MRS provides system-defined policies that can be directly used in IAM. You can also create custom policies to supplement system-defined policies for more refined access control. Operations supported by policies are specific to APIs. The following are common concepts related to policies:
- Permissions: statements in a policy that allow or deny certain operations.
- APIs: REST APIs that can be called by a user who has been granted specific permissions.
- Actions: specific operations that are allowed or denied in a custom policy.
- Dependencies: actions which a specific action depends on. When allowing an action for a user, you also need to allow any existing action dependencies for that user.
- IAM projects/Enterprise projects: the authorization scope of a custom policy. A custom policy can be applied to IAM projects or enterprise projects or both. Policies that contain actions for both IAM and enterprise projects can be used and applied for both IAM and Enterprise Management. Policies that contain actions only for IAM projects can be used and applied to IAM only. Administrators can check whether an action supports IAM projects or enterprise projects in the action list. For details about the differences between IAM and enterprise management, see Differences Between IAM and Enterprise Management
The following table lists the actions that you can define in policy statements for MRS.
Permission | API | Action | IAM Project (Project) | Enterprise Project (Enterprise Project) |
|---|---|---|---|---|
Creating a cluster and executing a job (V1) | POST /v1.1/{project_id}/run-job-flow | mrs:cluster:create | √ | √ |
Creating a cluster (V2) | POST/v2/{project_id}/clusters | √ | √ | |
Querying a cluster list (V1) | GET /v1.1/{project_id}/cluster_infos | mrs:cluster:list | √ | √ |
Obtaining a cluster list (v2) (cluster details can be included) | GET/v2/{project_id}/clusters | √ | √ | |
Deleting a cluster | DELETE /v1.1/{project_id}/clusters/{cluster_id} | mrs:cluster:delete | √ | √ |
Querying a host list (V1) | GET /v1.1/{project_id}/clusters/{cluster_id}/hosts | mrs:host:list | √ | √ |
Querying a file list (V2) | GET/v2/{project_id}/clusters/{cluster_id}/files | mrs:file:list | √ | √ |
Adding and executing a job (V1) | POST /v1.1/{project_id}/jobs/submit-job | mrs:job:submit | √ | √ |
Adding and executing a job (V2) | POST /v2/{project_id}/clusters/{cluster_id}/job-executions | √ | √ | |
Querying the exe object list of jobs (V1) | GET /v1.1/{project_id}/job-exes | mrs:job:list | √ | √ |
Querying information about a job (V2) | GET /v2/{project_id}/clusters/{cluster_id}/job-executions/{job_execution_id} | √ | √ | |
Querying a list of jobs (V2) | GET /v2/{project_id}/clusters/{cluster_id}/job-executions | √ | √ | |
Obtaining the SQL result (V2) | GET /v2/{project_id}/clusters/{cluster_id}/job-executions/{job_execution_id}/sql-result | √ | √ | |
Querying exe object details (V1) | GET /v1.1/{project_id}/job-exes/{job_exe_id} | mrs:job:get | √ | √ |
Querying user agent information | GET/v2/{project_id}/clusters/{cluster_id}/agency-mapping | √ | √ | |
Querying job log details | GET/v2/{project_id}/clusters/{cluster_id}/job-executions/{job_execution_id}/log-detail | √ | √ | |
Querying tags of a specified cluster | GET /v1.1/{project_id}/clusters/{cluster_id}/tags | mrs:tag:list | √ | √ |
Querying all tags | GET /v1.1/{project_id}/clusters/tags | √ | √ | |
Creating a tag for a cluster | POST/v1.1/{project_id}/clusters/{cluster_id}/tags | mrs:tag:create | √ | √ |
Adding or deleting cluster tags in batches | POST /v1.1/{project_id}/clusters/{cluster_id}/tags/action | mrs:tag:batchOperate | √ | √ |
Querying a list of clusters with specified tags | POST /v1.1/{project_id}/clusters/resource_instances/action | mrs:tag:listResource | √ | × |
Terminating a Job (V2) | POST /v2/{project_id}/clusters/{cluster_id}/job-executions/{job_execution_id}/kill | mrs:job:stop | √ | √ |
Deleting jobs in batches (V2) | POST /v2/{project_id}/clusters/{cluster_id}/job-executions/batch-delete | mrs:job:batchDelete | √ | √ |
Canceling SQL execution | POST/v2/{project_id}/clusters/{cluster_id}/sql-execution/{sql_id}/cancel | mrs:sql:cancel | √ | √ |
Submitting a SQL statement | POST/v2/{project_id}/clusters/{cluster_id}/sql-execution | mrs:sql:execute | √ | √ |
Obtaining all auto scaling policies | GET/v2/{project_id}/autoscaling-policy/{cluster_id} | mrs:cluster:policy | √ | √ |
Configuring an auto scaling rule | POST /v1.1/{project_id}/autoscaling-policy/{cluster_id} | √ | √ | |
Updating user agent information | PUT/v2/{project_id}/clusters/{cluster_id}/agency-mapping | mrs:cluster:syncUser | √ | √ |
Obtaining job execution results | GET/v2/{project_id}/clusters/{cluster_id}/sql-execution/{sql_id} | mrs:sql:get | √ | √ |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
