Scalable File Service
Scalable File Service
- What's New
- Function Overview
- Service Overview
- Getting Started
- User Guide
- Best Practices
- API Reference
- SDK Reference
- Troubleshooting
-
FAQs
- Concepts
- Specifications
- Restrictions
- Networks
- Billing
-
Others
- How Do I Access a File System from a Server?
- How Do I Check Whether a File System on a Linux Server Is Available?
- What Resources Does SFS Occupy?
- Can a File System Be Accessed Across Multiple AZs?
- How Can I Migrate Data Between SFS and EVS?
- Can I Directly Access SFS from On-premises Devices?
- How Do I Delete .nfs Files?
- How Can I Improve the Copy and Delete Efficiency with an SFS Turbo File System?
- How Do Second- and Third-level Directory Permissions of an SFS Turbo File System Be Inherited?
On this page
Show all
Solution Overview
Updated on 2022-09-16 GMT+08:00
By default, an SFS Turbo file system can only be accessed by ECSs or CCEs that reside in the same VPC as the file system. If you need to use an SFS Turbo file system across VPCs, use Direct Connect, VPN, or VPC peering to enable communications between VPCs.
- Access from on premises or another cloud: Use Direct Connect or VPN.
- On-cloud, cross-VPC access using the same account in a given region: Use VPC peering.
- On-cloud, cross-account access in a given region: Use VPC peering.
- On-cloud, cross-region access: Use Cloud Connect.
Data can be migrated to SFS Turbo by using an ECS that can access the Internet.
- You can mount the SFS Turbo file system to the ECS and migrate data from the local Network Attached Storage (NAS) to the SFS Turbo file system.
- If communication cannot be enabled through file system mounting, migrate data using the ECS via the Internet.
Parent topic: Migrating Data to SFS
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
