Quotas
Following, you can find out about quotas when working with Amazon FSx for NetApp ONTAP.
Quotas that you can increase
Following are the quotas for Amazon FSx for NetApp ONTAP for each AWS account, per AWS Region, that you can increase.
Resource | Default | Description |
---|---|---|
ONTAP file systems |
100 |
The maximum number of Amazon FSx for NetApp ONTAP file systems that you can create in this account. |
ONTAP SSD storage capacity |
524,288 |
The maximum amount of SSD storage capacity (in GiB) for all Amazon FSx for NetApp ONTAP file systems that you can have in this account. |
ONTAP throughput capacity |
10,240 |
The maximum amount of throughput capacity (in MBps) for all Amazon FSx for NetApp ONTAP file systems that you can have in this account. |
ONTAP SSD IOPS |
1,000,000 |
The maximum amount of SSD IOPS for all Amazon FSx for NetApp ONTAP file systems that you can have in this account. |
ONTAP backups |
10,000 |
The maximum number of user-initiated volume backups for all Amazon FSx for NetApp ONTAP file systems that you can have in an AWS account. |
To request a quota increase
-
Open the AWS Support
page, sign in if necessary, and then choose Create case. -
For Create case, choose Account and billing support.
-
In the Case details panel make the following entries:
-
For Type choose Account.
-
For Category choose Other Account Issues.
-
For Subject enter
Amazon FSx for NetApp ONTAP service limit increase request
. -
Provide a detailed Description of your request, including:
-
The FSx quota that you want increased, and the value you want it increased to, if known.
-
The reason why you are seeking the quota increase.
-
The file system ID and region for each file system you are requesting an increase for.
-
-
-
Provide your preferred Contact options and choose Submit.
Resource quotas for each file system
The following table lists the quotas on Amazon FSx for NetApp ONTAP resources for each file system in an AWS Region.
Resource | Limit per file system |
---|---|
Minimum SSD storage capacity | 1,024 GiB per high-availability (HA) pair |
Maximum SSD storage capacity |
|
Maximum SSD IOPS | Second-generation file systems:
First-generation file systems:
|
Minimum throughput capacity |
|
Maximum throughput capacity | Second-generation file systems:
First-generation file systems:
|
Maximum number of volumes |
|
Maximum number of snapshots | 1,023 per volume3 |
Maximum number of backups | 4,091 per volume4 |
Maximum number of SVMs | Second-generation file systems with one HA pair:
Second-generation file systems with 2–12 HA pairs:
First-generation file systems:
|
Maximum number of tags | 50 |
Maximum retention period for automated backups | 90 days |
Maximum retention period for user-initiated backups | No retention limit |
Maximum number of routes supported per file system | 505 |
Note
1 On a second-generation Single-AZ file system with 12 HA pairs (6,144 MBps per HA pair). For more information, see Managing high-availability (HA) pairs.
2 To provision 4 GBps of throughput capacity, your FSx for ONTAP first-generation file system requires a configuration of the maximum SSD IOPS (160,000) and a minimum of 5,120 GiB of SSD storage capacity in a supported AWS Region. For more information about which AWS Regions support 4,096 MBps of throughput capacity, see Impact of throughput capacity on performance.
3 You can store up to 1,023 snapshots per volume at any point in time. Once you reach this limit, you must delete an existing snapshot before a new snapshot of your volume can be created.
4 You can store up to 4,091 backups per volume at any point in time. Once you reach this limit, you must delete an existing backup before a new backup of your volume can be created.
5 You can configure up to 50 routes per file system at any point in time. Once you reach this limit, you must delete an existing route before a new route can be configured. The number of routes your file system has is determined by the number of SVMs it has and the number of route tables associated with it. You can determine the existing number of routes to a file system using the following equation: (1 + number of SVMs in the file system) * (route tables associated with the file system).