FSx for NetApp ONTAP file systems should be configured for Multi-AZ deployment
Checks that the FSx for NetApp ONTAP file system uses a Multi-AZ deployment type (Multi-AZ 1 or Multi-AZ 2), whose standby file server runs in a second Availability Zone and receives every write synchronously, so data stays available when one zone is unavailable. Single-AZ 1 and Single-AZ 2 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, so create a Multi-AZ file system, move the data by SnapMirror, DataSync or a backup restore, repoint clients, then delete this one.
In the console
Amazon FSx → Create file system → Amazon FSx for NetApp ONTAP → Standard create
- Deployment type
- Multi-AZ 2 or Multi-AZ 1; either passes
- 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
- VPC 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 ONTAP --storage-capacity <storage-gib> --subnet-ids <preferred-subnet-id> <standby-subnet-id> --ontap-configuration DeploymentType=MULTI_AZ_1,ThroughputCapacity=<throughput-mbps>,PreferredSubnetId=<preferred-subnet-id> --region <region>With Terraform
resource "aws_fsx_ontap_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