Audience
This guide is intended for the IT architect or person planning the deployment of Web Access to provide remote access and file sharing.
This guide applies to Nasuni Edge Appliance 10.1 and higher.
Introduction
Web Access provides remote file access and secure file sharing for the Nasuni Edge Appliance.
Deployment
The Web Access application runs within a Nasuni Edge Appliance (NEA).
Considerations include the following:
The Web Access application is designed to be accessed by remote and distributed users over the Internet, without the need for a VPN.
Web Access requires port 443 to be open from the internet (inbound access). For more information, see Firewall and Port Requirements.
Additionally, an Application Proxy can be used. For more information, see Azure Entra ID Application Proxy.
Nasuni recommends enabling Web Access on a dedicated Nasuni Edge Appliance (NEA) and managing it through a Nasuni Management Console (NMC). A dedicated NEA provides easier workload management and allows for deployment outside the office, such as in a data center.
Sizing
Technical Specifications | Small | Medium | Large |
|---|---|---|---|
Max Users | 1000 | 2000 | 4000 |
VM Type |
|
| Azure - F32s v2 AWS - c6id.8xlarge GCP - c2d-highcpu-32 |
CPU (min) | 8 | 16 | 32 |
RAM (min) | 16 | 32 | 64 |
Disk Type * Azure | Premium SSD gp3 SSD Persistent | Premium SSD gp3 SSD Persistent | Premium SSD gp3 SSD Persistent |
Cache Disk Capacity (GiB) | 2000 | 2000 | 2000 |
COW Disk Capacity (GiB) | 256 GiB | 256 GiB | 256 GiB |
NFS Exports
To access data in an NFS export, you must enable the SMB (CIFS) protocol for the NFS volume in order to create a share. For more information, see Using Multiple Protocols.