Help Center/ Cloud Trace Service/ User Guide/ Using IAM to Grant Access to CTS/ Using IAM Roles or Policies to Grant Access to CTS
Updated on 2025-12-31 GMT+08:00

Using IAM Roles or Policies to Grant Access to CTS

System-defined permissions in Role/Policy-based Authorization provided by Identity and Access Management (IAM) let you control access to CTS. With IAM, you can:

  • Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing CTS resources.
  • Grant users only the permissions required to perform a given task based on their job responsibilities.
  • Entrust a Huawei Cloud account or a cloud service to perform efficient O&M on your CTS resources.

If your Huawei Cloud account meets your permissions requirements, you can skip this section.

Figure 1 shows the process flow of role/policy-based authorization.

Prerequisites

Before granting permissions to user groups, learn about system-defined permissions in Role/Policy-based Authorization for CTS. To grant permissions for other services, learn about all system-defined permissions supported by IAM.

Process Flow

Figure 1 Process of granting CTS permissions using role/policy-based authorization
  1. On the IAM console, create a user group and grant it permissions (CTS ReadOnlyAccess as an example).

    Create a user group on the IAM console and assign the CTS ReadOnlyAccess permission to the group.

  2. Create an IAM user and add it to the created user group.

    On the IAM console, create a user and add it to the user group created in 1.

  3. Log in as the IAM user and verify permissions.

    In the authorized region, perform the following operations:

    • Choose Service List > Cloud Trace Service. Then click Enable CTS on the CTS console. If a message appears indicating that you have insufficient permissions to perform the operation, the CTS ReadOnlyAccess policy is in effect.
    • Choose another service from Service List. If a message appears indicating that you have insufficient permissions to access the service, the CTS ReadOnlyAccess policy is in effect.

Example Custom Policies

You can create custom policies to supplement the system-defined policies of CTS. For details about actions supported in custom policies, see Actions Supported by Policy-based Authorization.

To create a custom policy, choose either visual editor or JSON.

  • Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy grammar.
  • JSON: Create a JSON policy or edit an existing one.

For details, see Creating a Custom Policy. The following lists examples of common CTS custom policies.

  • Example 1: Grant permission to query audit traces.
    {
        "Version": "1.1",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": [
                    "
                         cts:trace:list
                         cts:trace:listResource
                         cts:trace:listTraceUser
                     "
                ]
            }
        ]
    }
  • Example 2: Grant permission to deny tracker deletion.

    A policy with only "Deny" permissions must be used together with other policies. If the permissions granted to an IAM user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

    Assume that you want to grant the permissions of the CTS Administrator policy to a user but want to prevent them from deleting key event notifications. You can create a custom policy for denying key event notification deletion, and attach this policy together with the CTS Administrator policy to the user. As an explicit deny in any policy overrides any allows, the user can perform all operations on CTS except deleting key event notifications. Example policy denying key event notification deletion:

    {
            "Version": "1.1",
            "Statement": [
                    {
                            "Action": [
                                    "cts:*:*"
                            ],
                            "Effect": "Allow"
                    },
                    {
                            "Action": [
                                    "cts:notification:delete"
                            ],
                            "Effect": "Deny"
                    }
            ]
    }
  • Example 3: Create a custom policy containing multiple actions.

    A custom policy can contain the actions of one or multiple services that are of the same type (global or project-level). Example policy containing multiple actions:

    { 
            "Version": "1.1", 
            "Statement": [ 
                    { 
                            "Action": [ 
                                    "cts:quota:get", 
                                    "cts:notification:create", 
                                    "cts:notification:delete",
                                    "ecs:cloudServers:delete"
                                    "ims:images:list"
                                    "ims:serverImages:create"
                            ], 
                            "Effect": "Allow" 
                    } 
            ] 
    }