Tag Management Service (TMS)

Organizations provides your with Service Control Policies (SCPs) for access control.

SCPs do not actually grant any permissions to a principal. They only set the permissions boundary for the principal. When SCPs are attached to a member account or an organizational unit (OU), they do not directly grant permissions to that member account or OU. Instead, the SCPs just determine what permissions are available for that member account or the 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 create 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 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 TMS, 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 this column is empty (-), the action does not support any condition keys.
For details about the condition keys defined by TMS, see Conditions.

The following table lists the actions that you can define in custom policies for TMS.

**Table 1** Supported actions
Action	Description	Access Level	Resource Type (*: Required)	Condition Key
tms:predefineTags:list	Grants permission to query predefined tags.	list	-	-
tms:predefineTags:create	Grants permission to create predefined tags.	write	-	-
tms:predefineTags:update	Grants permission to modify predefined tags.	write	-	-
tms:predefineTags:delete	Grants permission to delete predefined tags.	write	-	-
tms:resourceTags:list	Grants permission to list resource tags.	list	-	-
tms:resourceTags:create	Grants permission to create resource tags.	write	-	-
tms:resourceTags:delete	Grants permission to delete resource tags.	write	-	-
tms:resources:list	Grants permission to list resources.	list	-	-
tms:tagKeys:list	Grants permission to list tag keys.	list	-	-
tms:tagValues:list	Grants permission to list tag values.	list	-	-

A TMS API usually supports one or more actions. Table 2 lists actions supported by each API and dependencies of actions.

**Table 2** Actions and dependencies
API	Action	Dependencies
GET /v1.0/predefine_tags	tms:predefineTags:list	-
POST /v1.0/predefine_tags/action	tms:predefineTags:create	-
PUT /v1.0/predefine_tags	tms:predefineTags:update	-
POST /v1.0/predefine_tags/action	tms:predefineTags:delete	-
GET /v2.0/resources/{resource_id}/tags	tms:resourceTags:list	-
POST /v1.0/resource-tags/batch-create	tms:resourceTags:create	-
POST /v1.0/resource-tags/batch-delete	tms:resourceTags:delete	-
POST /v1.0/resource-instances/filter	tms:resources:list	-
GET /v1.0/tag-keys	tms:tagKeys:list	-
GET /v1.0/tag-values	tms:tagValues:list	-

Resources

TMS does not support granting permissions for specific resources using SCPs To allow access to TMS, use the wildcard (*) in the Resource element in an SCP, and this SCP will apply to all resources of TMS.