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 resources 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 IAM Service Overview.

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.

Table 1 lists all the system-defined roles and policies supported by SFS.

**Table 1** System permissions for SFS Capacity-Oriented
Role/Policy Name	Description	Type	Dependency
SFS FullAccess	Administrator permissions for SFS. Users granted these permissions can perform all operations on file systems.	System-defined policy	None
SFS ReadOnlyAccess	Read-only permissions. Users granted these permissions can only view file system data.	System-defined policy	None
SFS Administrator	Permissions include: Creating, deleting, querying, and modifying file systems Adding, modifying, and deleting access rules of file systems Creating, querying, and deleting file system tags Expanding and shrinking the capacity of a file system Querying availability zones Read-only permissions on all cloud services if the Tenant Guest policy is assigned	System-defined role	Tenant Guest role needs to be assigned in the same project.

Table 2 lists the common operations supported by system-defined policies for SFS Capacity-Oriented.

**Table 2** Common operations supported by each system-defined policy of SFS Capacity-Oriented
Operation	SFS FullAccess	SFS ReadOnlyAccess	SFS Administrator
Creating a file system	√	x	√
Querying a file system	√	√	√
Modifying a file system	√	x	√
Deleting a file system	√	x	√
Adding an access rule of a file system (Adding a VPC or adding an authorized address to a file system)	√	x	√
Modifying an access rule of a file system (Modifying the VPC or authorized address of a file system).	√	x	√
Deleting an access rule of a file system (Deleting the VPC or authorized address of a file system).	√	x	√
Expanding the capacity of a file system	√	x	√
Shrinking the capacity of a file system	√	x	√
Creating file system tags	√	x	√
Querying file system tags	√	√	√
Deleting file system tags	√	x	√
Querying availability zones	√	√	√

Table 3 lists all the system-defined roles and policies supported by SFS Turbo.

**Table 3** System-defined roles and policies supported by SFS Turbo
Role/Policy Name	Description	Type	Dependency
SFS Turbo FullAccess	Administrator permissions for SFS Turbo. Users granted these permissions can perform all operations on SFS Turbo file systems.	System-defined policy	None
SFS Turbo ReadOnlyAccess	Read-only permissions for SFS Turbo. Users granted these permissions can only view SFS Turbo file system data.	System-defined policy	None

Table 4 lists all the system-defined roles and policies supported by General Purpose File System.

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.

**Table 4** System-defined roles and policies supported by General Purpose File System
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 5 lists the common operations supported by system-defined policies for General Purpose File System.

**Table 5** Common operations supported by each system-defined policy of General Purpose File System
Operation	SFS3 FullAccess	SFS3 ReadOnlyAccess
Obtaining file system lifecycle rules	√	√
Querying resources by tag	√	√
Obtaining file system information	√	√
Querying tags by project	√	√
Querying tags of a resource	√	√
Obtaining file system limits	√	√
Obtaining file system ACL information	√	√
Obtaining the file system storage usage	√	√
Configuring file system limits	√	×
Batch Adding tags to a resource	√	×
Creating a file system	√	×
Deleting a file system	√	×
Batch deleting tags from a resource	√	×
Setting/Deleting the file system lifecycle rules	√	×
Querying file systems	√	√
Configuring a file system ACL	√	×
Deleting a file system ACL	√	×

Role/Policy Dependencies of the SFS Turbo Console

**Table 6** Role/Policy dependencies of the SFS Turbo console
Console Function	Dependent Services	Role/Policy Required
Creating a file system	VPC Billing Center DSS ECS	The permissions of the SFS Turbo FullAccess policy already include the permissions of VPC FullAccess, which are required for creating file systems. An IAM user assigned the SFS Turbo Full Access policy does not need to have the VPC FullAccess policy assigned explicitly. To create yearly/monthly file systems, the BSS Administrator policy is required. To create file systems in dedicated projects, the DSS FullAccess and ECS FullAccess policies are required.
Querying file system details	VPC	The permissions of the SFS Turbo ReadOnlyAccess policy already include the permissions of VPC ReadOnlyAccess, which are required for querying file system details. An IAM user assigned the SFS Turbo ReadOnlyAccess policy does not need to have the VPC ReadOnlyAccess policy assigned explicitly.
Creating a vault at the OBS backend	OBS	To create vaults at the OBS backend, the OBS Administrator policy is required.

Role/Policy Dependencies of the General Purpose File System Console

**Table 7** Role/Policy dependencies of the General Purpose File System console
Console Function	Dependent Services	Role/Policy Required
Creating a general purpose file system	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.