Creating a volume - FSx for ONTAP

Creating a volume

You can create an FSx for ONTAP volume using the Amazon FSx console, the AWS CLI, and the Amazon FSx API, in addition to the NetApp ONTAP command line interface (CLI) and REST API.


The volume's security style is automatically set to the root volume's security style.

  1. Open the Amazon FSx console at

  2. In the left navigation pane, choose File systems, and then choose the ONTAP file system that you want to create a volume for.

  3. Choose the Volumes tab.

  4. Choose Create volume.

    The Create volume dialog box appears.

                                    The Create new volume dialog
  5. For File system, choose the file system to create the volume on.

  6. For Storage virtual machine, choose the storage virtual machine (SVM) to create the volume on.

  7. In the Volume name field, provide a name for the volume. You can use a up to 203 alphanumeric or underscore (_) characters.

  8. For Volume type, choose Read-Write (RW) to create a volume that is readable and writable or Data Protection (DP) to create a volume that is read-only and can be used as the destination of a NetApp SnapMirror or SnapVault relationship. For more information about volume types, see Volume types.

  9. For Junction path, enter a location within the file system to mount the volume. The name must have a leading forward slash, for example /vol3.

  10. For Volume size, enter any whole number in the range of 20–104857600 to specify the size in mebibytes (MiB).

  11. For Storage efficiency, choose Enabled to enable the ONTAP storage-efficiency features (deduplication, compression, and compaction). For more information, see FSx for ONTAP storage efficiency.

  12. For Capacity pool tiering policy, choose the storage pool tiering policy for the volume, which can be Auto (the default), Snapshot Only, All, or None. For more information about capacity pool tiering policies, see Tiering policies.

  13. For Snapshot policy, choose a snapshot policy for the volume. For more information about snapshot policies, see Snapshot policies.

    If you choose Custom policy, you must specify the policy's name in the custom-policy field. The custom policy must already exist on the SVM or in the file system. You can create a custom snapshot policy with the ONTAP CLI or REST API. For more information, see Create a Snapshot Policy in the NetApp ONTAP Product Documentation.

  14. Choose Confirm to create the volume.

You can monitor the update progress on the File systems detail page, in the Status column of the Volumes pane. The volume is ready for use when its status is Created.

  • To create an FSx for ONTAP volume, use the create-volume CLI command (or the equivalent CreateVolume API operation), as shown in the following example.

    aws fsx create-volume \ --volume-type ONTAP \ --name vol1 \ --ontap-configuration CopyTagsToBackups=true,JunctionPath=/vol1,SecurityStyle=NTFS, \ SizeInMegabytes=1024,SnapshotPolicy=default, \ StorageVirtualMachineId=svm-abcdef0123456789a,OntapVolumeType=RW

After successfully creating the volume, Amazon FSx returns its description in JSON format, as shown in the following example.

{ "Volume": { "CreationTime": "2022-08-12T13:03:37.625000-04:00", "FileSystemId": "fs-abcdef0123456789c", "Lifecycle": "CREATING", "Name": "vol1", "OntapConfiguration": { "CopyTagsToBackups": true, "FlexCacheEndpointType": "NONE", "JunctionPath": "/vol1", "SecurityStyle": "NTFS", "SizeInMegabytes": 1024, "SnapshotPolicy": "default", "StorageEfficiencyEnabled": true, "StorageVirtualMachineId": "svm-abcdef0123456789a", "StorageVirtualMachineRoot": false, "TieringPolicy": { "Name": "NONE" }, "OntapVolumeType": "RW" }, "ResourceARN": "arn:aws:fsx:us-east-2:111122223333:volume/fs-abcdef0123456789c/fsvol-abcdef0123456789b", "VolumeId": "fsvol-abcdef0123456789b", "VolumeType": "ONTAP" } }