# Updating an Amazon FSx for OpenZFS file system
Updating a file system

This section provides information on how to update modifyable properties, including storage capacity, throughput capacity, and maintenance windows, on your file system using the Amazon FSx console, the Amazon CLI, and the Amazon FSx API.

**Topics**
+ [

## Updating a file system (Amazon FSx console, Amazon CLI, and Amazon FSx API)
](#update-file-system-console-cli-api)
+ [

## Modifiable file system properties
](#updatable-properties)
+ [

# Modifying provisioned SSD storage capacity and IOPS
](managing-storage-capacity.md)
+ [

# Modifying provisioned SSD read cache
](managing-ssd-read-cache.md)
+ [

# Modifying throughput capacity
](managing-throughput-capacity.md)
+ [

# Modifying network type
](manage-network-type.md)
+ [

# Modifying file system maintenance windows
](maintenance-windows.md)

## Updating a file system (Amazon FSx console, Amazon CLI, and Amazon FSx API)
Updating a file system

------
#### [  Amazon FSx Console  ]

**To update how file system tags are copied**

1. Open the Amazon FSx console at [https://console.amazonaws.cn/fsx/](https://console.amazonaws.cn/fsx/).

1. In the left navigation pane, choose **File systems**, and then choose the FSx for OpenZFS file system that you want to update.

1. For **Actions**, choose **Update file system**. The **Update file system** dialog box displays.
   + For **Copy tags to backups**, choose whether to copy tags from the file system to any backup that's taken.
   + For **Copy tags to volumes**, choose whether to copy tags from the file system to any volume that you create.

1. Choose **Update** to update the file system with your changes.

**To update automatic daily backups**

1. Open the Amazon FSx console at [https://console.amazonaws.cn/fsx/](https://console.amazonaws.cn/fsx/).

1. To display the file system details page, in the left navigation pane, choose **File systems**, and then choose the FSx for OpenZFS file system that you want to update.

1. Choose the **Backups** tab, and then choose Update.

1. Modify the automatic daily backup settings for this file system, and then choose **Save**.

**To update the file system's VPC route tables**

1. Open the Amazon FSx console at [https://console.amazonaws.cn/fsx/](https://console.amazonaws.cn/fsx/).

1. To display the file system details page, in the left navigation pane, choose **File systems**, and then choose the FSx for OpenZFS file system that you want to update.

1. For **Actions**, choose **Update route tables**. This option is only available for Multi-AZ file systems.

1. In the **Manage route tables** dialog box. do one of the following:
   + To associate a new VPC route table, select a route table from the **Associate new route tables** dropdown list, and then choose **Associate**.
   + To disassociate an existing VPC route table, select a route table from the **Current route tables** pane, and then choose **Disassociate**.

1. Choose **Close**.

------
#### [ Amazon CLI and Amazon FSx API ]

**To update a file system (CLI and Amazon FSx API)**
+ To update the configuration of an FSx for OpenZFS file system, use the [update-file-system](https://docs.amazonaws.cn/cli/latest/reference/fsx/update-file-system.html) CLI command (or the equivalent [UpdateFileSystem](https://docs.amazonaws.cn/fsx/latest/APIReference/API_UpdateFileSystem.html) API operation), as shown in the following example.

  ```
  aws fsx update-file-system \
      --file-system-id fs-0123456789abcdef0 \
      --open-zfs-configuration AutomaticBackupRetentionDays=30,DailyAutomaticBackupStartTime=01:00, \
        WeeklyMaintenanceStartTime=1:01:30,AddRouteTableIds=rtb-0123abcd
  ```

------

## Modifiable file system properties


This section provides information on how to update the following FSx for OpenZFS file system properites. You can update an FSx for OpenZFS file system's configuration using the Amazon FSx console, the Amazon CLI, and the Amazon FSx API.
+ **Automatic daily backups** – Back up your file system automatically on a daily basis. Modify the backup window and the backup retention period. For more information about backups, see [Working with automatic daily backups](using-backups.md#automatic-backups).
+ **Copy tags to backups** – Copy file system tags to file system backups.
+ **Copy tags to volumes** – Copy file system tags to the volumes that are attached to the file system.
+ **Provisioned SSD IOPS** – Set a fixed number of IOPS or have Amazon FSx automatically maintain 3 SSD IOPS per GiB of storage capacity. For information on how to increase SSD IOPS, see [Updating SSD storage capacity and provisioned IOPS](managing-storage-capacity.md#increase-storage-capacity).
+ **Storage capacity** – For file systems with SSD (provisioned) storage, storage capacity cannot be decreased after creation, only increased. For information on how to increase SSD (provisioned) storage capacity, see [Updating SSD storage capacity and provisioned IOPS](managing-storage-capacity.md#increase-storage-capacity). For file systems using the Intelligent-Tiering storage class, storage capacity will automatically grow and strink to fit your data needs as they change.
+ **SSD read cache** – For file systems using the Intelligent-Tiering storage class, you can modify the sizing mode of the optional provisioned SSD read cache at any time. For information on how to modify your SSD read cache, see [Modifying provisioned SSD read cache](managing-ssd-read-cache.md). 
+ **Throughput capacity** – You can increase or decrease your file system's throughput capacity at any point. For information on how to update throughput capacity, see [Modifying throughput capacity](managing-throughput-capacity.md#increase-throughput-capacity).
+ **Network type** – You can change your file system's network type at any time. For information on how to change network type, see [Modifying network type](manage-network-type.md).
+ **Weekly maintenance window** – Set the day of the week and time that Amazon FSx performs file system maintenance and updates. For information on how to change the weekly maintenance window, see [Changing the weekly maintenance window](maintenance-windows.md#change-maintenance-window).
+ **Amazon VPC route tables** – For Multi-AZ file systems, FSx for OpenZFS creates an endpoint for accessing your file system in a VPC route table. You can associate new route tables that you create with your existing Multi-AZ file systems—allowing you to configure which clients can access your data even as your network evolves. You can also disassociate (remove) existing route tables from your file system.

# Modifying provisioned SSD storage capacity and IOPS
Modifying SSD storage capacity and IOPS

When you need additional storage for your dataset, you can increase the solid state drive (SSD) storage capacity of your Amazon FSx for OpenZFS file system without any disruption to your end users or applications by using the Amazon FSx console, Amazon FSx API, or Amazon Command Line Interface (Amazon CLI).

You can also change the provisioned SSD IOPS for your file system when you increase SSD storage capacity, or as an independent action. To specify the amount of provisioned SSD IOPS for your file system, use one of two IOPS modes:
+ Use **Automatic** mode if you want Amazon FSx to automatically scale your SSD IOPS.
+ Use **User-provisioned** mode if you want to provision a specific amount of SSD IOPS.

 For more information about these modes, see [Considerations when updating storage and IOPS](#scaling-considerations).

When you increase the SSD storage capacity of your Amazon FSx file system, the new capacity is available for use within minutes. These updates do not impact the availability of your file system in any way. You will be billed for the new SSD storage capacity after it becomes available to you. For more information, see [Amazon FSx for OpenZFS Pricing](https://www.amazonaws.cn/fsx/openzfs/pricing/).

 You can track the progress of an SSD storage capacity increase or SSD IOPS update at any time by using the Amazon FSx console, CLI, and API. For more information, see [Monitoring storage capacity and IOPS updates](#monitoring-storage-capacity-increase).

Once the increased SSD capacity is available, if the file system's root volume storage capacity quota is set to the same size as the file system, FSx will automatically update the volume's storage capacity quota to match the newly-increased file system capacity. Otherwise, you need to manually increase the `storage capacity quota` of the root volume, and any other volumes in your file system. For more information, see [Updating an Amazon FSx for OpenZFS volume](updating-volumes.md).

**Topics**
+ [

## Considerations when updating storage and IOPS
](#scaling-considerations)
+ [

## When to increase storage capacity
](#when-to-modify-storage-capacity)
+ [

## Updating SSD storage capacity and provisioned IOPS
](#increase-storage-capacity)
+ [

## Monitoring storage capacity and IOPS updates
](#monitoring-storage-capacity-increase)

## Considerations when updating storage and IOPS


Here are a few important considerations when modifying your SSD storage capacity and provisioned IOPS:
+ **Storage capacity increase only** – You can only *increase* the amount of SSD storage capacity for a file system; you cannot decrease the storage capacity.
+ **Storage capacity minimum increase** – Each SSD storage capacity increase must be a minimum of 10 percent of the file system's current SSD storage capacity, up to the maximum allowed value of 512 Tebibytes (TiB)\$1.
**Note**  
\$1The maximum storage capacity of your file system depends on the Amazon Web Services Region in which it is located. For more information, see [Resource quotas for each file system](limits.md#limits-openzfs-resources-file-system).
+ **Time between increases** – You can't request an SSD storage capacity increase or provisioned SSD IOPS change on a file system until 6 hours after the previous change request. For Multi-AZ and Intelligent-Tiering file systems, you also can't make SSD storage capacity or provisioned SSD IOPS changes within 6 hours of a throughput capacity change, and vice versa. For more information, see [Modifying throughput capacity](managing-throughput-capacity.md).
+ **Allocating increased storage capacity** – If the file system's root volume storage capacity quota is set to the same size as the file system, FSx will automatically update the volume's storage capacity quota to match the newly-increased file system capacity. Otherwise, you will need to manually [increase storage](updating-volumes.md) on the root volume and any other volumes in your file system.
+ **Provisioned IOPS modes** – For a provisioned IOPS change, you must specify a mode. The two IOPS modes are the following:
  + **Automatic** mode – Amazon FSx automatically scales your SSD IOPS to maintain 3 SSD IOPS per GiB of storage capacity, up to the maximum number of IOPS for your file system.
  + **User-provisioned** mode – You specify the number of SSD IOPS, which must be greater than or equal to 3 IOPS per GiB of storage capacity. If the amount of SSD IOPS is not at least 3 IOPS per GiB, the request will fail. You can optionally provision a higher level of IOPS. If you do so, you pay for the average IOPS provisioned above 3 IOPS per GiB per file system.
**Note**  
For file systems that are already configured with **User-provisioned** SSD IOPS, you must specify a value for **User-provisioned** SSD IOPS when you are updating your file system, or the update request will fail.

## When to increase storage capacity


If you are running out of SSD storage, we recommend that you increase the storage capacity of your file system. You can monitor SSD storage capacity on the file system using these file system-level Amazon CloudWatch metrics.
+ `StorageCapacity` measure the total amount of file system SSD storage capacity.
+ `UsedStorageCapacity` measures the amount of used SSD storage capacity.

You can use these metrics to measure storage capacity and create alarms. The following are some examples:
+ Per cent storage capacity used = `UsedStorageCapacity` ÷ `StorageCapacity`
+ Per cent storage capacity available = `StorageCapacity` ÷ `UsedStorageCapacity`
+ Amount of free storage capacity = `StorageCapacity` − `UsedStorageCapacity`

You can create a CloudWatch alarm on a metric and get notified when it drops below a specific threshold. For more information, see [Monitoring with Amazon CloudWatch](monitoring-cloudwatch.md).

## Updating SSD storage capacity and provisioned IOPS


You can increase a file system's SSD storage capacity and modify your provisioned SSD IOPS by using the Amazon FSx console, the Amazon CLI, or the Amazon FSx API.

### To update SSD storage capacity and provisioned IOPS for a file system (console)


1. Open the Amazon FSx console at [https://console.amazonaws.cn/fsx/](https://console.amazonaws.cn/fsx/).

1. In the left navigation pane, choose **File systems**. In the **File systems** list, choose the FSx for OpenZFS file system that you want to update SSD storage capacity and SSD IOPS for.

1. On the **Summary** panel, choose **Update** next to the file system's **SSD storage capacity** value.

   The **Update SSD storage capacity and IOPS** dialog box appears.

1. To increase SSD storage capacity, select **Modify storage capacity**.

1. For **Input type**, choose one of the following: 
   + To enter the new SSD storage capacity as a percentage change from the current value, choose **Percentage**.

     For **Desired % increase**, enter the percentage by which you want to increase storage capacity. This value must be at least 10 percent.
   + To enter the new value in GiB, choose **Absolute**.

     For **Desired storage capacity**, enter the new value for SSD storage capacity value in GiB, up to the maximum allowed value of 512 TiB\$1.
**Note**  
\$1The maximum storage capacity of your file system depends on the Amazon Web Services Region in which it is located. For more information, see [Resource quotas for each file system](limits.md#limits-openzfs-resources-file-system).

1. For **Provisioned SSD IOPS**, you have two options to modify the number of provisioned SSD IOPS for your file system:
   + If you want Amazon FSx to automatically scale your SSD IOPS to maintain 3 provisioned SSD IOPS per GiB of primary storage capacity, up to a maximum of 160,000 for Single-AZ 1 and 400,000 for Multi-AZ\$1, choose **Automatic**.
   + If you want to specify the number of SSD IOPS, choose **User-provisioned**. Enter an absolute number of IOPS that is at least 3 times the amount of GiB of your primary storage tier, and less than or equal to the maximum number of IOPS for your file system.

1. Choose **Update**.

### To update SSD storage capacity and provisioned IOPS for a file system (CLI)


To update the SSD storage capacity and provisioned IOPS for an FSx for OpenZFS file system, use the Amazon CLI command [update-file-system](https://docs.amazonaws.cn/cli/latest/reference/fsx/update-file-system.html) (UpdateFileSystem is the equivalent API action). Set the following parameters:
+ Set `--file-system-id` to the ID of the file system that you are updating.
+ To increase your SSD primary storage capacity, set `--storage-capacity` to a value that is at least 10 percent greater than the current value.
+ To modify your provisioned SSD IOPS, use the `--open-zfs-configuration DiskIopsConfiguration` property. This property has two parameters, `Iops` and `Mode`:
  + If you want to specify the number of provisioned SSD IOPS, use `Iops=number_of_IOPS`, up to a maximum of 160,000 for Single-AZ 1 and Multi-AZ\$1, and `Mode=USER_PROVISIONED`. The SSD IOPS value must be greater than or equal to 3 times the requested SSD storage capacity. If you're not increasing the storage capacity, the IOPs value must be greater than or equal to 3 times the current SSD storage capacity.
**Note**  
\$1The maximum SSD IOPS you can provision for Multi-AZ file systems depends on the Amazon Web Services Region your file system is located in. For more information, see [Data access from disk](performance-ssd.md#data-access-disk).
  + If you want Amazon FSx to automatically increase your SSD IOPS, use `Mode=AUTOMATIC` and don't use the `Iops` parameter. Amazon FSx will automatically maintain 3 provisioned SSD IOPS per GiB of your primary storage capacity, up to a maximum of 160,000 for Single-AZ 1 and Multi-AZ.

The following example requests an increase of 2000 GiB to the file system's SSD storage capacity. It also requests 7000 provisioned SSD IOPS.

```
aws fsx update-file-system \
    --file-system-id fs-0123456789abcdef0 \
    --storage-capacity 2000 \
    --open-zfs-configuration 'DiskIopsConfiguration={Iops=7000,Mode=USER_PROVISIONED}'
```

To monitor the progress of the update, use the [describe-file-systems](https://docs.amazonaws.cn/cli/latest/reference/fsx/describe-file-systems.html) Amazon CLI command. Look for the `AdministrativeActions` section in the output.

For more information, see [AdministrativeAction](https://docs.amazonaws.cn/fsx/latest/APIReference/API_AdministrativeAction.html) in the *Amazon FSx for OpenZFS API Reference*.

## Monitoring storage capacity and IOPS updates


You can monitor the progress of an SSD storage capacity and IOPS update by using the Amazon FSx console, the API, or the Amazon CLI.

### Monitoring updates in the console


You can monitor file system updates in the **Updates** tab on the **File system details** page.

For SSD storage capacity and IOPS updates, you can view the following information:

****Update type****  
Supported types are **Storage capacity**, **IOPS Mode**, and **SSD IOPS**. The **IOPS Mode** and **SSD IOPS** values are listed for all storage capacity and IOPS scaling requests. 

****Target value****  
The updated value for the file system's SSD storage capacity or IOPs.

****Status****  
The current status of the update. The possible values are as follows:  
+ **Pending** – Amazon FSx has received the update request, but has not started processing it.
+ **In progress** – Amazon FSx is processing the update request.
+ **Completed** – The update finished successfully.
+ **Failed** – The update request failed. Choose the question mark (**?**) to see details on why the request failed.

****Request time****  
The time that Amazon FSx received the update action request.

### Monitoring increases with the Amazon CLI and API


You can view and monitor file system SSD storage capacity increase requests using the [describe-file-systems](https://docs.amazonaws.cn/cli/latest/reference/fsx/describe-file-systems.html) Amazon CLI command and the [DescribeFileSystems](https://docs.amazonaws.cn/fsx/latest/APIReference/API_DescribeFileSystems.html) API operation. The `AdministrativeActions` array lists the 10 most recent update actions for each administrative action type. When you increase a file system's SSD storage capacity, a `FILE_SYSTEM_UPDATE` `AdministrativeActions` is generated.

The following example shows an excerpt of the response of a `describe-file-systems` CLI command. The file system has a pending administrative action to increase the SSD storage capacity to 2000 GiB and the provisioned SSD IOPS to 7000.

```
"AdministrativeActions": [
    {
        "AdministrativeActionType": "FILE_SYSTEM_UPDATE",
        "RequestTime": 1586797629.095,
        "Status": "PENDING",
        "TargetFileSystemValues": {
            "StorageCapacity": 2000,
            "OpenZFSConfiguration": {
                "DiskIopsConfiguration": {
                    "Mode": "USER_PROVISIONED",
                    "Iops": 7000
                }
            }
        }
    }
]
```

Amazon FSx processes the `FILE_SYSTEM_UPDATE` action, increasing the file system's storage capacity. When the new storage is available to the file system, the `FILE_SYSTEM_UPDATE` status changes to `COMPLETED`. The storage capacity shows the new larger value. This behavior is shown in the following excerpt of the response of a `describe-file-systems` CLI command. 

```
"AdministrativeActions": [
    {
        "AdministrativeActionType": "FILE_SYSTEM_UPDATE",
        "RequestTime": 1586799169.445,
        "Status": "UPDATED_OPTIMIZING",
        "TargetFileSystemValues": {
            "StorageCapacity": 2000,
            "OpenZFSConfiguration": {
                "DiskIopsConfiguration": {
                    "Mode": "USER_PROVISIONED",
                    "Iops": 7000
                }
            }
        }
    }
]
```

 If the storage capacity or IOPS update request fails, the status of the `FILE_SYSTEM_UPDATE` action changes to `FAILED`, as shown in the following example. The `FailureDetails` property provides information about the failure.

```
"AdministrativeActions": [
    {
        "AdministrativeActionType": "FILE_SYSTEM_UPDATE",
        "RequestTime": 1586373915.697,
        "Status": "FAILED",
        "TargetFileSystemValues": {
            "StorageCapacity": 2000,
            "OpenZFSConfiguration": {
                "DiskIopsConfiguration": {
                    "Mode": "USER_PROVISIONED",
                    "Iops": 7000
                }
            }
        },
        "FailureDetails": {
            "Message": "failure-message"
        }
    }
]
```

# Modifying provisioned SSD read cache
Modifying SSD read cache

When you create a file system with the Intelligent-Tiering storage class, you have the option to also provision an SSD read cache that provides SSD latencies for reads of frequently accessed data, up to 3 IOPS per GiB. The SSD read cache has three sizing modes: Automatic, Custom, and None. After your file system is created, you can modify your SSD read cache's sizing mode at any time.

**Topics**
+ [

## Considerations when updating SSD read cache sizing mode
](#considerations-update-ssd-read-cache)
+ [

## Updating the provisioned SSD read cache
](#how-to-update-ssd-read-cache)
+ [

## Monitoring SSD read cache updates
](#monitoring-ssd-read-cache-update)

## Considerations when updating SSD read cache sizing mode


Here are a few important considerations when modifying your SSD read cache:
+ Any time you modify the SSD read cache, all of its contents will be erased. This means that you may see a decrease in performance levels until the SSD read cache is populated again.
+ You can both increase and decrease the size of the SSD read cache. However, you can only do this once every six hours. There is no time restriction when adding or removing the SSD read cache from your file system.
+ You must increase or decrease the size of your SSD read cache by a minimum of 10% every time you modify it.

## Updating the provisioned SSD read cache


You can update your SSD read cache using the Amazon FSx console, the Amazon CLI, or the Amazon FSx API.

### To update the SSD read cache for an Intelligent-Tiering file system (console)


1. Open the Amazon FSx console at [https://console.amazonaws.cn/fsx/](https://console.amazonaws.cn/fsx/).

1. In the left navigation pane, choose **File systems**. In the **File systems** list, choose the FSx for OpenZFS file system that you want to update the SSD read cache for.

1. On the **Summary** panel, choose **Update** next to the file system's **SSD read cache configuration** value.

   The **Update SSD read cache** panel appears.

1. Select the new sizing mode that you would like for your SSD read cache, as follows:
   + Choose **Automatic (Proportional to throughput capacity)** to have your SSD read cache automatically sized based on your throughput capacity.
   + Choose **Custom (User-provisioned)** if you know the approximate size of your dataset and would like to customize your SSD read cache. If you select Custom, you will also need to specify the **Desired read cache capacity** in GiB.
   + Choose **None** if you do not want to use an SSD read cache with your Intelligent-Tiering file system.

1. Choose **Update**.

### To update the SSD read cache for an Intelligent-Tiering file system (CLI & API)


To update the SSD read cache for an Intelligent-Tiering file system, use the Amazon CLI command [update-file-system](https://docs.amazonaws.cn/cli/latest/reference/fsx/update-file-system.html) or the equivalent UpdateFileSystem API action. Set the following parameters:
+ Set `--file-system-id` to the ID of the file system that you are updating.
+ To modify your SSD read cache, use the `--open-zfs-configuration ReadCacheConfiguration` property. This property has two parameters, `SizeGiB` and `SizingMode`:
  + 
    + Set to `NO_CACHE` if you do not want to use an SSD read cache with your Intelligent-Tiering file system.
    + Set to `USER_PROVISIONED` to specify the exact size of your SSD read cache.
    + Set to `PROPORTIONAL_TO_THROUGHPUT_CAPACITY` to have your SSD read cache automatically sized based on your throughput capacity.

The following example updates the SSD read cache sizing mode to **USER\$1PROVISIONED** and sets the size to 524288 GiB.

```
aws fsx update-file-system \
    --open-zfs-configuration 'ReadCacheConfiguration={SizeGiB=524288,SizingMode=USER_PROVISIONED}'
```

To monitor the progress of the update, use the [describe-file-systems](https://docs.amazonaws.cn/cli/latest/reference/fsx/describe-file-systems.html) Amazon CLI command. Look for the `AdministrativeActions` section in the output.

For more information, see [AdministrativeAction](https://docs.amazonaws.cn/fsx/latest/APIReference/API_AdministrativeAction.html) in the *Amazon FSx for OpenZFS API Reference*.

## Monitoring SSD read cache updates


You can monitor the progress of an SSD read cache update by using the Amazon FSx console, the API, or the Amazon CLI.

### Monitoring updates in the console


You can monitor file system updates in the **Updates** tab on the **File system details** page.

For SSD read cache updates, you can view the following information:

****Update type****  
Supported types are **SSD read cache sizing mode** and **SSD read cache size**.

****Target value****  
The updated value for the file system's SSD read cache sizing mode or SSD read cache size.

****Status****  
The current status of the update. The possible values are as follows:  
+ **Pending** – Amazon FSx has received the update request, but has not started processing it.
+ **In progress** – Amazon FSx is processing the update request.
+ **Completed** – The update finished successfully.
+ **Failed** – The update request failed. Choose the question mark (**?**) to see details on why the request failed.

****Request time****  
The time that Amazon FSx received the update action request.

### Monitoring SSD read cache updates with the Amazon CLI and API


You can view and monitor file system SSD read cache update requests using the [describe-file-systems](https://docs.amazonaws.cn/cli/latest/reference/fsx/describe-file-systems.html) Amazon CLI command and the [DescribeFileSystems](https://docs.amazonaws.cn/fsx/latest/APIReference/API_DescribeFileSystems.html) API operation. The `AdministrativeActions` array lists the 10 most recent update actions for each administrative action type. When you update a file system's SSD read cache, a `FILE_SYSTEM_UPDATE` `AdministrativeActions` is generated.

The following example shows an excerpt of the response of a `describe-file-systems` CLI command. The file system has a pending administrative action to change the SSD read cache sizing mode to `USER_PROVISIONED` and the SSD read cache size to 524288.

```
"AdministrativeActions": [
    {
        "AdministrativeActionType": "FILE_SYSTEM_UPDATE",
        "RequestTime": 1586797629.095,
        "Status": "PENDING",
        "TargetFileSystemValues": {
            "OpenZFSConfiguration": {
                "ReadCacheConfiguration": {
                     "SizingMode": "USER_PROVISIONED"
                     "SizeGiB": 524288,
                }
            }
        }
    }
]
```

When the new SSD read cache configuration is available to the file system, the `FILE_SYSTEM_UPDATE` status changes to `COMPLETED`. If the SSD read cache update request fails, the status of the `FILE_SYSTEM_UPDATE` action changes to `FAILED`.

# Modifying throughput capacity


 Every FSx for OpenZFS file system has a throughput capacity that is configured when you create the file system. You can modify your file system's throughput capacity at any time, as needed. Throughput capacity is one factor that determines the speed at which the file server hosting the file system can serve file data. Higher levels of throughput capacity also come with higher levels of I/O operations per second (IOPS) and more memory for caching of data on the file server. For more information, see [Performance for Amazon FSx for OpenZFSPerformance](performance.md). 

 When you modify your file system's throughput capacity, behind the scenes, Amazon FSx switches out the file system's file server. For Single-AZ (HA) and Multi-AZ (HA) file systems, it results in an automatic failover and failback while Amazon FSx switches out the preferred and secondary file servers. Single-AZ (non-HA) file systems will be unavailable for a few minutes during throughput capacity scaling. You are billed for the new amount of throughput capacity once it is available to your file system.

 For all FSx for OpenZFS file systems, you can't request a throughput capacity update if there is an ongoing SSD storage capacity or provisioned SSD IOPS update. You must wait until the SSD storage capacity or provisioned SSD IOPS update has completed before requesting a throughput capacity update. For Multi-AZ and Intelligent-Tiering file systems, you must wait a minimum of six hours between requests to update the throughput capacity, SSD storage capacity, or provisioned SSD IOPS. For more information on SSD storage and provisioned IOPS updates, see [Modifying provisioned SSD storage capacity and IOPS](managing-storage-capacity.md).

File systems offer varying levels of throughput capacity, depending on your deployment type. The values of throughput capacity (in MBps) for Single-AZ 1 and Multi-AZ are as follows:
+ **Multi-AZ** – 160, 320, 640, 1280, 2560, 3840, 5120, 7680, 10240
+ **Single-AZ 1 (HA)** – 128, 256, 512, 1024, 2048, 3072, 4096
+ **Single-AZ 1 (non-HA)** – 64, 128, 256, 512, 1024, 2048, 3072, 4096

**Topics**
+ [

## When to modify throughput capacity
](#when-to-modify-throughput-capacity)
+ [

## Modifying throughput capacity
](#increase-throughput-capacity)

## When to modify throughput capacity


Amazon FSx integrates with Amazon CloudWatch, enabling you to monitor your file system's ongoing throughput usage levels. The performance (throughput and IOPS) that you can drive through your file system depends on your specific workload’s characteristics, in addition to your file system’s throughput capacity, storage capacity, and storage type. You can use CloudWatch metrics to determine which of these dimensions to change to improve performance. For more information, see [Monitoring with Amazon CloudWatch](monitoring-cloudwatch.md).

## Modifying throughput capacity


You can modify a file system's throughput capacity using the Amazon FSx console, the Amazon Command Line Interface (Amazon CLI), or the Amazon FSx API.

### To modify a file system's throughput capacity (console)


1. Open the Amazon FSx console at [https://console.amazonaws.cn/fsx/](https://console.amazonaws.cn/fsx/).

1. Navigate to **File systems**, and choose the FSx for OpenZFS file system that you want to increase the throughput capacity for.

1. For **Actions**, choose **Update throughput capacity**. Or, in the **Summary** panel, choose **Update** next to the file system's **Throughput capacity**.

   The **Update throughput capacity** window appears.

1. Choose the new value for **Desired throughput capacity** from the list.

1. Choose **Update** to initiate the throughput capacity update.
**Note**  
Your file system may experience a very brief period of unavailability during the update.

### To modify a file system's throughput capacity (CLI)

+ To modify a file system's throughput capacity, use the [update-file-system](https://docs.amazonaws.cn/cli/latest/reference/fsx/update-file-system.html) CLI command (or the equivalent [UpdateFileSystem](https://docs.amazonaws.cn/fsx/latest/APIReference/API_UpdateFileSystem.html) API operation), as shown in the following example.

  ```
  aws fsx update-file-system \
      --file-system-id fs-0123456789abcdef0 \
      --open-zfs-configuration '{"ThroughputCapacity":512}'
  ```

# Modifying network type
Modifying network type

When you create an Amazon FSx for OpenZFS file system, you must specify a network type, which must be one of the following options:
+ `IPv4` allows your file system to communicate using only Internet Protocol version 4 (IPv4).
+ `Dual-stack` allows your file system to communicate using both Internet Protocol version 6 (IPv6) and IPv4.

You can change the network type of an existing FSx for OpenZFS file system at any time using the Amazon FSx Management Console, Amazon CLI, Amazon API, or one of the Amazon SDKs. For example, if your subnets support both IPv4 and IPv6 addressing, you can update your existing file system from IPv4-only to dual-stack mode, You can also update your dual-stack file system to IPv4-only.

## Using dual-stack mode


You should use dual-stack mode if you need to access and manage your Amazon FSx file systems natively from IPv6 clients. By configuring your Amazon FSx file system to use dual-stack addressing, you can access your file data from IPv6 clients, as well as IPv4 clients, in the same Amazon VPC, in another Amazon Web Services account's VPC, or in your on-premises network. For example, with an Amazon FSx file system configured to use dual-stack, you can have existing IPv4 clients and new IPv6 clients accessing your file data stored on your file system.

By default, Amazon FSx and Amazon VPC use the IPv4 addressing protocol. So as a prerequisite to using IPv6, you must first assign an Amazon-provided IPv6 Classless Inter-Domain Range (CIDR) block to your VPC and subnets before you can use IPv6 with your Amazon FSx file systems. For information on enabling IPv6 for your VPC, see [Add IPv6 support for your VPC](https://docs.amazonaws.cn/vpc/latest/userguide/vpc-migrate-ipv6-add.html) in the *Amazon Virtual Private Cloud User Guide*.

When creating FSx for OpenZFS file systems set to dual-stack mode, you can specify the IPv6 address range, in addition to the existing IPv4 address range, in which the endpoints to access your file system will be created. By default, Amazon FSx chooses a block of 1024 IP addresses from one of the VPC's IPv6 CIDR ranges to use as the endpoint IPv6 address range for the file system.

## Changing network type


You can modify a file system's network type using the Amazon FSx console, the Amazon Command Line Interface (Amazon CLI), or the Amazon FSx API.

### To change a file system's network type (console)


1. Open the Amazon FSx console at [https://console.amazonaws.cn/fsx/](https://console.amazonaws.cn/fsx/).

1. Navigate to **File systems**, and choose the FSx for OpenZFS file system that you want to change the network type for.

1. For **Actions**, choose **Update network type**. Or, in the **Network & security** panel, choose **Manage** next to the file system's **Network type**.

   The **Update network type** window appears.

1. For **Desired network type**, choose either **IPv4** or **Dual-stack**.
   + If you choose `IPv4`, no further configuration is required.
   + If you choose `Dual-stack`, specify the IPv6 address range that your file system endpoints will use:
     + **Unallocated IPv6 address range from your VPC** – Amazon FSx chooses an available /118 IP address range from one of the VPC's IPv6 CIDR ranges to use as the endpoint IPv6 address range for the file system.
     + **Enter an IPv6 address range** – You can provide an IPv6 CIDR range of your own choosing. The IP address range that you choose can either be inside or outside the VPC’s IP address range, as long as it doesn't overlap with any subnet.

1. Choose **Update**.

### To modify a file system's network type (CLI)

+ To modify a file system's network type, use the [update-file-system](https://docs.amazonaws.cn/cli/latest/reference/fsx/update-file-system.html) CLI command (or the equivalent [UpdateFileSystem](https://docs.amazonaws.cn/fsx/latest/APIReference/API_UpdateFileSystem.html) API operation), as shown in the following example.

  ```
  aws fsx update-file-system \
      --file-system-id fs-0123456789abcdef0 \
      --network-type DUAL
  ```

# Modifying file system maintenance windows
Modifying maintenance windows

Amazon FSx for OpenZFS performs routine software patching for the OpenZFS software it manages. The maintenance window is your opportunity to control what day and time of the week this software patching occurs. You can choose the maintenance window during file system creation, or at a later time. If you have no time preference, a 30-minute default window is assigned.

FSx for OpenZFS allows you to adjust your maintenance window as needed to accommodate your workload and operational requirements. You can move your maintenance window as frequently as required, provided that a maintenance window is scheduled at least once every 14 days. If a patch is released and you haven’t scheduled a maintenance window within 14 days, FSx for OpenZFS will proceed with maintenance on the file system to ensure its security and reliability.

 Patching occurs infrequently, typically once every month during the maintenance window that you specify. Patching should require only a portion of your 30-minute maintenance window. We recommend scheduling your maintenance window during idle periods when there is minimal load on your file system. While patching is in progress, you should expect that your Single-AZ (non-HA) file systems will be unavailable, typically for less than 15 minutes. Your Single-AZ (HA) and Multi-AZ (HA) file systems will remain available and automatically fail over and fail back between the preferred file server and the standby file server. For more information, see [Failover process for FSx for OpenZFS](availability-durability.md#multi-az-failover). 

For file systems that use the Intelligent-Tiering storage class, the in-memory cache will be erased during maintenance, leading to higher latencies, particularly on metadata, until after maintenance has been completed.

**Note**  
To ensure data integrity during maintenance activity, FSx for OpenZFS completes pending write operations to the underlying storage volumes that host your file system before maintenance begins.

 You can use the Amazon FSx Management Console, Amazon CLI, Amazon API, or one of the Amazon SDKs to change the maintenance window for your file systems. 

## Changing the weekly maintenance window


**To change the weekly maintenance window (console)**

1. Open the Amazon FSx console at [https://console.amazonaws.cn/fsx/](https://console.amazonaws.cn/fsx/).

1. Choose **File systems** in the left hand navigation column.

1. Choose the file system that you want to change the weekly maintenance window for. The file system details page displays.

1. Choose **Administration** to display the file system administration **Settings** panel.

1. Choose **Update** to display the **Change maintenance window** window.

1.  Enter the new day and time that you want the weekly maintenance window to start.

1. Choose **Save** to save your changes. The new maintenance start time is displayed in the file system administration **Settings** panel.

To change the weekly maintenance window using the [update-file-system](https://docs.amazonaws.cn/cli/latest/reference/fsx/update-file-system.html) CLI command, see [Updating a file system (Amazon FSx console, Amazon CLI, and Amazon FSx API)](updating-file-system.md#update-file-system-console-cli-api).