This page outlines the key parameters and operational limits of Nasuni Data Service (NDS) for AWS. These values reflect current product behavior and are intended to help customers plan and optimize their use of NDS.
Operational Boundaries
Read-only access - Data cannot be added, modified, or deleted via NDS.
Volume-level authentication - Access is granted at the container/volume scope.
ACLs as metadata only - File permissions/ACLs are presented in metadata but are not enforced by NDS.
Supported AWS Regions
NDS for AWS is deployed in the following AWS regions:
ap-northeast-1
ap-northeast-2
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
eu-north-1
eu-west-1
eu-west-2
eu-west-3
sa-east-1
us-east-1
us-east-2
us-west-1
us-west-2
Large File Downloads
Condition | Limit / Guidance |
|---|---|
Single Get Object request | ≤ 250 MB / 262,144,000 bytes |
Files > 250 MB | Download in parts with HTTP Range headers |
Example (500 MB file):
First request:
Range: bytes=0-262144000 (first 1 GB chunk)Second request:
Range: bytes=262144001-524288000 (remaining)
Connectivity Requirements
Outbound traffic over SSL/443 must be allowed to the UaaS/NDS deployment from the Nasuni Management Console (NMC) and the volume owner Edge Appliances for the target volume or volumes.
Traffic over SSL/443 must also be allowed between the UaaS/NDS deployment and the AWS S3 bucket/Azure Storage Account backing the target Nasuni volume or volumes. Public access on the storage accounts must be unrestricted, unless the deployment is within a VPC on AWS.