Mount points
A Mount Point connects external file-based storage directly to a workspace file system. Unlike Data Buckets, which create point-in-time snapshots that are replicated to the cluster, Mount Points provide live access to the storage. Changes made inside the workspace are immediately visible to other workspaces sharing the same Mount Point, enabling real-time collaboration on shared files and datasets.
Mount Points are useful when teams need to:
- Share large datasets (for example, ML training data or model artifacts) without duplicating them across workspaces.
- Collaborate in real time on shared files without a manual snapshot-and-publish workflow.
- Access terabytes of data instantly, without waiting for replication.
Note
Mount Points are available only when a platform administrator has enabled the feature in System Configuration > Integrations > Mount Point Storage. See Enable Mount Points for details.
Note
Mount Points are not supported in multi-region configurations.
View Mount Points
Mount Points configured for the current project are displayed on the Resources > Mount Points page.
Each Mount Point displays the following information:
- Name — A descriptive label for the Mount Point.
- Type — The storage type (for example, File).
- Status — The current state of the Mount Point (for example, Ready).
- Container Name / Server Address — The storage account or server address for the Mount Point.
-
Default Mount Path — The file system path where the share is mounted inside the workspace (for example,
/mnt/shared-data). - Actions — View details or manage the Mount Point.
Add a Mount Point
Requires the Resources permission set to Manage.
To add a Mount Point, select Add Mount Point on the Resources > Mount Points page.
First, select a Storage Provider from the dropdown:
- Azure Files (Create New) — Provisions a new Azure file share.
- Azure Files (Attach Existing) — Connects to an existing Azure file share.
- AWS (Amazon EFS / Amazon S3 Files) Create New — Provisions new AWS-backed shared storage from an eligible storage class.
- AWS (Amazon EFS / Amazon S3 Files) Attach Existing — Connects to existing Amazon Elastic File System (EFS) or Amazon S3 Files storage prepared by your infrastructure team.
Azure Files (Create New)
Provide the following information:
- Name — A descriptive name to identify the Mount Point.
- Storage Class — Select a storage class from the available options.
-
Default Mount Path — The path where the share is mounted inside the workspace file system. The path is prefixed with
/mnt/(for example, enteringdataresults in/mnt/data). - Volume Capacity — The size of the file share in GB.
- Access Permissions — Select Read/Write or Read Only.
- Attach Asset Information (optional) — Add metadata to classify the Mount Point.
Azure Files (Attach Existing)
When attaching an existing Azure file share, provide a Name and select a Connection Method:
-
Manual Connection — Enter the storage credentials directly:
- Access Key — The storage account access key.
- File Share Name — The name of the file share to mount.
Then configure the Default Mount Path and Access Permissions as described above.
AWS (Amazon EFS / Amazon S3 Files) Create New
When creating a new AWS-backed Mount Point, select a storage class that represents either Amazon EFS or Amazon S3 Files. The storage class determines the backing service and must be configured by an administrator before project owners can use it.
Provide the following information:
- Name — A descriptive name to identify the Mount Point.
- Storage Class — Select an eligible Amazon EFS or Amazon S3 Files storage class.
-
Default Mount Path — The path where the storage is mounted inside the workspace file system. The path
is prefixed with
/mnt/. - Volume Capacity — The requested size for the Mount Point.
- Access Permissions — Select Read/Write or Read Only.
- Attach Asset Information (optional) — Add metadata to classify the Mount Point.
Note:
Create-new AWS Mount Points are provisioned with read/write storage. Choose read-only access when attaching the Mount Point to a workspace if users should not modify the shared data from that workspace.
AWS (Amazon EFS / Amazon S3 Files) Attach Existing
Use attach existing when an infrastructure team has already created the file system or access point that the project should use.
Provide the following information:
- Name — A descriptive name to identify the Mount Point.
- Backend — Select Amazon EFS or Amazon S3 Files.
- File system ID — Enter the AWS file system identifier.
- Access point ID — Enter the access point identifier when required for the selected backend.
- SubPath (optional) — Mount a specific directory within the backing storage.
- Default Mount Path — The path where the storage is mounted inside the workspace file system.
- Access Permissions — Select Read/Write or Read Only.
For Amazon EFS, SecurSpaces uses encrypted mount options for eligible storage classes. If a required storage class or access point is not available, ask your platform administrator to review the AWS Mount Point storage configuration.
AWS storage classes and existing file systems are prepared by your platform administrator outside of the platform. If the AWS options are missing, or an existing file system you expect is not offered, see Prepare AWS storage for Mount Points.
Note
Editing and deleting Mount Points is available when the Mount Point is not in use by a live workspace, workspace template, or a deleted workspace that can still be restored.
Attach a Mount Point to a workspace
You can attach one or more Mount Points to a workspace during workspace creation or when creating a workspace template.
Mount Points appear in the Resource Access step alongside other resource types such as GitHub, GitLab, Secrets, and Connected Services.
When attaching a Mount Point:
- Expand the Mount Points section in the Resource Access step.
- Select a Mount Point from the Repository dropdown.
- Optionally, specify a Source SubPath to mount a specific subdirectory of the file share.
- Review or customize the Mount Path — the location in the workspace file system where the share is accessible. The path is prefixed with
/mnt/. - Review the Access Permissions assigned to the Mount Point.
- Select Attach Repository to add the Mount Point to the workspace.
Attached Mount Points are listed under Configured Repositories below the attachment form.
Important
Each Mount Point in a workspace must use a unique mount path. If a path conflict is detected, the system displays an error and prevents the workspace from being created until the conflict is resolved.
Note
Mount Points can only be added in the primary region. If the workspace is configured for a non-primary region, the Mount Points section is disabled.
Mount Points in workspace templates
When you create or update a workspace template, you can pre-configure Mount Points in the same way as during workspace creation. Workspaces created from the template automatically inherit the configured Mount Points and their mount paths.
Developers creating a workspace from a template can still customize the mount path for each attached Mount Point before launching the workspace.