---
title: "setNasVolumeAccessControl"
slug: "cli-vnas-volume-setnasvolumeaccesscontrol"
updated: 2026-10-08T05:03:25Z
published: 2026-10-08T05:03:25Z
canonical: "cli.ncloud-docs.com/cli-vnas-volume-setnasvolumeaccesscontrol"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://cli.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# setNasVolumeAccessControl

Available in VPC

Remove the access controls for an existing NAS volume instance and set them up again.

## Syntax

The `setNasVolumeAccessControl` syntax is as follows:

```
./ncloud vnas setNasVolumeAccessControl \
    --nasVolumeInstanceNo <nas-volume-instance-no> \
    --accessControlRuleList <access-control-rule-config> \
    [--regionCode <KR|SGN|JPN>] \
    [--output <json|xml>]
```

## Options

This section describes the options available when running `setNasVolumeAccessControl`.

### Required options

The following options are required for `setNasVolumeAccessControl`.

| Options | Type | Required | Description |
| --- | --- | --- | --- |
| `--nasVolumeInstanceNo` | String | Required | NAS volume instance number - Access control settings can only be configured for NAS volume instances where the volume allocation protocol type is NFS. - See [getNasVolumeInstanceList](/docs/en/cli-vnas-volume-getnasvolumeinstancelist). |
| `--accessControlRuleList` | List | Required | Access control rule list - For each rule, enter {field='value'} pairs enclosed in quotes and separated by commas. - `serverInstanceNo` (required): Server instance number to be configured for access control. See [getServerInstanceList](/docs/en/cli-vserver-server-getserverinstancelist). - `writeAccess` (optional): Write permission. `true` (default) \| `false` |

### Common options

For information about the options common to all `vnas` subcommands, see [NAS (VPC) options](/docs/en/cli-vnas#%EC%98%B5%EC%85%98).

## Examples

If the access control configuration request is successful, the configuration information for the NAS volume instance and the newly configured access-allowed server information are returned.

### Command

The command example is as follows:

```
./ncloud vnas setNasVolumeAccessControl \
    --nasVolumeInstanceNo 10234567 \
    --accessControlRuleList "serverInstanceNo='34567890', writeAccess='true'" \
    --regionCode KR \
    --output json
```

### Output

The output example is as follows:

```
{
  "setNasVolumeAccessControlResponse": {
    "totalRows": 1,
    "nasVolumeInstanceList": [
      {
        "nasVolumeInstanceNo": "10234567",
        "nasVolumeInstanceStatus": {
          "code": "CREAT",
          "codeName": "NAS creation status"
        },
        "nasVolumeInstanceOperation": {
          "code": "NULL",
          "codeName": "NAS NULL OP"
        },
        "nasVolumeInstanceStatusName": "created",
        "createDate": "2026-08-19T11:32:32+0900",
        "nasVolumeDescription": "Test NAS volume",
        "mountInformation": "192.0.2.10:/n123456_testnas01",
        "volumeAllotmentProtocolType": {
          "code": "NFS",
          "codeName": "NFS"
        },
        "volumeName": "n123456_testnas01",
        "volumeTotalSize": 536870912000,
        "volumeSize": 483183820800,
        "snapshotVolumeConfigurationRatio": 10.0,
        "snapshotVolumeConfigPeriodType": {
          "code": "DAY",
          "codeName": "Daily"
        },
        "snapshotVolumeConfigDayOfWeekType": {
          "code": "-1",
          "codeName": "Everyday"
        },
        "snapshotVolumeConfigTime": 1,
        "snapshotVolumeSize": 53687091200,
        "isSnapshotConfiguration": true,
        "isEventConfiguration": false,
        "regionCode": "KR",
        "zoneCode": "KR-2",
        "nasVolumeServerInstanceNoList": [
          "34567890"
        ],
        "isEncryptedVolume": false,
        "nasVolumeInstanceCustomIpList": [],
        "isReturnProtection": false
      }
    ],
    "requestId": "",
    "returnCode": "0",
    "returnMessage": "success"
  }
}
```