What I left off the file portal on AWS — how far FSx for ONTAP features reach, and the work handed to a schedule (Part 6)

Introduction

This is the last part of the series. Part 1 built a file portal on Amazon FSx for NetApp ONTAP (FSx for ONTAP) S3 access points, Part 2 added ransomware response and WORM retention, Part 3 put AI agents on it, Part 4 delegated 182 storage operations, and Part 5 collected what the running cluster refused.

This part is what was left off the screen. That is the difference from last time: where Parts 4 and 5 were about operations you run from a screen, this one has two subjects. How much of ONTAP stays usable without going through the portal at all, and the operational work that was handed to a schedule instead of a button.

What this part does not cover: performance figures (this measures whether things are possible and under what condition, not throughput), running SnapLock or Object Lock (irreversible, so not enabled without an instruction naming the retention), and actual tiering into a capacity pool (needs a different aggregate configuration, which was not on this path).

The reach of ONTAP features on this path