If you need to have a CFS instance shared by multiple CVM instances in different AZs in the same region, you can configure the CVM and CFS instances into the same VPC to achieve cross-AZ access to resources.
For example, assume that there is a CVM instance in Guangzhou Zone 1 that needs to use CFS, but file systems cannot be directly created in Guangzhou Zone 1 as the resources are sold out there.
If the CVM instance is in the "Guangzhou Zone 1" subnet of a VPC, you can log in to the VPC Console to create a subnet whose AZ is "Guangzhou Zone 2" for the VPC.
After the subnet is successfully created, go back to the CFS Console and select this VPC and the subnet you just created to create resources in Guangzhou Zone 2. The CFS file system can be directly mounted to the CVM instance in the subnet of Guangzhou Zone 1 in this VPC. For more information, please see Using CFS File Systems on Linux Clients.
CFS supports the following scenarios for resource access.
You can achieve resource access across the CVM instances distributed in VPC-A/VPC-B and CFS instance distributed in VPC-C by configuring a "peering connection". For more information, please see Configuring the Route to Peering Connection.
If you need to have a CFS instance shared by multiple CVM instances distributed in the basic network and a VPC, you can create a CFS file system in the VPC.
- Currently, CFS instances in the basic network cannot be connected to CVM instances in VPCs.
- The client and CFS instance are in the basic network and a VPC, respectively, but they cannot be connected if they are in different regions.