Cloud FSx for ONTAP Finance Oct 05, 2026
What NetApp published
The brief frames the target as banks and other regulated firms trying to modernise core banking, trading, analytics and regulatory-archive data "without increasing risk, operational complexity, or long-term cost." Its central claim is a familiar one: FSx for ONTAP is "familiar ONTAP, delivered as an AWS service," so migrations can use existing tools, workflows and operational models instead of refactoring or retraining.
Two cost claims anchor the document. The first is a headline figure of "up to $2M in annual benefits," attributed in a footnote to an IDC business-value study of FSx for ONTAP that the brief links to. That is a modelled, IDC-derived number — useful directionally, not a quote you can put in a business case without reading the study's assumptions. The second is a specific, named customer.
The Thomson Reuters numbers
The customer spotlight is the only place the brief puts a patient, real-world figure on the page. NetApp says Thomson Reuters needed to move a set of business-critical legal and financial applications to the cloud without disrupting revenue-generating services, while keeping high availability and operational control. The documented actions and results:
- Consolidated multiple NAS environments into a single, fully managed cloud storage solution.
- Used dual-write architectures and ONTAP replication to prioritise data protection during the move.
- Reported improved resilience, automated data protection using AWS Backup, and enhanced monitoring with Grafana.
- Reported approximately $250,000 in annual savings through standardisation on FSx for ONTAP.
Read precisely: that is one customer, one workload set, and a savings figure attributed to the customer. It is the most concrete thing in the document, and it is still a single data point. The $2M figure and the $250K figure are not comparable — one is a portfolio-level model, the other is a named account.
Claims vs. the Open Questions
| Requirement | What the brief claims | What a migration team must still confirm |
|---|---|---|
| Low-risk migration | SnapMirror reproduces the existing architecture, so no application refactoring, recertification or retraining is needed. | Supported source ONTAP releases, topologies, cutover/RPO behaviour and rollback steps for the specific application set. |
| Security & compliance | Encryption at rest and in transit, Active Directory integration, file-level auditing, and SnapLock immutable (WORM) storage; brief states eligibility for ISO, SOC, PCI-DSS and HIPAA. | Which of these are part of the managed service versus customer-operated, and the audit evidence you can actually pull. |
| Resilience | Single-AZ and Multi-AZ deployment options with continuous availability and automated infrastructure management. | RTO/RPO expectations, failover procedure, and how Multi-AZ pricing and limits behave for your workload. |
| Cost & efficiency | ONTAP deduplication, compression, thin provisioning and automatic tiering reduce footprint; fully managed service removes hardware ops. | Real efficiency ratios on your data, tiering thresholds, and total cost including AWS side costs. |
| Integration | Multi-protocol block, file and object, and connection to other AWS services via S3 Access Points. | Which protocols/versions the service exposes and how they interact with your existing clients. |
What the brief does not say
The document contains no pricing, no performance figures (throughput, latency or IOPS), no service limits, and no source-release compatibility matrix. The compliance sentence says the service is "certified for" PCI-DSS, ISO, SOC and HIPAA without listing attestation scope or expiry. For a financial-services audience — the exact audience the brief addresses — the missing layer is the one that decides whether a migration is approved: the control evidence and the support boundary.
This is normal for a vendor solution brief, and it is not a reason to dismiss it. It is a reason to treat the brief as a starting point for the evaluation sheet rather than the answer to it.
How to use it
If you already run ONTAP and are weighing an AWS move, the brief's own logic points at your existing data services. Start with the FSx for NetApp ONTAP reference guide to ground the AWS-specific constraints, and compare the operating model against customer-deployed Cloud Volumes ONTAP — the responsibility split for upgrades, HA and observability is different, and that difference drives who you call when it breaks. Placement decisions belong with the hybrid cloud hub. The SnapLock, SnapMirror and auditing capabilities named here are exactly the primitives to map against your own protection and retention requirements before agreeing to a cutover plan.
Bottom line
The brief is credible as a migration-management story: keep the ONTAP data services you already trust, move the deployment model to a managed AWS service, and lean on SnapMirror to avoid application change. Its proof is thin but real — one customer, about $250K a year — and its cost headline is an IDC model. Useful as vendor framing and as a case-study reference; not yet evidence of your own numbers.