Step 1: Create an Amazon FSx for NetApp ONTAP file system - FSx for ONTAP

Step 1: Create an Amazon FSx for NetApp ONTAP file system

The Amazon FSx console has two options for creating a file system – a Quick create option and a Standard create option. To rapidly and easily create an Amazon FSx for NetApp ONTAP file system with the service recommended configuration, use the Quick create option.

The Quick create option creates a file system with a single storage virtual machine (SVM) and one volume. The Quick create option configures this file system to allow data access from Linux instances over the Network File System (NFS) protocol. After your file system is created, you can create additional SVMs and volumes as needed, including an SVM joined to an Active Directory to allow access from Windows and macOS clients over the Server Message Block (SMB) protocol.

For information about using the Standard create option to create a file system with a customized configuration, see Creating FSx for ONTAP file systems.

To create your file system

  1. Open the Amazon FSx console at https://console.aws.amazon.com/fsx/.

  2. On the dashboard, choose Create file system to start the file system creation wizard.

  3. On the Select file system type page, choose Amazon FSx for NetApp ONTAP, and then choose Next. The Create ONTAP file system page appears. For Creation method, choose Quick create.

    
            Quick create file system details screen showing options for the file system
              name, SSD storage capacity, virtual private cloud (VPC), and storage efficiency
              features.
  4. In the Quick configuration section, for File system name - optional, enter a name for your file system. It's easier to find and manage your file systems when you name them. You can use a maximum of 256 Unicode letters, white space, and numbers, plus these special characters: + - (hyphen) = . _ (underscore) : /

  5. For Deployment type choose Multi-AZ or Single-AZ.

    • Multi-AZ file systems replicate your data and support failover across multiple Availability Zones in the same AWS Region.

    • Single-AZ file systems replicate your data and offer automatic failover within a single Availability Zone.

    For more information, see Availability and durability.

  6. For SSD storage capacity, specify the storage capacity of your file system, in gibibytes (GiBs). Enter any whole number in the range of 1,024–196,608.

    You can increase the amount of storage capacity as needed at any time after you create the file system. For more information, see Managing storage capacity.

  7. For Virtual Private Cloud (VPC), choose the Amazon VPC that you want to associate with your file system.

  8. For Storage efficiency, choose Enabled to turn on the ONTAP storage efficiency features (compression, deduplication, and compaction) or Disabled to turn them off.

  9. (Multi-AZ only) Endpoint IP address range specifies the IP address range in which the endpoints to access your file system are created.

    Choose a Quick create option for the endpoint IP address range:

    • Unallocated IP address range from your VPC – Choose this option to have Amazon FSx use the last 64 IP addresses from the VPC’s primary CIDR range as the endpoint IP address range for the file system. Note that this range is shared across multiple file systems if you choose this option multiple times.

      Note

      This option is grayed out if any of the last 64 IP addresses in a VPC's primary CIDR range are in use by a subnet.

    • Floating IP address range outside your VPC – Choose this option to have Amazon FSx use a 198.19.x.0/24 address range that isn't already used by any other file systems with the same VPC and route tables.

    You can also specify your own IP address range in the Standard create option.

  10. Choose Next, and review the file system configuration on the Create ONTAP file system page. Note which file system settings you can modify after the file system is created.

  11. Choose Create file system.

Quick create creates a file system with one SVM (named fsx) and one volume (named vol1). The volume has a junction path of /vol1 and a capacity pool tiering policy of Auto (which will automatically tier any data that hasn't been accessed for 31 days to lower-cost capacity pool storage). The default snapshot policy gets assigned to the default volume. The file system data is encrypted at rest using your default service managed AWS KMS key.