Real-world Impact: Amazon FSx Case Studies

The file systems are completely managed, as is already the case with this service, with latency to primary storage being in the sub-millisecond range and latency to the capacity pool being in the tens of milliseconds.

Current FSx for ONTAP scale-up file systems have a maximum throughput of 4 GBps and 192 TiB of SSD storage. They are powered by a single pair of servers in an active/passive high availability (HA) arrangement.

To provide continuous availability even in the event that an Availability Zone is unavailable, the server pair can be placed in two different Availability Zones or across different fault domains within a single Availability Zone.

ONTAP file systems powered by two to six HA pairs can now have scale-out FSx created for them. The following are the specifications for the scale-out and scale-up file systems

Using the AWS Management Console, AWS Command Line Interface (AWS CLI), or by creating code that invokes the Amazon FSx CreateFileSystem function, You can construct a scale-out file system. Using the console, you will first select Amazon FSx for NetApp ONTAP.

You select a Single-AZ deployment, type in a name, select Standard create, and enter the amount of SSD storage you want. You have three alternatives (more on that in a moment): accept the suggested throughput capacity, select a value from the menu, or enter a value to see my possibilities.

Occasionally, the console may present you with multiple choices for the same required throughput capacity. Low Throughput: You will only be able to use one HA pair if you select a plan that offers 4 GBps or less. Choosing this option is the easiest if you don’t want a high throughput.

High Storage and/or Throughput: The maximum throughput varies depending on how many HA pairs you supply. Additionally, selecting a solution with more pairs will increase your headroom for potential future increases in allocated storage.