Help Center> > API Reference > Appendix > Permissions Policies and Supported Actions >Introduction


This section describes fine-grained permissions management for your VPCs. If your account does not need individual IAM users, then you may skip over this section.

A policy is a set of permissions defined in JSON format. By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign permission policies to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on VPCs based on the permissions. For more information about policy syntax and example policies, see Fine-grained Policy.

There are fine-grained policies and role-based access control (RBAC) policies. An RBAC policy consists of permissions for an entire service. Users in a group with such a policy assigned are granted all of the permissions required for that service. A fine-grained policy consists of API-based permissions for operations on specific resource types. Fine-grained policies, as the name suggests, allow for more fine-grained control than RBAC policies.

  • Fine-grained policies are currently available for open beta testing. You can apply to use the fine-grained access control function free of charge. For more information, see "Fine-grained Policy".
  • If you want to allow or deny the access to an API, fine-grained authorization is a good choice.

An account has all of the permissions required to call all APIs, but IAM users must have the required permissions specifically assigned. The permissions required for calling an API are determined by the actions supported by the API. Only users that have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user queries VPCs using an API, the user must have been granted permissions that allow the vpc:vpcs:list action.

Supported Actions

Operations supported by a fine-grained policy are specific to APIs. The following describes the headers of the actions provided in this section:

  • Permissions: Defined by actions in a custom policy.
  • Actions: Added to a custom policy to control permissions for specific operations.
  • Authorization Scope: A custom policy can be applied to IAM projects or enterprise projects or both. Policies that contain actions supporting both IAM and enterprise projects can be assigned to user groups and take effect in both IAM and Enterprise Management. Policies that only contain actions supporting IAM projects can be assigned to user groups and only take effect for IAM. Such policies will not take effect if they are assigned to user groups in Enterprise Management. For details about the differences between IAM and enterprise projects, see What Are the Differences Between IAM and Enterprise Management.
  • APIs: REST APIs that can be called in a custom policy.

VPC supports the following actions that can be defined in custom policies:

VPC actions that supported by VPC APIs include creating a VPC, querying a VPC, querying VPCs, updating a VPC, and deleting a VPC.