Permissions Policies and Supported Actions

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

By default, new users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

You can grant users permissions by using roles and policies. Roles are a type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.

If you want to allow or deny the access to an API, fine-grained authorization is a good choice.

Your account has all the permissions required to call all APIs, but IAM users under your account must be assigned the required permissions. 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 creates a RabbitMQ instance using an API, the user must have been granted permissions that allow the dms:instance:create action.

Supported Actions

IAM provides system-defined policies that can be directly used. You can also create custom policies and use them to supplement system-defined policies, implementing more refined access control. Operations supported by policies are specific to APIs. The following lists 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.
IAM project or enterprise projects: type of projects for which an action will take effect. 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.

DMS for RabbitMQ supports the following actions that can be defined in custom policies. Permissions must be obtained before calling DMS APIs. For details on how to obtain permissions, visit the Identity and Access Management help center.

**Table 1** DMS for RabbitMQ actions
Permissions	APIs	Actions	IAM Project	Enterprise Project
Creating an instance	POST /v1.0/{project_id}/instances	dms:instance:create	√	√
Viewing instance details	GET /v1.0/{project_id}/instances/{instance_id}	dms:instance:get	√	√
Modifying an instance	PUT /v1.0/{project_id}/instances/{instance_id}	dms:instance:modify	√	√
Deleting an instance	DELETE /v1.0/{project_id}/instances/{instance_id}	dms:instance:delete	√	√
Modifying instance specifications	POST /v1.0/{project_id}/instances/{instance_id}/extend	dms:instance:scale	√	√
Querying all instances	GET /v1.0/{project_id}/instances	dms:instance:list	√	√
Restarting an instance	POST /v1.0/{project_id}/instances/action	dms:instance:modifyStatus	√	√
Changing instance passwords	This operation is supported only by using the console and not by calling APIs.	dms:instance:modifyAuthInfo	√	√
Resetting Instance Passwords	This operation is supported only by using the console and not by calling APIs.	dms:instance:resetAuthInfo	√	√
Querying one or more background tasks that have not been deleted	This operation is supported only by using the console and not by calling APIs.	dms:instance:getBackgroundTask	√	√
Deleting a background task	This operation is supported only by using the console and not by calling APIs.	dms:instance:deleteBackgroundTask	√	√
Changing public access bandwidth or enabling or disabling public access	This operation is supported only by using the console and not by calling APIs.	dms:instance:modify	√	√
Querying public access bandwidth	This operation is supported only by using the console and not by calling APIs.	dms:instance:get	√	√