EZGH Files gives the instances in a VPC a shared file system. You create a file system in a VPC
and a mount target in one of its subnets: an address and a DNS name that every instance in the
VPC mounts over NFS 4.1. A file system grows and shrinks with what you store; there’s no size to
choose. Data is stored redundantly across servers, and a write that asks for it (fsync, or
closing the file) returns once it’s stored.
Get started
Create a file system and a mount target, and mount it.
Mount a file system
The mount command, /etc/fstab, allowed sources and firewalls.
Access points
Mount a folder of the file system as a fixed user.
Encrypt with TLS
Mount over TLS, and require it for a file system.
Share wp-content in WordPress
An autoscaling WordPress behind a load balancer, with uploads on Files.
Limits
Quotas, throughput and what happens over them.
The Files API is at https://files-api.ezghcloud.com.
Resources
| Resource | ID | What it is |
|---|---|---|
| File system | fsy_… |
The shared files. It belongs to one VPC, chosen at create |
| Mount target | fmt_… |
An address in one subnet of that VPC, with a DNS name. Clients in any subnet of the VPC can use it. One per subnet per file system |
| Access point | fap_… |
A folder of the file system, mounted on its own, optionally as a fixed POSIX user |
Each is regional and lives in a project. Clients mount from inside the VPC only: there’s no public address, and other VPCs can’t reach it.
File systems
| Field | Meaning |
|---|---|
vpc |
The VPC whose instances mount it (vpc_…). Fixed |
sizeBytes |
Bytes stored, as a string of digits. Measured about once an hour |
limits |
throughputMBps and metadataOpsPerSecond, from your quotas |
rootSquash |
true (the default): root on a client acts as an anonymous user. false: root is root |
requireTls |
true: only TLS mounts are accepted. Default false |
deletionProtection |
true: the file system can’t be deleted until it’s turned off. Default false |
status |
See Status |
UpdateFileSystem changes the name, description, tags,
rootSquash, requireTls and deletionProtection.
DeleteFileSystem deletes the file system and every file in
it. It’s refused while the file system has mount targets or access points
(409 file_system_in_use) and while deletionProtection is on (409 deletion_protected).
Status
| Status | Means |
|---|---|
creating |
It’s being created. |
available |
It’s ready. |
deleting |
It’s being deleted. |
failed |
It couldn’t be created; failure says why. Delete it. |
New statuses may appear. Creates and deletes are asynchronous: they answer 202 with an operation,
and the resource exists from then on with its ID.
Access control
Files uses IAM for the API. The actions are files.fileSystems.*, files.mountTargets.* and
files.accessPoints.* (each list, get, create, update and delete) and
files.operations.list. The managed policies are FilesFullAccess and FilesReadOnlyAccess;
ReadOnlyAccess includes Files’ list and get. Creating a file system also needs
network.vpcs.get on its VPC.
Mounting isn’t checked by IAM. Any client that can reach a mount target, and is inside its allowed sources, can mount the file system and any of its access points. Use allowed sources and your instances’ firewalls to decide who mounts.
Trails records every create, update and delete. It never records file names, paths or contents.