Permissions and Supported Actions

This chapter describes fine-grained permissions management for your ROMA Connect using the Identity and Access Management (IAM) service. If your Huawei Cloud account does not need individual IAM users, you may skip this chapter.

By default, new IAM 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. After authorization, the user can perform specified operations on ROMA Connect based on the permissions.

You can grant users their 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.

A cloud 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 who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user queries ROMA Connect instances using an API, the user must have been granted permissions that allow the roma:instances:get action.

Supported Actions

ROMA Connect 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. 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 by a user who has been granted specific permissions.
• Action: Specific operations that are allowed or denied.
• Related actions: Actions on which a specific action depends to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the dependent actions.
• IAM or enterprise projects: Type of projects for which an action will take effect. Policies that contain actions for both IAM and enterprise projects can be used and take effect for both IAM and Enterprise Management. Policies that only contain actions for IAM projects can be used and only take effect for IAM. For details about the differences between IAM and enterprise projects, see What Are the Differences Between IAM and Enterprise Management?

The check mark (√) and cross symbol (x) respectively indicate that an action takes effect or does not take effect for the corresponding type of projects.

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

• Public Resource Permissions
• Data Integration Permissions
• Device Integration Permissions