DataArts Studio
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 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. 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 by an SCP in an identity policy.
- 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 identity policy.
- 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 identity policy statements.
- If this column includes a resource type, you must specify a URN for the Resource element in 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 DataArts Studio, see Resources.
- Condition Key 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 DataArts Studio, see Conditions.
- The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.
The following table lists the actions that you can define in custom identity policies for DataArts Studio.
Due to API restrictions, if the resource type is specified for a custom identity policy, the permission configuration may not meet expectations because some operations are unavailable for specified workspace or instance resources. For example, if an operation that does not support specified resources is allowed but a specific resource is specified for the operation, all resource operations are denied. If an operation that does not support specified resources is denied but a specific resource is specified for the operation, all resource operations are allowed.
"Resource": [
"DataArtsStudio:*:*:workspace:*",
"DataArtsStudio:*:*:instance:*"
]
The operations that cannot be performed on specified resources in DataArts Studio are as follows:
- Operations that can be performed only on specified instance resources but not on specified workspace resources:
- DataArtsStudio:workspace:create
- DataArtsStudio:workspace:list
- Operations that cannot be performed on specified instance or workspace resources:
- DataArtsStudio:instance:create
- DataArtsStudio:instance:get
- DataArtsStudio:instance:list
- DataArtsStudio:instance:resize
- DataArtsStudio:instance:getAgency
- DataArtsStudio:instance:createAgency
- DataArtsStudio:instance:uploadDriver
- DataArtsStudio:instance:deleteDriver
- DataArtsStudio:instance:listDrivers
- DataArtsStudio:instance:listTags
- DataArtsStudio:workspace:listTags
|
Action |
Description |
Access Level |
Resource Type (*: Required) |
Condition Key |
Alias |
|---|---|---|---|---|---|
|
DataArtsStudio:workspace:list |
Grants the permission to query all workspaces. |
List |
workspace * |
|
|
|
instance * |
|||||
|
DataArtsStudio:workspace:create |
Grants the permission to create a workspace. |
Write |
workspace * |
- |
- |
|
instance * |
|||||
|
- |
|||||
|
DataArtsStudio:workspace:get |
Grants the permission to query workspace information. |
Read |
workspace * |
- |
|
|
instance * |
|||||
|
DataArtsStudio:workspace:frozen |
Grants the permission to freeze a workspace. |
Write |
workspace * |
- |
|
|
instance * |
|||||
|
DataArtsStudio:workspace:unfrozen |
Grants the permissions to unfreeze a workspace. |
Write |
workspace * |
- |
|
|
instance * |
|||||
|
DataArtsStudio:workspace:update |
Grants the permission to update a workspace. |
Write |
workspace * |
- |
|
|
instance * |
|||||
|
DataArtsStudio:instance:list |
Grants the permission to query all instances. |
List |
instance * |
|
|
|
DataArtsStudio:instance:create |
Grants the permission to create an instance. |
Write |
instance * |
- |
- |
|
- |
|||||
|
DataArtsStudio:instance:get |
Grants the permission to query an instance. |
Read |
instance * |
- |
|
|
DataArtsStudio:instance:resize |
Grants the permission to change instance specifications. |
Write |
instance * |
- |
|
|
DataArtsStudio:instance:listDrivers |
Grants the permission to query all driver files. |
List |
- |
- |
- |
|
DataArtsStudio:instance:uploadDriver |
Grants the permission to upload a driver file. |
Write |
- |
- |
- |
|
DataArtsStudio:instance:deleteDriver |
Grants the permission to delete a driver file. |
Write |
- |
- |
- |
|
DataArtsStudio:workspace:delete |
Grants the permission to delete a workspace. |
Write |
workspace * |
- |
|
|
instance * |
|||||
|
DataArtsStudio:instance:getAgency |
Grants the permission to query an agency. |
Read |
- |
- |
- |
|
DataArtsStudio:instance:createAgency |
Grants the permission to create an agency. |
Write |
- |
- |
- |
|
DataArtsStudio:instance:delete |
Grants the permission to delete an instance. |
Write |
instance * |
- |
|
|
DataArtsStudio:instance:migrateBusinessModel |
Grants the permission to change the business model of an instance. |
Write |
instance * |
- |
|
|
DataArtsStudio:instance:operate |
Grants the permission to operate the resources of an instance. |
Write |
instance * |
- |
|
|
DataArtsStudio:workspace:operate |
Grants the permission to operate the resources in a workspace. |
Write |
workspace * |
- |
|
|
instance * |
|||||
|
DataArtsStudio:instance:createRole |
Grants the permission to create a custom role. |
Write |
instance * |
- |
|
|
DataArtsStudio:instance:listRoles |
Grants the permission to query custom roles. |
List |
instance * |
- |
|
|
DataArtsStudio:instance:getRoleType |
Grants the permission to query the type of a custom role. |
Read |
instance * |
- |
|
|
DataArtsStudio:instance:getRole |
Grants the permission to query a custom role. |
Read |
instance * |
- |
|
|
DataArtsStudio:instance:updateRole |
Grants the permission to update a custom role. |
Write |
instance * |
- |
|
|
DataArtsStudio:instance:deleteRole |
Grants the permission to delete a custom role. |
Write |
instance * |
- |
|
|
DataArtsStudio:instance:tagResource |
Grants the permission to add an instance tag. |
Write |
instance * |
- |
|
|
- |
|||||
|
DataArtsStudio:instance:unTagResource |
Grants the permission to delete an instance tag. |
Write |
instance * |
- |
|
|
- |
|||||
|
DataArtsStudio:instance:listIncrementalPackages |
Grants the permission to query all incremental packages. |
List |
instance * |
- |
|
|
DataArtsStudio:workspace:createIncrementalPackage |
Grants the permission to create an incremental package for a workspace. |
Write |
workspace * |
- |
|
|
instance * |
|||||
|
DataArtsStudio:workspace:tagResource |
Grants the permission to add a tag to a workspace. |
Write |
workspace * |
- |
|
|
instance * |
|||||
|
- |
|||||
|
DataArtsStudio:workspace:unTagResource |
Grants the permission to delete a tag from a workspace. |
Write |
workspace * |
- |
|
|
instance * |
|||||
|
- |
|||||
|
DataArtsStudio:instance:createIncrementalPackage |
Grants the permission to create an incremental package for an instance. |
Write |
instance * |
- |
|
|
DataArtsStudio:instance:listTags |
Grants the permission to query the tags of all instances. |
List |
instance * |
- |
|
|
DataArtsStudio:workspace:listTags |
Grants the permission to query the tags of all workspaces. |
List |
workspace * |
- |
|
|
instance * |
|||||
|
DataArtsStudio:instance:listTagsForResource |
Grants the permission to query the tags of an instance. |
List |
instance * |
- |
|
|
DataArtsStudio:workspace:listTagsForResource |
Grants the permission to query the tags of a workspace. |
List |
workspace * |
- |
|
|
instance * |
|||||
|
DataArtsStudio:workspace:updateDataServiceApiQuota |
Grants the permission to update the DataArts DataService API quota of a workspace. |
Write |
workspace * |
- |
|
|
instance * |
|||||
|
DataArtsStudio:workspace:executeDataServiceInstanceAction |
Grants the permission to run commands to perform operations on DataArts DataService clusters. |
Write |
workspace * |
- |
|
|
instance * |
|||||
|
DataArtsStudio:instance:configureDataSecurityAdministrator |
Grants the permission to configure the data security administrator. |
Write |
instance * |
- |
|
|
DataArtsStudio:instance:listResourcesByTag |
Grants the permission to filter instances by tag. |
List |
instance * |
- |
|
|
DataArtsStudio:workspace:listResourcesByTag |
Grants the permission to filter workspaces by tag. |
List |
workspace * |
- |
|
|
instance * |
Each API of DataArts Studio usually supports one or more actions. Table 2 lists the actions and dependencies supported by DataArts Studio APIs.
|
API |
Action |
Dependency |
|---|---|---|
|
GET /v1/{project_id}/workspaces/{instance_id} |
DataArtsStudio:workspace:list |
- |
|
POST /v1/{project_id}/workspaces/{instance_id} |
DataArtsStudio:workspace:create |
- |
|
GET /v1/{project_id}/workspaces/{instance_id}/{workspace_id} |
DataArtsStudio:workspace:get |
- |
|
POST /v1/{project_id}/change-resource |
DataArtsStudio:instance:resize |
- |
|
GET /v1/{project_id}/instances |
DataArtsStudio:instance:list |
- |
|
POST /v1/{project_id}/instances/onekey-purchase |
DataArtsStudio:instance:create |
- |
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, the resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to resources of this type. 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 define in identity policy statements for DataArts Studio.
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.
- Condition keys are the key values in the Condition element of an identity policy statement. They are classified into global condition keys and service-specific condition keys based on the application scope.
- 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, dataarts studio:) apply only to operations of the specific service. For details, see Table 4.
- 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.
- An operator, a condition key, and a condition value together constitute a complete condition statement. An identity policy becomes in effect only when its request conditions are met. For supported condition operators, see Condition operators.
Service-specific condition keys supported by DataArts Studio
The following table lists the condition keys that you can define in custom identity policies for DataArts Studio. You can include these condition keys to specify conditions for when your identity policy is in effect.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot