Values.UpdateFileSystemOntapConfigurationSourceThe configuration updates for an Amazon FSx for NetApp ONTAP file system.
type nonrec t = {automaticBackupRetentionDays : AutomaticBackupRetentionDays.t option;dailyAutomaticBackupStartTime : DailyTime.t option;fsxAdminPassword : AdminPassword.t option;Update the password for the fsxadmin user by entering a new password. You use the fsxadmin user to access the NetApp ONTAP CLI and REST API to manage your file system resources. For more information, see Managing resources using NetApp Application.
*)weeklyMaintenanceStartTime : WeeklyTime.t option;diskIopsConfiguration : DiskIopsConfiguration.t option;The SSD IOPS (input output operations per second) configuration for an Amazon FSx for NetApp ONTAP file system. The default is 3 IOPS per GB of storage capacity, but you can provision additional IOPS per GB of storage. The configuration consists of an IOPS mode (AUTOMATIC or USER_PROVISIONED), and in the case of USER_PROVISIONED IOPS, the total number of SSD IOPS provisioned. For more information, see File system storage capacity and IOPS.
*)throughputCapacity : MegabytesPerSecond.t option;Enter a new value to change the amount of throughput capacity for the file system in megabytes per second (MBps). For more information, see Managing throughput capacity in the FSx for ONTAP User Guide. Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions: The value of ThroughputCapacity and ThroughputCapacityPerHAPair are not the same value. The value of ThroughputCapacity when divided by the value of HAPairs is outside of the valid range for ThroughputCapacity.
*)addRouteTableIds : RouteTableIds.t option;(Multi-AZ only) A list of IDs of new virtual private cloud (VPC) route tables to associate (add) with your Amazon FSx for NetApp ONTAP file system.
*)removeRouteTableIds : RouteTableIds.t option;(Multi-AZ only) A list of IDs of existing virtual private cloud (VPC) route tables to disassociate (remove) from your Amazon FSx for NetApp ONTAP file system. You can use the API operation to retrieve the list of VPC route table IDs for a file system.
*)throughputCapacityPerHAPair : ThroughputCapacityPerHAPair.t option;Use to choose the throughput capacity per HA pair, rather than the total throughput for the file system. This field and ThroughputCapacity cannot be defined in the same API call, but one is required. This field and ThroughputCapacity are the same for file systems with one HA pair. For SINGLE_AZ_1 and MULTI_AZ_1 file systems, valid values are 128, 256, 512, 1024, 2048, or 4096 MBps. For SINGLE_AZ_2, valid values are 1536, 3072, or 6144 MBps. For MULTI_AZ_2, valid values are 384, 768, 1536, 3072, or 6144 MBps. Amazon FSx responds with an HTTP status code 400 (Bad Request) for the following conditions: The value of ThroughputCapacity and ThroughputCapacityPerHAPair are not the same value for file systems with one HA pair. The value of deployment type is SINGLE_AZ_2 and ThroughputCapacity / ThroughputCapacityPerHAPair is not a valid HA pair (a value between 1 and 12). The value of ThroughputCapacityPerHAPair is not a valid value.
*)hAPairs : HAPairs.t option;Use to update the number of high-availability (HA) pairs for a second-generation single-AZ file system. If you increase the number of HA pairs for your file system, you must specify proportional increases for StorageCapacity, Iops, and ThroughputCapacity. For more information, see High-availability (HA) pairs in the FSx for ONTAP user guide. Block storage protocol support (iSCSI and NVMe over TCP) is disabled on file systems with more than 6 HA pairs. For more information, see Using block storage protocols.
*)endpointIpv6AddressRange : Ipv6AddressRange.t option;(Multi-AZ only) Specifies the IPv6 address range in which the endpoints to access your file system will be created. By default in the Amazon FSx API and Amazon FSx console, Amazon FSx selects an available /118 IP address range for you from one of the VPC's CIDR ranges. You can have overlapping endpoint IP addresses for file systems deployed in the same VPC/route tables, as long as they don't overlap with any subnet.
*)}val make :
?automaticBackupRetentionDays:??? ->
?dailyAutomaticBackupStartTime:??? ->
?fsxAdminPassword:??? ->
?weeklyMaintenanceStartTime:??? ->
?diskIopsConfiguration:??? ->
?throughputCapacity:??? ->
?addRouteTableIds:??? ->
?removeRouteTableIds:??? ->
?throughputCapacityPerHAPair:??? ->
?hAPairs:??? ->
?endpointIpv6AddressRange:??? ->
unit ->
tval to_value :
t ->
[> `Structure of
(string
* [> `Integer of AutomaticBackupRetentionDays.t
| `List of [> `String of RouteTableId.t ] list
| `String of DailyTime.t
| `Structure of
(string * [> `Enum of string | `Long of Iops.t ]) list ])
list ]