Paying too much for FSx for Windows®?
Amazon FSx for Windows File Server is AWS's native managed SMB service — a strong fit when you need deep Windows-native features and a fully AWS-managed file system. Many teams on EFS economics or VDI-heavy workloads hit a different pain: provisioned capacity, throughput tiers, and mostly-inactive data billed at full rate while Roadrunner SMB on Amazon EFS tracks real demand.
The FSx cost pattern
FSx for Windows® pricing combines storage capacity with provisioned throughput. That model rewards steady, predictable load — but VDI profile stores, departmental shares with idle periods, and large estates with cold data often mean paying for a peak you sized up front. Amazon EFS Infrequent Access and demand-following Marketplace billing on Roadrunner SMB change that equation for many teams at 10–50 TB scale.
Many teams report 40–60% lower TCO vs. FSx for Windows at 10–50 TB VDI scale. Your results depend on share count, access patterns, and AWS pricing — see the illustrative example on the Pricing page.
Provisioned peak vs. demand-following cost
Elastic SMB™ metadata caching absorbs login-storm load on EFS — so throughput and software billing can track weekly demand instead of a 24×7 provisioned peak.
Roadrunner SMB vs. FSx for Windows
Both deliver managed SMB on AWS with Active Directory and Windows ACL semantics. Roadrunner SMB is an EFS-backed Marketplace appliance in your VPC — elastic storage, hourly consumption billing, and Elastic SMB metadata acceleration for VDI-heavy workloads.
| Dimension | Roadrunner SMB | FSx for Windows |
|---|---|---|
| Storage foundation | Your Amazon EFS (elastic, multi-AZ) | Managed FSx storage |
| Deployment | AWS Marketplace + CloudFormation in your VPC | AWS managed service |
| Storage economics | EFS Standard + Infrequent Access; elastic capacity | Provisioned SSD/HDD capacity tiers |
| VDI / FSLogix at scale | Elastic SMB L1 metadata cache; demand-following throughput | Provisioned throughput tiers |
| Billing model | Hourly ShareHours + ManagedStorageGBHours (Marketplace) | FSx capacity + throughput pricing |
| Pause / dev-test | Scale ASG to 0 — zero RRSMB software charges while offline | FSx capacity charges continue for provisioned storage |
| Linux on same dataset | Same EFS data over NFS and SMB | SMB-focused; separate storage for Linux NFS workloads |
| Data exit | Standard files remain in your EFS if you remove the appliance | FSx-managed volume lifecycle |
| Deep Windows-native features | See Known Limitations (VSS, DFS-R, etc.) | Native Windows Server feature set (VSS, dedupe, DFS, etc.) |
Workloads requiring VSS, DFS replication, or other deep Windows-native SMB features may be better served by FSx for Windows or self-managed Windows file servers — see Known Limitations.
Detailed TCO and architecture
The GA architecture whitepaper covers Elastic SMB caching, cluster HA, identity model, billing dimensions, deployment topology, and FSx comparison rationale in depth.
Not coming from FSx?
Self-managed Windows file servers on EC2 → · DIY Samba on EFS →
Evaluate Roadrunner SMB on Amazon EFS
Subscribe on AWS Marketplace, launch into your VPC, and compare demand-following billing to your current FSx estate — most teams reach a first SMB share in about 30 minutes.