Skip to content
Calcrivo

FSx Storage Calculator

Cost an FSx file system from SSD capacity, throughput capacity, backups, Multi-AZ and deduplication savings.

Inputs

GB
USD per GB-month
MBps
USD per MBps-month
GB
USD per GB-month

Multi-AZ mirrors capacity and throughput into a second Availability Zone, modelled here as a 2x multiplier.

%

Monthly File System Cost

$3,717.76

Storage Capacity Cost

$1,064.96

Throughput Capacity Cost

$2,252.80

Backup Cost

$400.00

Logical Data It Can Hold

7,447GB

Cost per Logical GB

0.4992USD per GB-month

Step by step

  1. Values used

    Provisioned storage capacity = 4,096 GB; SSD storage price = 0.1300 USD per GB-month; Provisioned throughput capacity = 512 MBps; Throughput capacity price = 2.20 USD per MBps-month; Backup data retained = 8,000 GB; Backup storage price = 0.0500 USD per GB-month; Deploy Multi-AZ = Yes; Data deduplication and compression savings = 45 %

  2. FSx Storage

    cost = (GB x storage rate + MBps x throughput rate) x Multi-AZ factor + backup GB x backup rate; logical capacity = GB ÷ (1 − dedup ratio).

  3. Monthly File System Cost

    = 3,717.76

  4. Storage Capacity Cost

    = 1,064.96

  5. Throughput Capacity Cost

    = 2,252.80

  6. Backup Cost

    = 400.00

  7. Logical Data It Can Hold

    = 7,447 GB

  8. Cost per Logical GB

    = 0.4992 USD per GB-month

How it works

FSx bills provisioned capacity and provisioned throughput as two independent dials, and throughput capacity also determines the file server's network and cache limits rather than only its bandwidth. Multi-AZ mirrors both dials into a second Availability Zone, so it roughly doubles the compute and storage line before backups are counted. Deduplication is what makes the real cost per logical GB far lower than the sticker rate on general-purpose file shares — and every rate here is a user-supplied list price to confirm on the AWS FSx pricing page for your region. Throughput capacity is usually the surprise on an FSx bill: at a couple of dollars per MBps-month it can outweigh the storage line entirely, and it is the one dial teams over-provision by habit.

Formula

FSx Storage

cost = (GB x storage rate + MBps x throughput rate) x Multi-AZ factor + backup GB x backup rate; logical capacity = GB ÷ (1 − dedup ratio).

MBps
Provisioned throughput capacity, which also sets network and cache limits
dedup ratio
Fraction of bytes removed by deduplication and compression

Frequently Asked Questions

How is FSx Storage calculated?

cost = (GB x storage rate + MBps x throughput rate) x Multi-AZ factor + backup GB x backup rate; logical capacity = GB ÷ (1 − dedup ratio). FSx bills provisioned capacity and provisioned throughput as two independent dials, and throughput capacity also determines the file server's network and cache limits rather than only its bandwidth. Multi-AZ mirrors both dials into a second Availability Zone, so it roughly doubles the compute and storage line before backups are counted. Deduplication is what makes the real cost per logical GB far lower than the sticker rate on general-purpose file shares — and every rate here is a user-supplied list price to confirm on the AWS FSx pricing page for your region.

Why does FSx Storage matter?

Throughput capacity is usually the surprise on an FSx bill: at a couple of dollars per MBps-month it can outweigh the storage line entirely, and it is the one dial teams over-provision by habit.

What values do I need to enter?

This calculator takes 8 inputs: Provisioned storage capacity, SSD storage price, Provisioned throughput capacity, Throughput capacity price, Backup data retained, Backup storage price, Deploy Multi-AZ, Data deduplication and compression savings. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Does throughput capacity affect anything besides bandwidth?

Yes. It sizes the file server's memory cache and network throughput too, so raising it can improve metadata-heavy workloads even when the raw bandwidth was never the bottleneck.

You might also need