File system storage: you pay for your use of a file system based on its storage capacity measured in gigabyte-months (GB-Months).
Persistent file systems are ideal for longer-term storage and workloads. Data is replicated and file servers are replaced if they fail. Scratch file systems are ideal for temporary storage and shorter-term processing of data. Data is not replicated and does not persist if a file server fails.
SSD storage is optimized for latency-sensitive workloads or workloads requiring the highest levels of IOPS/throughput. HDD storage is optimized for throughput-focused workloads that aren’t latency-sensitive. For HDD-based file systems, the optional SSD cache improves performance by automatically placing your most frequently read data on SSD (the cache size is 20% of your file system size).
Backups: For backup storage, you pay for the amount of backup data stored, measured in gigabytes-months (GB-Months). Backups are incremental, which means only the changes after your most recent backup are saved, so you save on storage costs by not duplicating data.
Data compression: You can use data compression to reduce storage consumption of both your file system storage and your file system backups.
Data transfer: Data transferred “in” to and “out” from Amazon FSx across Availability Zones (AZs) or VPC Peering connections in the same AWS Region is charged at the rate for data transfer within the same AWS Region.
Data transferred “out” from Amazon FSx to another AWS Region (including for copying backups across Regions) is charged at the inter-region rate for the specific inter-region transfer.
File systems and backups
File systems and backups
Different storage options are available based on the redundancy level and the level of throughput desired per TB of storage provisioned
Data transfer within the same AWS Region
Data transferred "in" to and "out" from Amazon FSx across Availability Zones or VPC Peering connections in the same AWS Region is charged at $0.01/GB in each direction.
Cross-region data transfer pricing
Pricing example 1
Assume you have a scratch file system in the US East (N. Virginia) region, which has been provisioned with 4800 GB of storage capacity, and you spin up your file system for an 8-hour workload every day and then shut it down. You do this for 30 days (a month).
Pricing example 2
Assume you have a persistent file system in the US East (N. Virginia) region, which has been provisioned with 4800 GB of storage capacity and per unit storage throughput of 100 MB/s/TiB, and you retain your file system for 30 days (a month) to execute your long-lived workload then shut it down.
Learn more about Amazon FSx for Lustre.
Instantly get access to the AWS Free Tier.
Get started building with Amazon FSx in the AWS Console.