A small city wants Windows file shares for a handful of department apps and is comparing Amazon FSx for Windows File Server with a self-managed Windows file cluster on EC2. Which cost guidance should the architect emphasize?

Managed Amazon FSx for Windows File Server often delivers lower total cost of ownership than a self-managed Windows file cluster on EC2 for a small city because TCO includes labor, patching, backup tooling, monitoring, and failover—not only the EC2 sticker price. FSx provides SMB shares with Active Directory integration and managed high-availability and backup options, which matters when municipal IT staff are few and nights spent babysitting cluster quorum steal capacity from citizen-facing work. Emphasizing fully loaded cost steers the architect away from false economy. Claiming self-managed clusters are always cheaper because FSx never supports Active Directory fails conceptually and factually: FSx for Windows File Server is designed to work with Active Directory, so the premise is wrong and the cost comparison is invalid. Rejecting FSx because municipal workloads cannot use SMB fails because Windows department apps commonly rely on SMB; the protocol itself is not prohibited for civic file shares. Asserting that cost is identical so any console choice is fine fails because managed versus DIY diverge sharply once staff time, backup reliability, and failover operations enter the ledger. Exam caveat: compare FSx versus DIY Windows file servers on total cost of ownership including operations, not instance price alone, and do not invent AD or SMB blockers. Operational check: inventory department SMB dependencies and AD join requirements; estimate hours for patching, backup tests, and HA drills on DIY; price FSx with required throughput/storage; and choose the lower fully loaded option with documented ownership and restore tests for the city’s file shares.