Does the Security Group of a VPC Affect the Use of SFS?

A security group is a collection of access control rules for cloud servers that have the same security protection requirements and are mutually trusted in a VPC. After a security group is created, you can create different access rules for the security group to protect the cloud servers that are added to this security group. The default security group rule allows all outgoing data packets. Cloud servers in a security group can access each other without the need to add rules. The system creates a security group for each cloud account by default. Users can also create custom security groups by themselves.

For an SFS Turbo file system, the system automatically enables the security group ports required by the NFS protocol after the file system is created. This ensures that the SFS Turbo file system can be successfully mounted to your servers. The inbound ports required by the NFS protocol are ports 111, 2049, 2051, 2052, and 20048. If you need to change the enabled ports, go to the VPC console, choose Access Control > Security Groups, locate the target security group, and change the ports. You are advised to use an independent security group for an SFS Turbo file system to isolate it from service nodes.

For a General Purpose File System, you need to manually add the inbound and outbound rules for the security group. For details, see section "Adding a Security Group Rule" in the Virtual Private Cloud User Guide. The inbound ports required by the NFS protocol are ports 111, 2049, and 2050.

For an SFS Capacity-Oriented file system, you need to manually add inbound and outbound rules for the security group. For details, see Adding a Security Group Rule. For an SFS Capacity-Oriented file system, the inbound ports required by the NFS protocol are ports 111, 2049, 2051, and 2052. The inbound port required by the DNS server is port 53 and that required by the CIFS protocol is port 445.