Section | Field | Required | Meaning |
Basic Configurations | File System Name | Yes | Specify a custom name for the file system. |
| Region | Yes | Select the region where the CFS file system will reside. |
| Availability Zone | Yes | Select the AZ for which you want to create a CFS file system. |
Storage Class | Architecture Type | No | For quickly switching between file system types suitable for different scenarios. |
| Storage Class | Yes | You can flexibly choose according to actual needs. For file types, refer to Storage Types and Performance Specifications. For published prices, see Pricing Overview. Note that: If the product type you need to create is labeled Application for Usage, please click to submit a ticket. You must apply for allowlist account permissions before you can continue creating. If the product type displays Unsupported Yet, it indicates that this AZ does not currently support creating this product type. It is recommended to switch to another AZ to try creating. |
| Protocol | Yes | Select the protocol type for the file system: NFS or SMB. NFS protocol is more suitable for Linux/Unix clients. SMB protocol is more suitable for Windows clients. The Turbo series only supports use by private clients and does not require selecting a file system protocol. |
| Metadata Type | Yes | Only Turbo series needs to select metadata type. You can choose a more suitable metadata type based on actual business scenarios. For details, see Turbo File System Metadata Type. |
| Storage Usage | Yes | Only Turbo series requires filling in storage capacity. Turbo series adopts a dedicated cluster architecture, thus establishing fundamental rules for cluster scale and scale-out mechanisms: Standard Turbo: The initial minimum cluster size is 20TiB, with subsequent scaling steps of 10TiB; High-Performance Turbo: The initial minimum cluster size is 10TiB, with subsequent scaling steps of 10TiB. |
| Auto scaling policy | No | Only Turbo series provides automatic scaling. The automatic scaling policy can automatically trigger scaling when the capacity threshold is reached, mitigating the risk of capacity overrun. |
Snapshots | Data Source | No | File systems can be created from file system snapshots. Snapshots are a data backup method provided by Tencent Cloud, which generates a complete and independently usable data replica for a specified file system. The lifecycle of this replica is independent of the source file system. File systems created based on snapshots contain all data from the snapshot at the moment of creation. Snapshot Type and File System Series Correspondence: General series snapshots: Only support serving as data sources for Standard and High-Performance file systems. Turbo series snapshots: Only support serving as data sources for Standard Turbo and High-Performance Turbo file systems. Note: Standard (Enhance) and High-Performance (Enhance) file systems currently do not support the snapshot feature. |
| Scheduled snapshot | No | You can configure scheduled snapshots for the file system, which can be restored to recover abnormal data caused by accidental deletion by users, virus infections, and so on. |
Network and Permission | Select Network | Yes | Specify the VPC and subnet where the file system resides. Instances within the same VPC can mount and access the file system. For the creation process, refer to VPC - Network Planning. |
| Permission Group | Yes | Each file system must be bound to a permission group, which defines an allowlist of authorized clients and their read and write permissions. For details on permission group settings, see Permission Management. |
| Network Type | Yes | Required only for the Turbo series. When a Turbo-type file system is created, the CCN network solution is recommended. If you need to use a VPC network, see Turbo File System Network Selection to plan and apply. |
| CCN Instance | Yes | Required only for the Turbo series. Select an existing CCN instance or create a new one. For more information, see Cloud Connect Network. |
| Turbo IPv4 CIDR | Yes | Required only for the Turbo series. This field reserves IP address ranges for Turbo creation and future scaling. The CIDR block must meet the following conditions: The selected CIDR block must not conflict with the address ranges of other instances in the cloud that need to communicate with Turbo; To ensure sufficient IP addresses, the subnet mask range should be between /16 - /24 (such as 10.0.0.0/24). |
Other Settings | Encryption | No | You can optionally enable data encryption for the file system. Due to data encryption and decryption, this feature may cause performance degradation. Consider carefully whether to enable it. For details, see Data Encryption. Encryption is supported only during file system creation. An encrypted file system cannot be converted back to unencrypted storage after creation. Note: This feature is currently available only through whitelist access. To request access, submit a ticket to contact us. |
| Tag | No | If you already have a tag, you can add it to the new file system here. If you don't have a tag, create the required tag in the Tag Console and then bind it to the file system. You can also add tags to the file system after creation. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback