Setting the file. One moment.
Subchapter 43.5
references/fsx-ontap-knowledge.mdMarkdown7 KBView on GitHub
This reference captures information addressing common gotchas and frequently asked questions for Amazon FSx for NetApp ONTAP to support accurate model responses. It is not a complete specification. The authoritative source for current specifications, limits, quotas, and API behavior is the Amazon FSx for NetApp ONTAP User Guide, , , and . Retrieve current specifications, limits, and quotas from those pages before citing specifics; cite figures only from those pages.
What it is: Amazon FSx for NetApp ONTAP provides fully managed shared storage built on NetApp’s popular ONTAP file system, bringing the familiar features, performance, and APIs of on-premises NetApp to AWS as a fully managed service. It offers multi-protocol access (NFS, SMB, iSCSI, NVMe-over-TCP, and the Amazon S3 API via S3 Access Points), and is designed to deliver sub-millisecond latencies and tens of GB/s of throughput along with ONTAP’s rich data management capabilities (like snapshots, data cloning, SnapMirror replication, deduplication, compression, and automatic tiering).
Well-suited for: enterprise NAS migrations, especially from NetApp, and any workload that needs more than one access protocol or the broadest set of enterprise data-management, security, and resiliency features from a single system, such as general-purpose file shares and home directories, multi-protocol shares, business-critical databases (such as SAP HANA, Oracle, and SQL Server), VMware datastores, line-of-business applications (such as medical imaging and product lifecycle management), and hybrid or disaster-recovery workloads.
See When to choose Amazon FSx (opens in a new tab) and How Amazon FSx for NetApp ONTAP works (opens in a new tab).
You MUST retrieve information from the linked documentation in the below table before answering any user question on the related topic.
| Topic | Example service characteristics, features, and actions | Documentation |
|---|---|---|
| Access and protocols | NFS; SMB; iSCSI and NVMe-over-TCP (block protocols, limited by HA-pair count); S3 Access Points; concurrent NFS and SMB; Storage Virtual Machines; volume security style; Active Directory and LDAP identity | Accessing your FSx for ONTAP data (opens in a new tab) |
| Deployment and availability | Single-AZ HA; Multi-AZ | Availability, durability, and deployment options (opens in a new tab) |
| Storage classes | SSD; capacity pool | Managing storage capacity (storage tiers) (opens in a new tab) |
| Data protection and management | tiering policies; snapshots; SnapMirror (ONTAP-to-ONTAP data replication); FlexClone (clones); FlexCache (caching); deduplication; compression; compaction; thin provisioning; SnapLock WORM; backups | Protecting your data (opens in a new tab) |
| Performance | SSD IOPS baseline and limits; throughput capacity; scale-out with HA pairs; utilization-gated tiering | Amazon FSx for NetApp ONTAP performance (opens in a new tab) |
| Security | AWS KMS at rest; in-transit via Nitro, Kerberos, IPsec; vscan; SnapLock; file-access auditing; QoS; administrative credentials | Security in Amazon FSx for NetApp ONTAP (opens in a new tab) |
| Health and monitoring | CloudWatch metrics; alarms; ONTAP EMS events; AWS CloudTrail | Monitoring Amazon FSx for NetApp ONTAP (opens in a new tab) |
| Pricing | SSD storage; SSD IOPS; throughput capacity; capacity pool storage and requests; backup storage; S3 Access Points requests; Multi-AZ premium (not exhaustive, review pricing page for the full list of pricing dimensions) | Amazon FSx for NetApp ONTAP pricing (opens in a new tab) |
You MUST retrieve information from the linked documentation in the below table before answering any user question on the related service.
| Example service | Example characteristics and common workloads | Documentation |
|---|---|---|
| S3 Access Points for FSx | S3 API access to file data; per-access-point IAM and POSIX; concurrent NFS and S3 | Accessing your data via Amazon S3 access points (opens in a new tab) |
| Non-NetApp NAS migration | Dell PowerScale/Isilon, Qumulo, VAST, Pure; rsync, Robocopy, NetApp CloudSync | Migrating to Amazon FSx for NetApp ONTAP (opens in a new tab) |
You MUST retrieve information from the linked documentation in the below table before providing the user with any guidance on the related area.
| Example area | Example errors | Example fixes | Documentation |
|---|---|---|---|
| Access and permissions | NFS identities unresolved; SMB fails without AD | join the SVM to Active Directory and configure LDAP | Enabling multiprotocol workloads (opens in a new tab), Active Directory in FSx for ONTAP (opens in a new tab) |
| Migration | SnapMirror from a non-NetApp source | use AWS DataSync (AWS-native, recommended), rsync, Robocopy, or NetApp CloudSync | Amazon FSx for NetApp ONTAP FAQs (opens in a new tab) |
| Capacity and scaling | tuning not aligned with SSD utilization; per-volume tiering-policy fine-tuning | keep SSD utilization in range; fine-tune the tiering policy per volume for the workload | Volume storage capacity (opens in a new tab) |
| Connectivity and networking | access issues for Multi-AZ file systems from a peered or on-premises network; iSCSI or NVMe LUN unavailable | for Multi-AZ file systems, NFS, SMB, and ONTAP management endpoints use floating IP addresses, so access from a peered VPC or on-premises requires AWS Transit Gateway (VPC Peering, Direct Connect, and Site-to-Site VPN cannot route to floating IPs); Single-AZ endpoints are secondary IPs in the VPC CIDR and do not require Transit Gateway; iSCSI, NVMe, and inter-cluster (SnapMirror) endpoints use VPC-CIDR IPs and work over VPC Peering; for LUNs verify igroup and mapping | Routing to Multi-AZ file systems (opens in a new tab), Creating an iSCSI LUN (opens in a new tab) |