Mount AWS Elastic File System (NFS) – Valohai Help

This feature is available for customers who are using their own cloud or on-premises workers.

Mounting gives you direct access to the network file system like AWS EFS without having to download the files on your machine.

Valohai does not version or keep track of the changes made inside the mounted file system. The files that are created, edited, or deleted will not be versioned as part of a Valohai execution.

NFS mounts are not version controlled

We strongly recommend using the Valohai inputs and outputs system, as they are versioned as a part of the execution.

You can mount a filesystem to access a large dataset, run preprocessing operations, and output the processed dataset into Valohai Outputs before it’s used further in the pipeline. This way the snapshot of the preprocessed data will be versioned.

Define a mount in YAML

You can either use an existing or create a new AWS EFS.

Create your EFS in the same VPC where all Valohai resources are in or setup VPC peering between the two VPCs
Make sure the security group of your EFS has an inbound rule to accept traffic from the Valohai workers (sg-valohai-workers)
Valohai will connect to the EFS over DNS name or IP address. Make sure the VPC has DNS hostnames and DNS resolution enabled, if you’re connecting over DNS name.

Example valohai.yaml configuration:

- step:
    name: mount-sample
    image: python:3.8
    command:
        - ls -la /my-data
    mounts:
        - destination: /my-data
          source: fs-1234aa62.efs.eu-west-1.amazonaws.com:/
          type: nfs
          readonly: false

Mounts are defined for each environment separately. Contact Valohai, if you see an error mounts were ignored due to environment configuration. in your execution logs.

Define a mount in YAML

Related articles