Docs

Big Data File Storage

Manage VPCs for instances

Add VPC

A file storage instance can simultaneously provide file storage and acceleration services for multiple services, and each service may use a different VPC. Therefore, CloudFS supports binding multiple VPCs to a file storage instance, making it more convenient for services that need to access CloudFS to perform read and write operations. CloudFS supports manually adding VPCs, and VPCs can also be automatically added when products such as Serverless Flink and Spark associate with CloudFS.

Notice

A maximum of 3 VPCs can be added to a file storage instance. When the maximum number is reached, no additional VPCs can be added.

If any VPC in the file storage instance is in the mounting or unmounting state, further mounting and unmounting operations cannot be performed, and a message will indicate that the file storage instance status is incorrect.

For file storage mode (HDFS) instances, the cache acceleration feature must be enabled before VPCs can be added.

Prerequisites

Before adding a VPC to a file storage mode (HDFS) instance, the cache acceleration feature must be enabled; otherwise, an error will be prompted. For instructions on enabling cache acceleration, see Enable cache acceleration.

VPCs, subnets, and security groups must be created in advance. For details, see Create a private network, Create a subnet, and Create a security group.

Manually add VPC

You can manually add a VPC to a file storage instance. Manually added VPCs are displayed as Custom in the service name field.

In the top menu bar, select the target Region.

In the left navigation pane, select File storage list and click the name of the target file storage instance.

On the instance details page, click the Private network tab, then click Add private network.

In the Add private network dialog box, select the private network, subnet, and security group, then click OK.

tip

When selecting a VPC, you may encounter gray VPCs that cannot be selected. This is because the network segment of that VPC conflicts with the network segment of a currently bound VPC.

When selecting a subnet, you can set to allow all subnets within the entire VPC to access the instance.

Wait for the VPC to be added.

After submitting the request to add a VPC, the VPC is displayed as Mounting. Once the addition is complete, it is displayed as Normal. At the same time, you can view information such as the service name (Custom), status, private network, subnet, security group, time added, and other information.

Automatically add a VPC

When products such as Serverless Flink and Spark are associated with CloudFS, a VPC is automatically added. The automatically added VPC is displayed as the specific service name, such as Flink-flink01.

Last updated: 2026.02.02 11:17:06