If you’re running AWS Storage Gateway to bridge your on-premises environment and cloud storage, you’ve probably noticed the bill isn’t just one line item. Between gateway usage fees, storage charges, request pricing, and data transfer costs, a single gateway can rack up charges across four separate billing dimensions — and most teams don’t realize it until the monthly invoice arrives.

Here’s the thing: Storage Gateway isn’t inherently expensive. But it becomes expensive when teams deploy it without understanding the pricing model, leave default configurations in place, or fail to implement lifecycle policies on the underlying storage. According to AWS Prescriptive Guidance, choosing the right gateway type for your workload can mean the difference between $449 and $1,335 per month for the same 10 TB of data.

This guide breaks down exactly where your Storage Gateway costs come from, which configuration decisions have the biggest cost impact, and specific strategies to reduce your bill — whether you’re running S3 File Gateway, Volume Gateway, or Tape Gateway.

Understanding Storage Gateway Cost Components

Storage Gateway billing has three main pillars, and most teams only think about one of them.

Storage pricing covers the underlying AWS storage your gateway writes to. For S3 File Gateway, that’s Amazon S3 pricing. For Volume Gateway, it’s $0.023 per GB-month of volume data stored. For Tape Gateway, virtual tape storage runs $0.023 per GB-month — but archived tapes in S3 Glacier Flexible Retrieval drop to $0.0036 per GB-month, and S3 Glacier Deep Archive costs just $0.00099 per GB-month.

Request pricing is the one that surprises people. Every gigabyte your gateway writes to AWS storage incurs a $0.01 per GB charge — regardless of gateway type. That sounds cheap until you’re writing 5 TB per day across multiple gateways. The first 100 GB per account per month is free, but after that, a gateway writing 10 TB monthly adds $100 in request charges alone.

Data transfer pricing covers data flowing between your gateway and AWS. Data transferred OUT from the Storage Gateway service to your gateway appliance varies by region. If your gateway runs on an EC2 instance in the same region as your storage, that transfer is $0.00 per GB. But on-premises gateways pulling data back from AWS pay standard outbound data transfer rates, which start at $0.09 per GB for the first 10 TB per month.

There’s a fourth cost most teams forget: the infrastructure running the gateway itself. On-premises gateways need hardware — minimum four vCPUs, 16 GB RAM, and dedicated cache/upload buffer disks. EC2-based gateways need instance hours. Neither shows up on your Storage Gateway bill, but both affect your total cost of ownership.

Storage Gateway Pricing by Type: What You're Actually Paying For

The pricing model shifts significantly depending on which gateway type you deploy. Here’s how costs compare for a real-world deployment handling 10 TB of storage in US East (N. Virginia):



Gateway Type

Storage Cost (10 TB)

Gateway Fee

Request Cost (1 TB Written/Mo)

Best For

S3 File Gateway

$449.51/mo (Intelligent-Tiering)

None (S3 rates apply)

$10.24/mo

Scale-out reads, backups, cold data

FSx File Gateway

$503.70/mo (single gateway)

$0.69/hour (~$500/mo)

Included in FSx pricing

Multi-region file access, Windows shares

Volume Gateway

$230/mo (stored data only)

None

$10.24/mo

Block storage, iSCSI, DR snapshots

Tape Gateway

$230/mo (active) / $36/mo (Glacier)

Up to $125/mo

$10.24/mo

Backup archive, tape replacement

Amazon EBS (no gateway)

$1,335.69/mo (GP3)

N/A

N/A

Direct-attached block storage

 

*Note: Pricing from AWS Prescriptive Guidance cost comparison and AWS Storage Gateway Pricing. Actual costs vary by region, storage class, and access patterns.*

A few things jump out from this comparison. S3 File Gateway saves you nearly $900 per month over raw EBS for the same 10 TB — but only if you’re okay with object-level access and can tolerate the S3 consistency model. FSx File Gateway costs more upfront than S3 File Gateway, but eliminates the need for a second Amazon FSx file system in multi-region deployments, which could save $180 per month or $2,100 annually by avoiding duplicate infrastructure.

Tape Gateway is the standout for pure archival. If you’re replacing physical tape infrastructure, moving 10 TB to S3 Glacier Deep Archive through Tape Gateway costs under $10 per month in storage — plus the gateway write charges. Compare that to maintaining an on-premises tape library, and the math is clear.

Five Strategies to Reduce Your Storage Gateway Bill

1. Implement S3 Lifecycle Policies Aggressively

If you’re using S3 File Gateway, your biggest optimization lever is storage class transitions. Most teams store everything in S3 Standard by default and never move it. But data that hasn’t been accessed in 30 days is a perfect candidate for S3 Infrequent Access (IA) — and data untouched for 90 days should be in Glacier.

AWS Prescriptive Guidance recommends using S3 Intelligent-Tiering with File Gateway because it automatically moves objects between access tiers without retrieval fees. The result: an 80/10/10 split across Standard, IA, and Glacier tiers reduces your effective storage cost by roughly 40% compared to keeping everything in Standard.

But there’s a catch practitioners on Reddit have flagged. One r/aws thread from June 2025 reported unexpectedly high HEAD/GET request charges on buckets linked to Storage Gateway with IA objects. The culprit? Client-side activity — antivirus scans, backup software, and directory enumeration tools continuously accessing IA objects and triggering retrieval fees. Before enabling IA transitions, audit what’s reading your files through the gateway.

2. Control Versioning-Driven Cost Bloat

This one is a silent budget killer. If your S3 File Gateway writes to a versioning-enabled bucket, every file modification creates a new object version. Here’s why that’s expensive: File Gateway performs incremental uploads based on modified data, modified metadata, and multipart uploads of larger files. In a versioned bucket, a single file edit can create multiple object versions.

According to AWS re:Post, this is one of the top reasons Storage Gateway bills increase unexpectedly. The fix: configure lifecycle rules that expire non-current object versions after a defined period. Seven days is reasonable for most workloads — 30 days if you need rollback capability. If you don’t need versioning at all for your File Gateway bucket, turn it off.

3. Right-Size Your Gateway Infrastructure

Every gateway needs allocated resources — cache storage, upload buffer, and compute. Over-provisioning these costs money directly (if on EC2) or in hardware utilization (if on-premises).

For cache sizing, the sweet spot is matching your cache disk to your active working set — the data accessed most frequently. AWS recommends at minimum 150 GB for cache storage, but many teams allocate 500 GB or more “just in case.” Track your `CacheHitPercent` CloudWatch metric. If it’s consistently above 80%, your cache is oversized and you’re paying for storage you don’t use. If it’s below 60%, you need more cache — because cache misses trigger data retrieval from AWS, which incurs transfer costs.

For EC2-based gateways, right-size the instance. A gateway handling light file-sharing workloads doesn’t need an m5.2xlarge. Start with an m5.xlarge (4 vCPUs, 16 GB RAM) and scale up only if you see performance degradation in your ReadBytes and WriteBytes metrics.

4. Consolidate Gateways Where Possible

Each gateway you deploy adds infrastructure overhead — compute costs, network bandwidth, and operational complexity. Teams often deploy multiple gateways because they started with separate proof-of-concept deployments or because different teams spun up their own.

Before adding another gateway, check whether an existing one can handle the additional workload. A single S3 File Gateway can support up to 10 file shares. A Volume Gateway supports up to 32 volumes. If you have three gateways running at 30% capacity each, consolidating to one or two gateways running at higher utilization saves both infrastructure costs and management time.

*Note: There’s a ceiling here. AWS limits each gateway to a maximum throughput, and high-throughput applications may genuinely need multiple gateways. Monitor your gateway’s bandwidth utilization before consolidating.*

5. Audit Data Transfer Patterns

Data transfer is the cost component that scales most unpredictably. Two scenarios consistently drive up transfer costs:

Excessive reads from cloud storage. When applications behind a File Gateway access files that aren’t in the local cache, the gateway pulls them from S3 — incurring data transfer OUT charges. If your workload reads the same files repeatedly but your cache isn’t sized to hold them, you’re paying transfer charges on every access.

Cross-region gateway deployments. If your gateway runs on-premises or in a different region from your target S3 bucket, all data transfer goes over the internet (or Direct Connect). Moving a gateway to the same region as its storage — or deploying it on EC2 in that region — eliminates inter-region transfer costs entirely. AWS confirms that data transfer from Storage Gateway to an EC2-based gateway in the same region is $0.00 per GB.

When Storage Gateway Costs More Than It Saves

Storage Gateway makes economic sense when it replaces more expensive alternatives — on-premises storage hardware, multiple Amazon FSx file systems, or manual tape management. But there are scenarios where it adds cost without sufficient benefit.

You’re only using it for backup, and your data never comes back. If files flow one way — from on-premises into S3 — and you never read them through the gateway, you might not need a gateway at all. AWS DataSync handles one-way transfers more efficiently for bulk data movement, and tools like the AWS CLI S3 sync command work for smaller datasets without the ongoing gateway infrastructure overhead.

Your working set exceeds practical cache size. If 80% or more of your reads hit cloud storage rather than local cache, you’re effectively paying gateway infrastructure costs on top of full S3 data transfer costs. At that point, direct S3 access from your applications — or mounting an FSx file system directly — may be cheaper.

Your on-premises hardware is approaching end-of-life. Running a gateway requires maintained infrastructure. If you’re facing a hardware refresh cycle anyway, evaluate whether migrating fully to cloud-native storage (S3, EFS, or FSx) eliminates both the gateway and the hardware cost.

The decision framework comes down to a simple calculation: total gateway cost (infrastructure + storage + requests + transfer) minus the cost of what it replaces (duplicate infrastructure, tape libraries, or direct-to-S3 bandwidth). If that number is positive, the gateway is costing you more than the alternative.

Optimize Your Cloud Bill with nOps

Storage Gateway is just one piece of your overall cloud storage bill. Here at nOps, we see teams spending significant portions of their AWS budget on storage services — S3, EBS, EFS, FSx, and the gateways connecting them — without visibility into what’s driving those costs or whether their configurations are optimal. Our platform was built to help, with:

 

  1. Full cost visibility across AWS, Azure & GCP
  2. Commitment Management that automatically optimizes your savings and reduces your risk
  3. Free Savings Analysis so you can find out in just 30 minutes whether you’re fully optimized.

 

If you’re looking for visibility into where your storage costs are going and automated optimization for the compute side of your bill, schedule a demo with one of our AWS experts.

 

nOps optimizes $4 billion in cloud spending and is was recently ranked #1 in G2’s Cloud Cost Management category.