AWS Storage Gateway cost: you pay for the AWS storage it fronts

Quick answer

Storage Gateway bills mostly for the AWS storage it fronts, S3 for File Gateway, EBS snapshots for Volume Gateway, or archival storage for Tape Gateway, plus requests, retrievals, and data transfer, and on some configurations a per-gateway fee. The gateway software itself is low-cost; the backing storage and retrieval charges are the bill, so the same S3 and snapshot cost levers apply.

AWS Storage Gateway bridges on-premises applications to AWS storage, presenting S3, EBS snapshots, or virtual tape libraries through familiar protocols (NFS, SMB, iSCSI). Its cost is mostly the AWS storage behind it, so understanding Storage Gateway cost means understanding the storage service it uses.

The backing storage is the bill

Gateway type	Backing storage
File Gateway	S3 (any storage class)
Volume Gateway	EBS snapshots in S3
Tape Gateway	S3 and archival (Glacier) as virtual tapes

For File Gateway you pay S3 storage rates for what you store, plus request and retrieval charges. Volume Gateway costs EBS snapshot storage. Tape Gateway costs S3 and Glacier storage for virtual tapes plus retrieval. On top, some configurations add a small per-gateway or data-written fee, but the storage dominates.

The same storage levers apply

Because the bill is really S3 or snapshot storage, the optimizations are the same: choose the right S3 storage class for the access pattern, apply lifecycle policies, and manage snapshot retention for Volume Gateway. Retrieval costs matter for archival tiers, so match the tier to how often data is actually read.

When Storage Gateway fits

Storage Gateway earns its place for hybrid scenarios: on-premises applications that need AWS-backed storage with local caching, backup and archive to AWS, or migration. If your workload is already in AWS, using S3 or EFS directly avoids the gateway layer. Reserve Storage Gateway for genuine hybrid needs, and optimize the backing storage as you would any S3 or snapshot cost.

FAQ

How is AWS Storage Gateway priced?

Mostly by the AWS storage it fronts: S3 rates for File Gateway, EBS snapshot storage for Volume Gateway, and S3 plus archival storage for Tape Gateway, along with request, retrieval, and data transfer charges. Some configurations add a small per-gateway or data-written fee, but backing storage dominates.

What is the main cost of Storage Gateway?

The AWS storage behind it, not the gateway software. For File Gateway that is S3 storage plus requests and retrievals; for Volume Gateway, EBS snapshot storage; for Tape Gateway, S3 and Glacier for virtual tapes plus retrieval. Optimizing that storage optimizes the bill.

How do I reduce Storage Gateway cost?

Apply the same storage levers as the backing service: choose the right S3 storage class for File Gateway, use lifecycle policies, manage snapshot retention for Volume Gateway, and match archival tiers to retrieval frequency for Tape Gateway. Retrieval costs matter for cold tiers.

Should I use Storage Gateway or S3 directly?

Use Storage Gateway for hybrid scenarios, on-premises applications needing AWS-backed storage with local caching, backup and archive to AWS, or migration. If the workload already runs in AWS, S3 or EFS directly avoids the gateway layer and its overhead.

Does Tape Gateway retrieval cost extra?

Yes. Tape Gateway stores virtual tapes in S3 and archival storage like Glacier, and retrieving from archival tiers incurs retrieval charges and latency. Match the archive tier to how often tapes are actually restored so you do not pay high retrieval costs on frequently-accessed data.

Does C3X estimate Storage Gateway cost?

C3X prices the backing S3 and snapshot storage that Storage Gateway uses from your Terraform, which is where most of the cost is. Data written and retrieved depend on usage, which you provide as assumptions.

What to do next

Price the storage behind your gateway before you deploy. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.