Help Center> Distributed Database Middleware> API Reference> Permissions Policies and Supported Actions> Introduction
Updated on 2022-06-30 GMT+08:00
View PDF

Introduction

This section describes fine-grained permissions management for your DDM instance. If your account does not need individual IAM users, skip over this section.

By default, new IAM users do not have any permissions granted. You need to add a user to one or more groups, and assign policies or roles 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 the service based on the permissions.

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. If you want to send an API request using an IAM user of the account, ensure that the IAM user has the required permissions specifically assigned. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user queries ECSs using an API, the user must have been granted permissions that allow the ecs:servers:list action.

Supported Actions

DDM provides system-defined policies that can be directly used in IAM. You can also create custom policies and use them to supplement system-defined policies, implementing more refined access control. Actions supported by policies are specific to APIs. The following are common concepts related to policies:

  • Permission: A statement in a policy that allows or denies certain operations.
  • APIs: REST APIs that can be called in a custom policy
  • Actions: Added to a custom policy to control permissions for specific operations
  • Related actions: Actions which a specific action depends on to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the dependent actions.
  • IAM projects or enterprise projects: Type of projects in which policies can be used to grant permissions. A policy can be applied to IAM projects, enterprise projects, or both. Policies that contain actions for both IAM and enterprise projects can be used and take effect for both IAM and Enterprise Project Management Service (EPS). 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.