Thalassa Filesystem Service (TFS)
Beta
Thalassa Filesystem Service is currently in Beta.
Thalassa Filesystem Service (TFS) provides a high-availability, multi-availability zone Network File System (NFS) service for shared storage across your infrastructure. TFS supports NFSv4 and NFSv4.1 protocols. It’s primairy use-case is file sharing between virtual machines, containers, and other workloads within your Thalassa Cloud environment.
TFS instances are deployed within your Virtual Private Cloud (VPC) and subnets. You can create multiple NFS exports from a single TFS instance. If you expose a TFS instance within your VPC, you can mount the exports from any network that can reach it, including; VPC peering, Site-to-Site connections, etc.
Key Features
| Feature | Description |
|---|---|
| High Availability | Multi-availability zone deployment ensures service continuity and data protection. |
| NFS Protocol Support | Supports NFSv4 and NFSv4.1. |
| VPC Integration | Deploy TFS instances within your VPC and subnets for network isolation. |
| Security Groups | Secure access to your TFS instances using Security Groups. |
TFS Use Cases
TFS is best for sharing files and folders between multiple virtual machines, containers, or users. Common uses include:
- Sharing application data or configuration files
- Storing media, documents, and other shared content
- Providing persistent storage for containers for cache, filesharing, etc
Not Suitable For High Performance Workloads
TFS is not intended for high-performance workloads that require low latency or high input/output operations per second (IOPs), such as databases or transactional systems. For applications that involve frequent, small, random I/O operations or demand consistent low-latency access, we recommend using Block Storage in Thalassa Cloud for optimal performance.
Deployment and Configuration
VPC and Subnet Deployment
TFS instances are deployed within your VPC and subnet configuration.
Security Groups
Secure your TFS instances by configuring Security Groups to control inbound and outbound network traffic, restrict access to specific IP addresses or subnets, and enforce network-level security policies. Ensure that Security Groups allow NFS traffic (typically TCP port 2049) only from trusted sources within your VPC or designated IP ranges.
NFS Exports
Create multiple NFS exports from a single TFS instance to:
- Organise data by application, team, or purpose
- Apply different access controls and permissions per export
- Manage storage efficiently across different use cases
Each export can be configured with specific mount options and access permissions.
Mounting TFS Exports
TFS exports can be mounted using any standard NFS client. The mounting process is consistent across different operating systems and NFS client implementations.
Linux
# Mount an NFS export
sudo mount -t nfs4 -o vers=4.1 <tfs-endpoint>:/<export-path> /mnt/nfs
# Persistent mount via /etc/fstab
<tfs-endpoint>:/<export-path> /mnt/nfs nfs4 vers=4.1,defaults 0 0macOS
# Mount an NFS export
sudo mount -t nfs -o vers=4.1 <tfs-endpoint>:/<export-path> /mnt/nfsIntegration with Other Services
TFS can be integrates with other Thalassa Cloud services:
- Virtual Machines: Mount TFS exports on VMs for shared storage across instances
- Kubernetes / CSI: Fully compatible and tested with the Kubernetes NFS CSI driver