Help Center/ Organizations/ User Guide/ Managing SCPs/ Actions Supported by SCP-based Authorization/ Management & Governance/ Cloud Trace Service (CTS)
Updated on 2024-09-26 GMT+08:00
View PDF
Share

Cloud Trace Service (CTS)

The Organizations service 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.

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

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 SCP.

  • 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 SCP.
  • 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 SCP 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 cts, see Resources.

  • The Condition Key column contains keys that you can specify in the Condition element of an SCP 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 cts, see Conditions.

The following table lists the actions that you can define in SCP statements for cts.

Table 1 Actions supported by CTS

Action

Description

Access Level

Resource Type (*: required)

Condition Key

cts:trace:list

Grants permission to query audit traces.

list

-

-

cts:tracker:create

Grants permission to create a tracker.

write

-

-

cts:tracker:list

Grants permission to query trackers.

list

-

-

cts:tracker:update

Grants permission to update a tracker.

write

cts:<region>:<account-id>:tracker:<tracker-id>

-

cts:tracker:delete

Grants permission to delete a tracker.

write

cts:<region>:<account-id>:tracker:<tracker-id>

-

cts:quota:get

Grants permission to query tracker quotas.

read

-

-

cts:notification:create

Grants permission to create a notification rule.

write

-

-

cts:notification:update

Grants permission to update a key event notification.

write

cts:<region>:<account-id>:notification:<notification-id>

-

cts:notification:list

Grants permission to query key event notifications.

list

-

-

cts:notification:delete

Grants permission to delete a notification rule.

write

cts:<region>:<account-id>:notification:<notification-id>

-

cts:tag:create

Grants permission to create a resource tag.

tagging

cts:<region>:<account-id>:tracker:<tracker-id>

-

-
  • g:TagKeys
  • g:RequestTag/<tag-key>

cts:tag:delete

Grants permission to delete a resource tag.

tagging

cts:<region>:<account-id>:tracker:<tracker-id>

-

-
  • g:TagKeys
  • g:RequestTag/<tag-key>

cts:notification:listOperation

Grants permission to query all operation lists.

list

-

-

cts:trace:listTraceUser

Grants permission to query all operator lists.

list

-

-

cts:trace:listResource

Grants permission to query all trace resource type lists.

list

-

-

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

Table 2 Actions and dependencies of CTS APIs

API

Action

Dependencies

GET /v3/{project_id}/traces

cts:trace:list

-

GET /v3/{project_id}/quotas

cts:quota:get

-

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:PutBucketAcl
  • kms:cmk:list

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

GET /v3/{project_id}/trackers

cts:tracker:list

-

DELETE /v3/{project_id}/trackers

cts:tracker:delete

-

POST /v3/{project_id}/notifications

cts:notification:create
  • smn:topic:listTopic
  • iam:users:listUsers
  • iam:groups:listGroups

PUT /v3/{project_id}/notifications

cts:notification:update
  • smn:topic:listTopic
  • iam:users:listUsers
  • iam:groups:listGroups

DELETE /v3/{project_id}/notifications

cts:notification:delete

-

GET /v3/{project_id}/notifications/{notification_type}

cts:notification:list

-

POST /v3/{project_id}/{resource_type}/{resource_id}/tags/create

cts:tag:create

-

DELETE /v3/{project_id}/{resource_type}/{resource_id}/tags/delete

cts:tag:delete

-

GET /v3/{domain_id}/resources

cts:trace:listResource

-

GET /v3/{project_id}/operations

cts:notification:listOperation

-

GET /v3/{project_id}/user-resources

cts:trace:listTraceUser

-

POST /v3/{domain_id}/checkbucket

cts:tracker:list

obs:bucket:ListAllMyBuckets

GET /v3/{project_id}/traces

cts:trace:list

-

GET /v3/{project_id}/quotas

cts:quota:get

-

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:PutBucketAcl
  • kms:cmk:list

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

GET /v3/{project_id}/trackers

cts:tracker:list

-

DELETE /v3/{project_id}/trackers

cts:tracker:delete

-

POST /v3/{project_id}/notifications

cts:notification:create
  • smn:topic:listTopic
  • iam:users:listUsers
  • iam:groups:listGroups

PUT /v3/{project_id}/notifications

cts:notification:update
  • smn:topic:listTopic
  • iam:users:listUsers
  • iam:groups:listGroups

DELETE /v3/{project_id}/notifications

cts:notification:delete

-

GET /v3/{project_id}/notifications/{notification_type}

cts:notification:list

-

POST /v3/{project_id}/{resource_type}/{resource_id}/tags/create

cts:tag:create

-

DELETE /v3/{project_id}/{resource_type}/{resource_id}/tags/delete

cts:tag:delete

-

GET /v3/{domain_id}/resources

cts:trace:listResource

-

GET /v3/{project_id}/operations

cts:notification:listOperation

-

GET /v3/{project_id}/user-resources

cts:trace:listTraceUser

-

POST /v3/{domain_id}/checkbucket

cts:tracker:list

obs:bucket:ListAllMyBuckets

Resources

CTS does not support resource-level authorization. To allow access to cts, use a wildcard (*) in the Resource element of the SCP, indicating that the SCP will be applied to all resources.

Conditions

CTS does not support service-specific condition keys in SCPs.It can only use global condition keys applicable to all services. For details, see Global Condition Keys.

Parent topic: Management & Governance