Getting started with Amazon FSx for NetApp ONTAP

Learn how to get started using Amazon FSx for NetApp ONTAP. This getting started exercise includes the following steps.

Setting up FSx for ONTAP

Before you use Amazon FSx for the first time, complete the following tasks:

1. Sign up for an AWS account

2. Create a user with administrative access

Topics

• Sign up for an AWS account
• Create a user with administrative access
• Next step

Sign up for an AWS account

If you do not have an AWS account, complete the following steps to create one.

To sign up for an AWS account

1. Open https://portal.aws.amazon.com/billing/signup.

2. Follow the online instructions.

   Part of the sign-up procedure involves receiving a phone call and entering a verification code on the phone keypad.

   When you sign up for an AWS account, an AWS account root user is created. The root user has access to all AWS services and resources in the account. As a security best practice, assign administrative access to a user, and use only the root user to perform tasks that require root user access.

AWS sends you a confirmation email after the sign-up process is complete. At any time, you can view your current account activity and manage your account by going to https://aws.amazon.com/ and choosing My Account.

Create a user with administrative access

After you sign up for an AWS account, secure your AWS account root user, enable AWS IAM Identity Center, and create an administrative user so that you don't use the root user for everyday tasks.

Secure your AWS account root user

1. Sign in to the AWS Management Console as the account owner by choosing Root user and entering your AWS account email address. On the next page, enter your password.

   For help signing in by using root user, see Signing in as the root user in the AWS Sign-In User Guide.

2. Turn on multi-factor authentication (MFA) for your root user.

   For instructions, see Enable a virtual MFA device for your AWS account root user (console) in the IAM User Guide.

Create a user with administrative access

1. Enable IAM Identity Center.

   For instructions, see Enabling AWS IAM Identity Center in the AWS IAM Identity Center User Guide.

2. In IAM Identity Center, grant administrative access to a user.

   For a tutorial about using the IAM Identity Center directory as your identity source, see Configure user access with the default IAM Identity Center directory in the AWS IAM Identity Center User Guide.

Sign in as the user with administrative access

• To sign in with your IAM Identity Center user, use the sign-in URL that was sent to your email address when you created the IAM Identity Center user.

  For help signing in using an IAM Identity Center user, see Signing in to the AWS access portal in the AWS Sign-In User Guide.

Assign access to additional users

1. In IAM Identity Center, create a permission set that follows the best practice of applying least-privilege permissions.

   For instructions, see Create a permission set in the AWS IAM Identity Center User Guide.

2. Assign users to a group, and then assign single sign-on access to the group.

   For instructions, see Add groups in the AWS IAM Identity Center User Guide.

Next step

To get started using FSx for ONTAP see Getting started with Amazon FSx for NetApp ONTAP for instructions to create your Amazon FSx resources.

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 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. You can also add additional high-availability (HA) pairs depending on the deployment type that you choose and how many HA pairs you add at creation.

For information about using the Standard create option to create a file system with a customized configuration, and for using the AWS CLI and API, see Creating 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.

4. For Creation method, choose Quick create.

5. 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) : /

6. 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, durability, and deployment options.

   Note

   The latest generation FSx for ONTAP file system that is available for your AWS Region is chosen by default. You can specify the generation of your file system (in available AWS Regions) with the Standard create option. For more information, see Creating file systems.

7. For SSD storage capacity, specify the storage capacity of your file system, in gibibytes (GiB). Enter any whole number in the range of 1,024–1,048,576. For more information, see To create a file system (console).

   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.

8. For Throughput capacity, Amazon FSx automatically provides a recommended throughput capacity based on your SSD storage. You can also choose your file system's throughput (up to 73,728 MBps depending on the deployment type and amount of HA pairs).

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

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

11. (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

      • Each file system that you create consumes two IP addresses from this range—one for the cluster, and one for the first SVM. The first and last IP addresses are also reserved. For every additional SVM, the file system consumes another IP address. For example, a file system that hosts 10 SVMs uses 11 IP addresses. Additional file systems work in the same way. They consume the two initial IP addresses, plus one for each additional SVM. The maximum number of file systems using the same IP address range, each with a single SVM, is 31.

      • 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.

12. 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.

13. 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.

Mounting your file system from an Amazon EC2 Linux instance

You can mount your file system from an Amazon Elastic Compute Cloud (Amazon EC2) instance. This procedure uses an instance running Amazon Linux 2.

To mount your file system from Amazon EC2

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. Create or select an Amazon EC2 instance running Amazon Linux 2 that is in the same virtual private cloud (VPC) as your file system. For more information about launching an instance, see Step 1: Launch an instance in the Amazon EC2 User Guide.

3. Connect to your Amazon EC2 Linux instance. For more information, see Connect to your Linux instance in the Amazon EC2 User Guide.

4. Open a terminal on your Amazon EC2 instance using secure shell (SSH), and log in with the appropriate credentials.

5. Create a directory on your Amazon EC2 instance to use as the volume's mount point with the following command. In the following example, replace mount-point with your own information.

   $ sudo mkdir /mount-point

6. Mount your Amazon FSx for NetApp ONTAP file system to the directory that you created. Use a mount command similar to the example that follows. In the following example, replace the following placeholder values with your own information.

   • nfs_version – The NFS version you are using; FSx for ONTAP supports versions 3, 4.0, 4.1, and 4.2.

   • nfs-dns-name – The NFS DNS name of the storage virtual machine (SVM) in which the volume you are mounting exists. You can find the NFS DNS name in the Amazon FSx console by choosing Storage virtual machines, then choosing the SVM on which the volume you are mounting exists. The NFS DNS name is found on the Endpoints panel.

   • volume-junction-path – The junction path of the volume that you're mounting. You can find a volume's junction path in the Amazon FSx console on the Summary panel of the Volume details page.

   • mount-point – The name of the directory that you created on your EC2 instance for the volume's mount point.

   sudo mount -t nfs -o nfsvers=nfs_version nfs-dns-name:/volume-junction-path /mount-point

   The following command uses example values.

   sudo mount -t nfs -o nfsvers=4.1 svm-abcdef1234567890c.fs-012345abcdef6789b.fsx.us-east-2.amazonaws.com:/vol1 /fsxN

If you have issues with your Amazon EC2 instance (such as connections timing out), see Troubleshoot EC2 instances in the Amazon EC2 User Guide.

Clean up resources

After you have finished this exercise, you should follow these steps to clean up your resources and protect your AWS account.

To clean up resources

1. On the Amazon EC2 console, terminate your instance. For more information, see Terminate Your Instance in the Amazon EC2 User Guide.

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

3. On the Amazon FSx console, delete all of your FSx for ONTAP volumes that are not root volumes of your SVM. For more information, see Deleting volumes.

4. Delete all of your FSx for ONTAP SVMs. For more information, see Deleting storage virtual machines (SVM).

5. On the Amazon FSx console, delete your file system. When you delete a file system, all automatic backups are deleted automatically. However, you still must delete any manually created backups. The following steps outline this process.

   1. From the console dashboard, choose the name of the file system that you created for this exercise.

   2. For Actions, choose Delete file system.

   3. In the Delete file system dialog box, enter the ID of the file system that you want to delete in the File system ID box.

   4. Choose Delete file system.

   5. While Amazon FSx deletes the file system, its status in the dashboard changes to DELETING. Once the file system is deleted, it no longer appears in the dashboard. Any automatic backups are deleted along with the file system.

   6. Now you can delete any manually created backups for your file system. From the left-side navigation, choose Backups.

   7. From the dashboard, choose any backups that have the same File system ID as the file system that you deleted, and choose Delete backup. Be sure to retain the final backup, if you created one.

   8. The Delete backups dialog box opens. Keep the check box selected for the IDs of the backups that you want to delete, and then choose Delete backups.

   Your Amazon FSx file system and any related automatic backups are now deleted, along with any manual backups that you chose to delete as well.