FSx for OpenZFS file systems should be configured for Multi-AZ deployment
Checks that the FSx for OpenZFS file system uses the Multi-AZ (HA) deployment type, whose file servers and storage span two Availability Zones and fail over automatically, so data stays available and durable if one zone fails. Single-AZ (HA) and Single-AZ (non-HA) file systems fail.
- service
- FSx
- severity
- Medium
- scope
- evaluated in every region
How to fix it
- Replaces the resource: The deployment type is fixed at creation and a Single-AZ backup cannot restore as Multi-AZ, so create one, copy data by on-demand replication or rsync, repoint clients, then delete this one.
In the console
Amazon FSx → Create file system → FSx for OpenZFS → Standard create
- Deployment type
- Multi-AZ (HA)
- Preferred subnet
- A subnet in the Availability Zone where most clients run
- Standby subnet
- A subnet in a different Availability Zone from the preferred subnet
- Select route tables
- Every route table associated with the subnets your clients are in
With the AWS CLI
aws fsx create-file-system --file-system-type OPENZFS --storage-capacity <storage-gib> --subnet-ids <preferred-subnet-id> <standby-subnet-id> --open-zfs-configuration DeploymentType=MULTI_AZ_1,ThroughputCapacity=<throughput-mbps>,PreferredSubnetId=<preferred-subnet-id> --region <region>With Terraform
resource "aws_fsx_openzfs_file_system" "this" {
deployment_type = "MULTI_AZ_1"
subnet_ids = [var.preferred_subnet_id, var.standby_subnet_id]
preferred_subnet_id = var.preferred_subnet_id
route_table_ids = var.client_route_table_ids
storage_capacity = var.storage_capacity_gib
throughput_capacity = var.throughput_capacity
}
See which of your accounts this check is failing on.
Book a live scan