Cloud Data Center

IAM provides system-defined identity policies to define common actions supported by cloud services. You can also create custom identity policies using the actions supported by cloud services for more refined access control.

In addition to IAM, the Organizations service provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to a principal. 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. The granted permissions can be applied only if they are allowed by the SCPs.

To learn more about how IAM is different from Organizations for access control, see What Are the Differences in Access Control Between IAM and Organizations?

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

For details about how to use these elements to create an IAM custom identity policy, see Creating a Custom Identity Policy.
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 identity policy.

The Access Level column describes how the action is classified (such as List, Read, Write, or Tagging). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
The Resource 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 identity policy statements.
- If this column includes a resource type, you must specify the URN in the Resource element of your 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 CloudDC, see Resources.
The Condition Key column contains keys that you can specify in the Condition element of an identity policy 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 CloudDC, see Conditions.

The following table lists the actions that you can define in identity policy statements for CloudDC.

**Table 1** Actions supported by CloudDC
Action	Description	Access Level	Resource Type	Resource Condition Key	Global Condition Key
clouddc:imetal:list	Batch querying physical servers	list	iMetal	-	-
clouddc:imetal:get	Querying information about physical servers	read	iMetal	g:ResourceTag/<tag-key>	-
clouddc:imetal:getHardwareAttribute	Querying server hardware details	read	iMetal	g:ResourceTag/<tag-key>	-
clouddc:imetal:getFirmwareAttribute	Querying server firmware details	read	iMetal	g:ResourceTag/<tag-key>	-
clouddc:imetal:updatePowerStatus	Modifying the power statuses of physical servers	write	iMetal	g:ResourceTag/<tag-key>	-
clouddc:imetal:createDumpLog	Exporting server logs	write	iMetal	g:ResourceTag/<tag-key>	-
clouddc:imetal:getDumpLogProgress	Querying the export status of logs	read	iMetal	g:ResourceTag/<tag-key>	-
clouddc:imetal:createDownloadLog	Downloading logs	write	iMetal	g:ResourceTag/<tag-key>	-
clouddc:imetal:createRemoteConsoleLink	Obtaining the console address	write	iMetal	g:ResourceTag/<tag-key>	-
clouddc:instance:createBatch	Batch creating instances	write	iMetal	-	-
clouddc:instance:list	Batch querying instances	list	iMetal	-	-
clouddc:instance:deleteBatch	Batch deleting instances	write	iMetal	-	-
clouddc:instance:create	Creating an instance	write	iMetal	-	-
clouddc:instance:delete	Deleting an instance	write	iMetal	-	-
clouddc:instance:changePassword	Changing the password of an instance	write	iMetal	-	-
clouddc:instance:reinstallOS	Reinstalling the OS on an instance	write	iMetal	-	-
clouddc:instance:get	Querying the status of an instance	read	iMetal	-	-
clouddc:instance:updateIP	Changing the IP address of an instance	write	iMetal	-	-
clouddc::listResourcesByTag	Listing resources	list	iMetal	-	g:TagKeys
clouddc::listTagsForResource	Querying tags of a resource	list	iMetal	g:ResourceTag/<tag-key>	-
clouddc::listTags	Querying resource tags in a specified project.	list	iMetal	-	-
clouddc::listResourcesByTag	Querying the number of instances	list	iMetal	-	g:TagKeys
clouddc::tagResource	Batch creating iMetal server tags	tagging	iMetal	g:ResourceTag/<tag-key>	g:RequestTag/<tag-key> g:TagKeys
clouddc::unTagResource	Batch deleting iMetal server tags	tagging	iMetal	g:ResourceTag/<tag-key>	g:RequestTag/<tag-key> g:TagKeys
clouddc::listStatus	Obtaining server overview	list	iMetal	-	-
clouddc::listAlarmStat	Obtaining server alarm overview	list	iMetal	-	-
clouddc::listAlarmTrend	Obtaining the server alarm trend	list	iMetal	-	-
clouddc::listAlarm	Obtaining the server alarm list	list	iMetal	-	-
clouddc::listEvent	Obtaining the server event list	list	iMetal	-	-
clouddc::listIEventDicts	Querying event definitions	list	iMetal	-	-
clouddc::updateRepairs	Updating or creating server maintenance data	write	iMetal	-	-
clouddc::listRepairs	Querying server maintenance data	list	iMetal	-	-
clouddc::updateSpareParts	Creating and updating spare parts	write	iMetal	-	-
clouddc::listSpareParts	Querying spare parts	list	iMetal	-	-
clouddc:irack:update	Modifying the intelligent rack description	write	iRack	g:ResourceTag/<tag-key>	-
clouddc:irack:list	Querying the intelligent rack list	list	iRack	-	-
clouddc:idc:update	Modifying the IDC description	write	iRack	-	-
clouddc:idc:list	Querying the IDC list	list	iRack	-	-
clouddc::listResourcesByTag	Querying the rack list	list	iRack	-	g:TagKeys
clouddc::listTagsForResource	Querying rack tags	list	iRack	g:ResourceTag/<tag-key>	-
clouddc::listTags	Querying rack tags in a specified project	list	iRack	-	-
clouddc::listResourcesByTag	Querying the number of racks	list	iRack	-	g:TagKeys
clouddc::tagResource	Batch creating rack tags	tagging	iRack	g:ResourceTag/<tag-key>	g:RequestTag/<tag-key> g:TagKeys
clouddc::unTagResource	Batch deleting rack tags	tagging	iRack	g:ResourceTag/<tag-key>	g:RequestTag/<tag-key> g:TagKeys
clouddc::createIRackOrder	Granting permissions to check order parameters	write	iRack	-	-

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

**Table 2** APIs and actions
API URI	Request Type	Description	Action	Action
/v1/{project_id}/physicalservers	GET	Batch querying physical servers	clouddc:imetal:list	-
/v1/{project_id}/physicalservers/{id}	GET	Querying information about physical servers	clouddc:imetal:get	-
/v1/{project_id}/physicalservers/{id}/hardware-attributes	GET	Querying server hardware details	clouddc:imetal:getHardwareAttribute	-
/v1/{project_id}/physicalservers/{id}/firmware-attributes	GET	Querying server firmware details	clouddc:imetal:getFirmwareAttribute	-
/v1/{project_id}/physicalservers/{id}/power-state	PUT	Modifying the power statuses of physical servers	clouddc:imetal:updatePowerStatus	-
/v1/{project_id}/physicalservers/{id}/logs/exports	POST	Exporting server logs	clouddc:imetal:createDumpLog	-
/v1/{project_id}/physicalservers/{id}/logs/exports/{export_id}	GET	Querying the export status of logs	clouddc:imetal:getDumpLogProgress	-
/v1/{project_id}/physicalservers/{id}/logs/exports/{export_id}/content	GET	Downloading logs	clouddc:imetal:createDownloadLog	-
/v1/{project_id}/physicalservers/{id}/remote-console-address	GET	Obtaining the console address	clouddc:imetal:createRemoteConsoleLink	-
/v1/{project_id}/instances/batch-create	POST	Batch creating instances	clouddc:instance:createBatch	-
/v1/{project_id}/instances	GET	Batch querying instances	clouddc:instance:list	-
/v1/{project_id}/instances/batch-delete	DELETE	Batch deleting instances	clouddc:instance:deleteBatch	-
/v1/{project_id}/instance	POST	Creating an instance	clouddc:instance:create	-
/v1/{project_id}/instances/{id}	DELETE	Deleting an instance	clouddc:instance:delete	-
/v1/{project_id}/instances/{id}/password	PUT	Changing the password of an instance	clouddc:instance:changePassword	-
/v1/{project_id}/instances/{id}/reinstall	PUT	Reinstalling the OS on an instance	clouddc:instance:reinstallOS	-
/v1/{project_id}/instances/{id}/status	GET	Querying the status of an instance	clouddc:instance:get	-
/v1/{project_id}/instances/{id}/ip	PUT	Changing the IP address of an instance	clouddc:instance:updateIP	-
/{version}/{project_id}/{resource_type}/resource-instances/filter	POST	Listing resources	clouddc::listResourcesByTag	-
/{version}/{project_id}/{resource_type}/{resource_id}/tags	GET	Querying tags of a resource	clouddc::listTagsForResource	-
/{version}/{project_id}/{resource_type}/tags	GET	Querying resource tags in a specified project.	clouddc::listTags	-
/{version}/{project_id}/{resource_type}/resource-instances/count	POST	Querying the number of instances	clouddc::listResourcesByTag	-
/v1/{project_id}/{resource_type}/{resource_id}/tags/create	POST	Batch creating resource tags	clouddc::tagResource	-
/v1/{project_id}/{resource_type}/{resource_id}/tags/delete	POST	Batch deleting resource tags	clouddc::unTagResource	-
/v1/{project_id}/physicalservers/status	GET	Obtaining server overview	clouddc::listStatus	-
/v1/{project_id}/physicalservers/alarms/summary	GET	Obtaining server alarm overview	clouddc::listAlarmStat	ces:alarmHistory:list
/v1/{project_id}/physicalservers/alarms/trend	GET	Obtaining the server alarm trend	clouddc::listAlarmTrend	ces:alarmHistory:list
/v1/{project_id}/physicalservers/alarms	GET	Obtaining the server alarm list	clouddc::listAlarm	ces:alarmHistory:list
/v1/{project_id}/physicalservers/events	GET	Obtaining the server event list	clouddc::listEvent	ces:events:get
/v1/{project_id}/physicalservers/events/{event_id}	GET	Querying event definitions	clouddc::listIEventDicts	-
/v1/{project_id}/repairs	PUT	Updating or creating server maintenance data	clouddc::updateRepairs	-
/v1/{project_id}/repairs	GET	Querying server maintenance data	clouddc::listRepairs	-
/v1/{project_id}/spareparts	PUT	Creating and updating spare parts	clouddc::updateSpareParts	-
/v1/{project_id}/spareparts	GET	Querying spare parts	clouddc::listSpareParts	-
/v1/{project_id}/iracks/{irack_id}	PUT	Modifying the intelligent rack description	clouddc:irack:update	-
/v1/{project_id}/iracks	GET	Querying the intelligent rack list	clouddc:irack:list	-
/v1/{project_id}/idcs	PUT	Modifying the IDC description	clouddc:idc:update	-
/v1/{project_id}/idcs	GET	Querying the IDC list	clouddc:idc:list	-
/{version}/{project_id}/{resource_type}/resource-instances/filter	POST	Querying the rack list	clouddc::listResourcesByTag	-
/{version}/{project_id}/{resource_type}/{resource_id}/tags	GET	Querying rack tags	clouddc::listTagsForResource	-
/{version}/{project_id}/{resource_type}/tags	GET	Querying rack tags in a specified project	clouddc::listTags	-
/{version}/{project_id}/{resource_type}/resource-instances/count	POST	Querying the number of racks	clouddc::listResourcesByTag	-
/v1/{project_id}/iracks/{id}/tags/create	POST	Batch creating rack tags	clouddc::tagResource	-
/v1/{project_id}/iracks/{id}/tags/delete	POST	Batch deleting rack tags	clouddc::unTagResource	-
/v1/services/unibuy/extend	POST	Granting permissions to check order parameters	clouddc::createIRackOrder	-

Resources

A resource type indicates the resources that an identity policy applies to. If you specify a resource type for any action in Table 3, a resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to the resource. If no resource type is specified, the Resource element is marked with an asterisk (*) and the identity policy applies to all resources. You can also set condition keys in an identity policy to define resource types.

The following table lists the resource types that you can specify in identity policy statements for CloudDC.

**Table 3** Resource types supported by CloudDC
Resource Type	URN
iMetal	clouddc:<region>:<account-id>:imetal:<resource-id>
iRack	clouddc:<region>:<account-id>:irack:<resource-id>

Conditions

About condition keys

A Condition element lets you specify conditions for when an identity policy 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 Table 4. For details about global condition keys, see Common global condition keys.
- Service-specific condition keys (with the abbreviation of a service name plus a colon as the prefix, for example, clouddc:) only apply to operations of that service. CloudDC does not support service-specific condition keys in identity policies.
- 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 identity policy can be applied only when its request conditions are met.

The following table lists the condition keys that you can define in identity policies for CloudDC. You can include these condition keys to specify conditions for when your identity policy is in effect.

**Table 4** Global condition keys supported by CloudDC
Global Condition Key	Type	Description
g:ResourceTag/<tag-key>	Single-valued string	Tag attached to the requested resource.
g:RequestTag/<tag-key>	Single-valued string	Tag contained in a request.
g:TagKeys	Multivalued string	List of tag keys in a request.