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>	-
cts:tag:create	Grants permission to create a resource tag.	tagging	-	g:TagKeys g:RequestTag/<tag-key>
cts:tag:delete	Grants permission to delete a resource tag.	tagging	cts:<region>:<account-id>:tracker:<tracker-id>	-
cts:tag:delete	Grants permission to delete a resource tag.	tagging	-	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

A Condition element lets you specify conditions for when an SCP 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, cts:) only apply to operations of the CTS service. For details, see Table 3.
- 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 SCP can be applied only when its request conditions are met. For supported condition operators, see Condition operators.

The following table lists the condition keys that you can define in SCPs for CTS. You can include these condition keys to specify conditions for when your SCP is in effect.

**Table 3** Service-specific condition keys supported by CTS
Condition Key	Type	Single-valued/Multivalued	Description
cts:TargetType	string	Single-valued	Filter access permissions by data dump type.
cts:TargetAccountId	string	Single-valued	Filter access permissions based on the domain ID (account ID) of the user to which the OBS bucket belongs.
cts:TargetOrgId	string	Single-valued	Filter access permissions based on the organization to which the OBS bucket belongs.
cts:TargetOrgPath	string	Single-valued	Filter access permissions based on the OU path of the organization to which the OBS bucket belongs.