Permissions
If you need to assign different permissions to employees in your enterprise to access your SFS resources on Huawei Cloud, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you to securely access your Huawei Cloud resources.
With IAM, you can use your Huawei Cloud account to create IAM users, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use SFS resources but should not be allowed to delete the general-purpose file systems or perform any other high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using SFS resources.
If your Huawei Cloud account does not require individual IAM users for permissions management, skip this section.
IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see Identity and Access Management User Guide.
SFS Permissions
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 and can perform specified operations on cloud services based on the permissions.
SFS is a project-level service deployed and accessed in specific physical regions. To assign SFS permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing SFS, the users need to switch to a region where they have been authorized to use this service.
You can grant users permissions by using roles and policies.
- Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
- Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant ECS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by SFS, see Permissions Policies and Supported Actions.
The check mark (√) and cross symbol (x) indicate that an action takes effect or does not take effect for the corresponding type of projects.
Due to data caching, a role and policy involving General-Purpose File System actions will take effect 10 to 15 minutes after it is attached to a user, an enterprise project, or a user group.
| Role/Policy Name | Description | Type | Dependency |
|---|---|---|---|
| SFS3 FullAccess | Administrator permissions for General-Purpose File System. Users granted these permissions can perform all operations on general-purpose file systems. | System-defined policy | None |
| SFS3 ReadOnlyAccess | Read-only permissions for General-Purpose File System. Users granted these permissions can only view data in general-purpose file systems. | System-defined policy | None |
Table 2 lists the common operations supported by system-defined policies for General-Purpose File System.
| Operation | SFS3 FullAccess | SFS3 ReadOnlyAccess |
|---|---|---|
| Obtaining file information | √ | √ |
| Querying resources by tag | √ | √ |
| Obtaining files | √ | √ |
| Obtaining file system information | √ | √ |
| Querying tags by project | √ | √ |
| Obtaining CORS access rules of a file system | √ | √ |
| Querying resource tags | √ | √ |
| Querying site configurations | √ | √ |
| Obtaining file system limits | √ | √ |
| Obtaining file system ACL information | √ | √ |
| Querying project configurations | √ | √ |
| Obtaining the file system storage usage | √ | √ |
| Configuring file system limits | √ | × |
| Creating or updating CORS access rules for a file system | √ | × |
| Deleting project configurations | √ | × |
| Batch adding tags to a resource | √ | × |
| Creating project configurations | √ | × |
| Deleting files | √ | × |
| Creating file systems | √ | × |
| Deleting file systems | √ | × |
| Batch deleting resource tags | √ | × |
| Uploading files | √ | × |
| Deleting CORS access rules from a file system | √ | × |
| Listing files in a file system | √ | √ |
| Listing file systems | √ | √ |
| Listing project configurations | √ | √ |
| Configuring file system ACLs | √ | × |
| Deleting file system ACLs | √ | × |
Role/Policy Dependencies of the General-Purpose File System Console
| Console Function | Dependent Services | Role/Policy Required |
|---|---|---|
| Creating general-purpose file systems | VPC | The permissions of the SFS3 FullAccess policy already include the permissions of VPC ReadOnlyAccess, which are required for creating general-purpose file systems. An IAM user assigned the SFS3 FullAccess policy does not need to have the VPC ReadOnlyAccess policy assigned explicitly. |
| Querying general-purpose file system details | VPC | The permissions of the SFS3 ReadOnlyAccess policy already include the permissions of VPC ReadOnlyAccess, which are required for querying general-purpose file system details. An IAM user assigned the SFS3 ReadOnlyAccess policy does not need to have the VPC ReadOnlyAccess policy assigned explicitly. |
