Help Center/ Cloud Trace Service/ API Reference (Kuala Lumpur Region)/ Permissions Policies and Supported Actions
Updated on 2022-08-17 GMT+08:00

Permissions Policies and Supported Actions

This section describes fine-grained permissions management for your CTS. If your account does not require individual IAM users, you can skip this section.

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

You can grant users permissions by using and policies. Roles are a type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.

Policy-based authorization is useful if you want to allow or deny the access to an API.

An account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user wants to query metrics using an API, the user must have been granted permissions that allow the aom:metric:get action.

Supported Actions

CTS provides system-defined policies that can be directly used in IAM. You can also create custom policies and use them to supplement system-defined policies, implementing more refined access control. Operations supported by policies are specific to APIs. The following are common concepts related to policies:

  • Permissions: Defined by actions in a custom policy.
  • APIs: REST APIs that can be called by a user who has been granted specific permissions.
  • Actions: Specific operations that are allowed or denied.
  • Related actions: Actions on which a specific action depends to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the related actions.
  • IAM or enterprise projects: Type of projects for which an action will take effect. Policies that contain actions for both IAM and enterprise projects can be used and take effect for both IAM and Enterprise Management. Policies that only contain actions for IAM projects can be used and only take effect for IAM.

The check mark (√) and cross symbol (x) indicate that an action takes effect or does not take effect for the corresponding type of projects.

Permission

API

Action

Related Action

IAM Project

Enterprise Project

Querying a trace list

GET /v3/{project_id}/traces

cts:trace:list

-

x

Querying a tracker

GET /v3/{project_id}/trackers

cts:tracker:list

obs:bucket:GetBucketAcl

obs:bucket:ListAllMyBuckets

x

Creating a tracker

POST /v3/{project_id}/tracker

cts:tracker:create

lts:topics:list

lts:topics:create

lts:groups:list

lts:groups:create

obs:bucket:CreateBucket

obs:bucket:HeadBucket

obs:bucket:GetLifecycleConfiguration

obs:bucket:PutLifecycleConfiguration

obs:bucket:GetBucketAcl

obs:bucket:PutBucketAclkms:cmk:list

x

Modifying a tracker

PUT /v3/{project_id}/tracker

cts:tracker:update

lts:topics:list

lts:topics:create

lts:groups:list

lts:groups:create

obs:bucket:CreateBucket

obs:bucket:HeadBucket

obs:bucket:GetLifecycleConfiguration

obs:bucket:PutLifecycleConfiguration

obs:bucket:GetBucketAcl

obs:bucket:PutBucketAcl

kms:cmk:list

x

Deleting a tracker

DELETE /v3/{project_id}/trackers

cts:tracker:delete

-

x

Querying the tracker quota

GET /v3/{project_id}/quotas

cts:quota:get

-

x