RAM authorization-Voice Service(VS)-阿里云帮助中心

Resource Access Management (RAM) is a service provided by Alibaba Cloud to manage user identities and resource access permissions. Using RAM helps you avoid sharing your Alibaba Cloud account keys with other users and allows you to grant users the least privilege access. RAM uses permission policies to define authorizations. This topic describes the general structure of a RAM policy, and the policy statement elements (Action, Resource, and Condition) defined by Voice Service for RAM permission policies. The RAM code (RamCode) for Voice Service is dyvms , and the supported authorization granularity is OPERATION .

General structure of a policy

Permission policies support JSON format with the following general structure:

{
  "Version": "1",
  "Statement": [
    {
      "Effect": "<Effect>",
      "Action": "<Action>",
      "Resource": "<Resource>",
      "Condition": {
        "<Condition_operator>": {
          "<Condition_key>": [
            "<Condition_value>"
          ]
        }
      }
    }
  ]
}

The following list describes the fields in the policy:

Version: Specifies the policy version number. It is fixed at 1.
Statement:
- Effect: Specifies the authorization result. Valid values: Allow and Deny.
- Action: Specifies one or more operations that are allowed or denied.
- Resource: Specifies the specific objects affected by the operations. You can use Alibaba Cloud Resource Names (ARNs) to describe specific resources.
- Condition: Specifies the conditions for the authorization to take effect. This field is optional.
  - Condition operator: Specifies the conditional operators. Different types of conditions support different conditional operators.
  - Condition_key: Specifies the condition keys.
  - Condition_value: Specifies the condition values.

Action

The following table lists the actions defined by Voice Service. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that support authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding ARN in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys that are applicable across all RAM-integrated services. For more information, see Common condition keys.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action	API	Access level	Resource type	Condition key	Dependent action
dyvms:DegradeVideoFile	DegradeVideoFile	update	All Resource ``	None	None
dyvms:SmartCall	SmartCall	none	All Resource ``	None	None
dyvms:CancelOrderRobotTask	CancelOrderRobotTask	update	All Resource ``	None	None
dyvms:GetHotlineQualificationByOrder	GetHotlineQualificationByOrder	get	All Resource ``	None	None
dyvms:SubmitHotlineTransferRegister	SubmitHotlineTransferRegister	none	All Resource ``	None	None
dyvms:SetTransferCalleePoolConfig	SetTransferCalleePoolConfig	update	All Resource ``	None	None
dyvms:QueryCallInTransferRecord	QueryCallInTransferRecord	get	All Resource ``	None	None
dyvms:BatchRobotSmartCall	BatchRobotSmartCall	none	All Resource ``	None	None
dyvms:QueryCallDetailByCallId	QueryCallDetailByCallId	get	All Resource ``	None	None
dyvms:QueryVirtualNumberRelation	QueryVirtualNumberRelation	get	All Resource ``	None	None
dyvms:QueryRobotTaskCallDetail	QueryRobotTaskCallDetail	get	All Resource ``	None	None
dyvms:QueryCallDetailByTaskId	QueryCallDetailByTaskId	get	All Resource ``	None	None
dyvms:CreateRobotTask	CreateRobotTask	create	All Resource ``	None	None
dyvms:PauseVideoFile	PauseVideoFile	update	All Resource ``	None	None
dyvms:QueryVideoPlayProgress	QueryVideoPlayProgress	update	All Resource ``	None	None
dyvms:CancelCall	CancelCall	none	All Resource ``	None	None
dyvms:QueryRobotTaskDetail	QueryRobotTaskDetail	get	All Resource ``	None	None
dyvms:StartRobotTask	StartRobotTask	update	All Resource ``	None	None
dyvms:QueryRobotv2AllList	QueryRobotv2AllList	get	All Resource ``	None	None
dyvms:SmartCallOperate	SmartCallOperate	none	All Resource ``	None	None
dyvms:ListHotlineTransferRegisterFile	ListHotlineTransferRegisterFile	get	All Resource ``	None	None
dyvms:RecoverCallInConfig	RecoverCallInConfig	none	All Resource ``	None	None
dyvms:QueryVoiceFileAuditInfo	QueryVoiceFileAuditInfo	get	All Resource ``	None	None
dyvms:StopRobotTask	StopRobotTask	update	All Resource ``	None	None
dyvms:UpgradeVideoFile	UpgradeVideoFile	update	All Resource ``	None	None
dyvms:IvrCall	IvrCall	none	All Resource ``	None	None
dyvms:ExecuteCallTask	ExecuteCallTask	create	All Resource ``	None	None
dyvms:QueryCallInPoolTransferConfig	QueryCallInPoolTransferConfig	get	All Resource ``	None	None
dyvms:StopCallInConfig	StopCallInConfig	none	All Resource ``	None	None
dyvms:ListCallTask	ListCallTask	list	All Resource ``	None	None
dyvms:DeleteRobotTask	DeleteRobotTask	delete	All Resource ``	None	None
dyvms:SingleCallByVideo	SingleCallByVideo	none	All Resource ``	None	None
dyvms:ResumeVideoFile	ResumeVideoFile	update	All Resource ``	None	None
dyvms:QueryRobotTaskList	QueryRobotTaskList	get	All Resource ``	None	None
dyvms:SendVerification	SendVerification	none	All Resource ``	None	None
dyvms:QueryRobotInfoList	QueryRobotInfoList	get	All Resource ``	None	None
dyvms:QueryRobotTaskCallList	QueryRobotTaskCallList	get	All Resource ``	None	None
dyvms:CancelRobotTask	CancelRobotTask	update	All Resource ``	None	None
dyvms:AddVirtualNumberRelation	AddVirtualNumberRelation	none	All Resource ``	None	None
dyvms:UploadRobotTaskCalledFile	UploadRobotTaskCalledFile	none	All Resource ``	None	None
dyvms:PlayVideoFile	PlayVideoFile	update	All Resource ``	None	None
dyvms:CreateCallTask	CreateCallTask	create	All Resource ``	None	None
dyvms:SingleCallByTts	SingleCallByTts	none	All Resource ``	None	None
dyvms:SingleCallByVoice	SingleCallByVoice	none	All Resource ``	None	None
dyvms:GetToken	GetToken	get	All Resource ``	None	None
dyvms:ListCallTaskDetail	ListCallTaskDetail	list	All Resource ``	None	None
dyvms:SkipVideoFile	SkipVideoFile	update	All Resource ``	None	None

Resource

The following table lists the resources defined by Voice Service. Specify them in the Resource element of RAM policy statements to grant permissions for specific operations. They are uniquely identified by ARNs. Format: acs:{#ramcode}:{#regionId}:{#accountId}:{#resourceType}:

acs: The initialism of Alibaba Cloud service, which indicates the public cloud of Alibaba Cloud.
{#ramcode}: The code used in RAM to indicate an Alibaba Cloud service.
{#regionId}: The region ID. If the resource covers all regions, set it to an asterisk (*).
{#accountId}: The ID of the Alibaba Cloud account. If the resource covers all Alibaba Cloud accounts, set it to an asterisk (*).
{#resourceType}: The service-defined resource identifier. It supports a hierarchical structure, which is similar to a file path. If the statement covers global resources, set it to an asterisk (*).

Resource type

ARN

Condition

Voice Service does not define product-level condition keys. However, you can use Alibaba Cloud common condition keys for access control. For more information, see Common condition keys.

How to create custom RAM policies?

You can create custom policies and grant them to RAM users, RAM user groups, or RAM roles. For instructions, see: