EFS Mount with Access Point
This article provides the steps to configure Amazon Elastic File System (EFS) with access points for an Amazon EKS cluster. It includes EFS file system creation, access point configuration, PersistentVolume and PersistentVolumeClaim updates, and Helm chart configuration. This setup enables shared persistent storage access across OvalEdge UI and Job pods deployed in Kubernetes environments.
Prerequisites
Ensure the following prerequisites are met before starting the configuration:
AWS account access is available
Read and write permissions are available for Amazon EFS
Configure the Amazon EKS cluster before starting the EFS integration steps.
Helm is installed and configured
Install the EFS CSI driver in the Amazon EKS cluster.
Required Helm charts are available for deployment
Create an Amazon EFS File System
Log in to the AWS Management Console.
Navigate to the Amazon EFS service.
Click Create file system.

Click Customize to configure the EFS settings.

Provide the EFS file system name.

To select Network Configuration, perform the following actions:
Select the required VPC
Select the required Security Groups

To create a file system, click Next and then click Create.

Create EFS Access Points
Open Access points by performing the following actions:
Select the created EFS file system
Click Access points

Click Create access point.

Provide a name for the Access point and specify the root directory path as "/any-name".
Under "POSIX user," set:
USERID: 777
Group ID: 777
Secondary GroupID: 777
Set permissions for the root directory:
OWNER USER ID: 777
OWNER GROUP ID: 777
Access point: 777
Follow the same configuration as shown in the following screenshot


Repeat the same process to create access points for the following directories:
third-party-jars (csp-lib.jar, lineage.jar, required jars)
Oelogs
Certs
esdata
Update Helm Charts
Navigate to the Helm chart directory
Update the PersistentVolume and PersistentVolumeClaim YAML files with the EFS file system ID and access point ID obtained from the EFS.
No additional storage class configuration is required if the storage class already exists in the templates.
Configure JARS
Persistent Volume Replace <fs-filesystem_ID> and <AccessPointID> with the actual EFS file system ID and access point ID.
PersistentVolumeClaim
Configure Certs
Persistent Volume Replace <fileSystem-id> & <AccessPointID> with the actual file system ID and access point ID of "certs" from EFS.
PersistentVolumeClaim
Configure Files
Persistent Volume Replace <fileSystem-id> & <AccessPointID> with the actual file system ID and access point ID of "files" from EFS.
PersistentVolumeClaim
Attach the PersistentVolumeClaims to the UI and Job pod deployment YAML files.
Install Updated Helm Charts
Navigate to Helm Chart Directory
Open the directory containing the updated Helm charts.
Run the following command:
This command deploys the application with the updated EFS PersistentVolume and PersistentVolumeClaim configurations.
Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.
Last updated
Was this helpful?

