RAM authorization-Short Message Service(SMS)-阿里云帮助中心

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 Short Message Service for RAM permission policies. The RAM code (RamCode) for Short Message Service is dysms,cloudcomm,dybase,sms , and the supported authorization granularity is SERVICE .

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 Short Message 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
dysms:QueryCardSmsTemplate	QueryCardSmsTemplate	get	All Resource ``	None	None
dysms:ModifySmsTemplate	ModifySmsTemplate	update	All Resource ``	None	None
dysms:GetSmsSign	GetSmsSign	none	All Resource ``	None	None
dysms:GetMediaResourceId	GetMediaResourceId	get	All Resource ``	None	None
dysms:SmsConversionIntl	SmsConversionIntl	get	All Resource ``	None	None
dysms:GetCardSmsDetails	GetCardSmsDetails	none	All Resource ``	None	None
dysms:SendCardSms	SendCardSms	get	All Resource ``	None	None
dysms:DeleteSmsTemplate	DeleteSmsTemplate	delete	All Resource ``	None	None
dysms:QueryShortUrl	QueryShortUrl	get	All Resource ``	None	None
dysms:CreateSmsSign	CreateSmsSign	none	All Resource ``	None	None
dysms:GetCardSmsLink	GetCardSmsLink	get	All Resource ``	None	None
dysms:GetOSSInfoForCardTemplate	GetOSSInfoForCardTemplate	get	All Resource ``	None	None
dysms:SendBatchCardSms	SendBatchCardSms	get	All Resource ``	None	None
dysms:ListTagResources	ListTagResources	list	All Resource ``	None	None
dysms:CreateSmsTemplate	CreateSmsTemplate	none	All Resource ``	None	None
dysms:QuerySmsSignList	QuerySmsSignList	get	All Resource ``	None	None
dysms:AddSmsTemplate	AddSmsTemplate	create	All Resource ``	None	None
dysms:DeleteSmsSign	DeleteSmsSign	delete	All Resource ``	None	None
dysms:DeleteShortUrl	DeleteShortUrl	delete	All Resource ``	None	None
dysms:QuerySmsSign	QuerySmsSign	get	All Resource ``	None	None
dysms:SendBatchSms	SendBatchSms	get	All Resource ``	None	None
dysms:ConversionDataIntl	ConversionDataIntl	get	All Resource ``	None	None
dysms:CreateCardSmsTemplate	CreateCardSmsTemplate	create	All Resource ``	None	None
dysms:GetSmsOcrOssInfo	GetSmsOcrOssInfo	get	All Resource ``	None	None
dysms:UpdateSmsTemplate	UpdateSmsTemplate	none	All Resource ``	None	None
dysms:QuerySendDetails	QuerySendDetails	get	All Resource ``	None	None
dysms:QuerySendStatistics	QuerySendStatistics	get	All Resource ``	None	None
dysms:QuerySmsTemplate	QuerySmsTemplate	get	All Resource ``	None	None
dysms:QueryCardSmsTemplateReport	QueryCardSmsTemplateReport	get	All Resource ``	None	None
dysms:ModifySmsSign	ModifySmsSign	update	All Resource ``	None	None
dysms:SendSms	SendSms	get	All Resource ``	None	None
dysms:QueryMobilesCardSupport	QueryMobilesCardSupport	get	All Resource ``	None	None
dysms:QuerySmsTemplateList	QuerySmsTemplateList	get	All Resource ``	None	None
dysms:GetSmsTemplate	GetSmsTemplate	none	All Resource ``	None	None
dysms:UntagResources	UntagResources	delete	All Resource ``	None	None
dysms:CheckMobilesCardSupport	CheckMobilesCardSupport	get	All Resource ``	None	None
dysms:UpdateSmsSign	UpdateSmsSign	none	All Resource ``	None	None
dysms:AddShortUrl	AddShortUrl	create	All Resource ``	None	None
dysms:AddSmsSign	AddSmsSign	create	All Resource ``	None	None
dysms:TagResources	TagResources	update	All Resource ``	None	None

Resource

The following table lists the resources defined by Short Message 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

The following table lists the product-level condition keys defined by Short Message Service. You can also use Alibaba Cloud's Common condition keys. Specify these keys in the Condition element of RAM policy statements to define granular authorization rules. In the condition key, specify the condition values in the Condition_value element of the policy.

Each condition key has a specific data type, such as string, number, Boolean, or IP address. The data type determines which conditional operators can be used to compare the request values against policy values. You must specify the conditional operators compatible with the data type of the condition key. Mismatched operators will invalidate the policy. See Condition operator for valid combinations.

Condition key	Description	Data type
dysms:TLSVersion	TLS version	String

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: