All Products
Search
Document Center

Virtual Private Cloud:RAM authorization

Last Updated:Jan 30, 2026

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 Virtual Private Cloud for RAM permission policies. The RAM code (RamCode) for Virtual Private Cloud is vpc , and the supported authorization granularity is RESOURCE .

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 Virtual Private Cloud. 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

vpc:GetIpamPoolNextAvailableCidr GetIpamPoolNextAvailableCidr get

*IpamPool

acs:vpc:{#regionId}:{#accountId}:ipampool/{#IpamPoolId}

None None
vpc:CreateIpam CreateIpam create

*All Resource

*

None None
vpc:ListIpamResourceDiscoveryAssociations ListIpamResourceDiscoveryAssociations list

*All Resource

*

None None
vpc:TagResources TagResources update

Ipam

acs:vpc:{#regionId}:{#accountId}:ipam/{#IpamId}

IpamPool

acs:vpc:{#regionId}:{#accountId}:ipampool/{#IpamPoolId}

IpamScope

acs:vpc:{#regionId}:{#accountId}:ipamscope/{#IpamScopeId}

None None
vpc:ListIpamDiscoveredResource ListIpamDiscoveredResource list

*IpamResourceDiscovery

acs:vpc:{#regionId}:{#accountId}:ipamresourcediscovery/{#IpamResourceDiscoveryId}

None None
vpc:AddIpamPoolCidr AddIpamPoolCidr update

*All Resource

*

None None
vpc:UpdateIpamScope UpdateIpamScope update

*All Resource

*

None None
vpc:CreateIpamScope CreateIpamScope create

*All Resource

*

None None
vpc:AssociateIpamResourceDiscovery AssociateIpamResourceDiscovery update

*IpamResourceDiscovery

acs:vpc:{#regionId}:{#accountId}:ipamresourcediscovery/{#IpamResourceDiscoveryId}

*Ipam

acs:vpc:{#regionId}:{#accountId}:ipam/{#IpamId}

None None
vpc:UpdateIpamPoolAllocation UpdateIpamPoolAllocation update

*All Resource

*

None None
vpc:ListIpamPoolCidrs ListIpamPoolCidrs list

*All Resource

*

None None
vpc:GetIpamPoolAllocation GetIpamPoolAllocation get

*IpamPool

acs:vpc:{#regionId}:{#accountId}:ipampool/{#IpamPoolId}

None None
vpc:CreateIpamPoolAllocation CreateIpamPoolAllocation create

*All Resource

*

None None
vpc:UpdateIpam UpdateIpam update

*Ipam

acs:vpc:{#regionId}:{#accountId}:ipam/{#IpamId}

None None
vpc:CreateIpamResourceDiscovery CreateIpamResourceDiscovery create

*IpamResourceDiscovery

acs:vpc:{#regionId}:{#accountId}:ipamresourcediscovery/*

None None
vpc:DeleteIpamPoolAllocation DeleteIpamPoolAllocation delete

*IpamPool

acs:vpc:{#regionId}:{#accountId}:ipampool/{#IpamPoolId}

None None
vpc:DeleteIpamPool DeleteIpamPool delete

*All Resource

*

None None
vpc:DissociateIpamResourceDiscovery DissociateIpamResourceDiscovery update

*IpamResourceDiscovery

acs:vpc:{#regionId}:{#accountId}:ipamresourcediscovery/{#IpamResourceDiscoveryId}

*Ipam

acs:vpc:{#regionId}:{#accountId}:ipam/{#IpamId}

None None
vpc:DeleteIpamResourceDiscovery DeleteIpamResourceDiscovery delete

*IpamResourceDiscovery

acs:vpc:{#regionId}:{#accountId}:ipamresourcediscovery/{#IpamResourceDiscoveryId}

None None
vpc:UntagResources UntagResources update

Ipam

acs:vpc:{#regionId}:{#accountId}:ipam/{#IpamId}

IpamPool

acs:vpc:{#regionId}:{#accountId}:ipampool/{#IpamPoolId}

IpamScope

acs:vpc:{#regionId}:{#accountId}:ipamscope/{#IpamScopeId}

None None
vpc:OpenVpcIpamService OpenVpcIpamService create

*All Resource

*

None None
vpc:ListIpamResourceCidrs ListIpamResourceCidrs list

*IpamScope

acs:vpc:{#regionId}:{#accountId}:ipamscope/{#IpamScopeId}

None None
vpc:UpdateIpamPool UpdateIpamPool update

*All Resource

*

None None
vpc:ListTagResources ListTagResources list

Ipam

acs:vpc:{#regionId}:{#accountId}:ipam/{#IpamId}

IpamPool

acs:vpc:{#regionId}:{#accountId}:ipampool/{#IpamPoolId}

IpamScope

acs:vpc:{#regionId}:{#accountId}:ipamscope/{#IpamScopeId}

None None
vpc:ListIpamResourceDiscoveries ListIpamResourceDiscoveries list

*All Resource

*

None None
vpc:ListIpamMembers ListIpamMembers list

*All Resource

*

None None
vpc:ListIpamPools ListIpamPools list

*IpamPool

acs:vpc:{#regionId}:{#accountId}:ipampool/*

None None
vpc:GetVpcIpamServiceStatus GetVpcIpamServiceStatus get

*All Resource

*

None None
vpc:AddIpamMembers AddIpamMembers create

*All Resource

*

None None
vpc:ListIpamPoolAllocations ListIpamPoolAllocations list

*All Resource

*

None None
vpc:DeleteIpam DeleteIpam create

*All Resource

*

None None
vpc:CreateIpamPool CreateIpamPool create

*IpamPool

acs:vpc:{#regionId}:{#accountId}:ipamscope/*

None None
vpc:DeleteIpamPoolCidr DeleteIpamPoolCidr delete

*IpamPool

acs:vpc:{#regionId}:{#accountId}:ipampool/{#IpamPoolId}

None None
vpc:ListIpams ListIpams list

*All Resource

*

None None
vpc:ChangeResourceGroup ChangeResourceGroup update

*Ipam

acs:vpc:{#regionId}:{#accountId}:ipam/{#IpamId}

None None
vpc:DeleteIpamScope DeleteIpamScope delete

*IpamScope

acs:vpc:{#regionId}:{#accountId}:ipamscope/{#IpamScopeId}

None None
vpc:ListIpamScopes ListIpamScopes list

*IpamScope

acs:vpc:{#regionId}:{#accountId}:ipamscope/*

None None
vpc:UpdateIpamResourceDiscovery UpdateIpamResourceDiscovery update

*IpamResourceDiscovery

acs:vpc:{#regionId}:{#accountId}:ipamresourcediscovery/{#IpamResourceDiscoveryId}

None None

Resource

The following table lists the resources defined by Virtual Private Cloud. 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

IpamPool
  • acs:vpc:{#regionId}:{#accountId}:ipampool/{#IpamPoolId}
  • acs:vpc:{#regionId}:{#accountId}:ipampool/*
  • acs:vpcipam:{#regionId}:{#accountId}:ipampool/{#IpamPoolId}
  • acs:vpc:{#regionId}:{#accountId}:ipamscope/*
Ipam
  • acs:vpc:{#regionId}:{#accountId}:ipam/*
  • acs:vpc:{#regionId}:{#accountId}:ipam/{#IpamId}
IpamResourceDiscovery
  • acs:vpc:{#regionId}:{#accountId}:ipamresourcediscovery/*
  • acs:vpc:{#regionId}:{#accountId}:ipamresourcediscovery/{#IpamResourceDiscoveryId}
IpamScope
  • acs:vpc:{#regionId}:{#accountId}:ipamscope/{#IpamScopeId}
  • acs:vpc:{#regionId}:{#accountId}:ipamscope/*
  • acs:vpc:{#regionId}:{#accountId}:ipam/*
IpamService
  • acs:vpc:{#regionId}:{#accountId}:ipam/*

Condition

Virtual Private Cloud 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: