Certablo
Sign inCreate account
← Knowledge Base
Storageservice

AWS Storage Gateway

Hybrid storage that connects on-premises applications to AWS storage through file, volume and virtual-tape interfaces while retaining local caching where the gateway model requires it.

CLF-C02

Visual overview

HYBRID STORAGEKeep a familiar on-premises interface while the gateway connects data to AWS-backed storage
01Local clientExisting file, block or backup application
→
02GatewayFile · Volume · Tape interface
→
03Local cacheLow-latency working data according to gateway type
→
04AWS storageCloud-backed durable storage and archive workflows
FileNFS / SMB-style accessBlock + tapeiSCSI volumes or virtual tape library
Storage Gateway exists to bridge an on-premises storage interface with AWS. Native cloud workloads normally use the target AWS storage service directly.
AWS SERVICE MAPTranslate local storage protocols to AWS

A gateway presents familiar interfaces locally while AWS supplies the cloud-backed data layer.

GatewayNFS / SMB / iSCSI
Amazon S3Cloud object layer
S3 GlacierTape archive target
EXAM-RELEVANT MECHANICS

Technical reference

Gateway type follows the protocol the existing on-premises application understands.

S3 File GatewayNFS / SMB → S3

Presents file shares while storing data as S3 objects.

Volume GatewayiSCSI block

Presents cloud-backed iSCSI volumes.

Tape GatewayiSCSI VTL

Presents virtual tape drives/media changer to existing backup software.

Local componentGateway + cache

Local protocol access and cache bridge applications to AWS storage.

A bridge between familiar on-premises storage interfaces and AWS

AWS Storage Gateway is a hybrid cloud storage service that connects on-premises environments with AWS storage. The gateway presents storage interfaces that existing applications understand while moving or backing data into AWS-managed storage. This is useful when an organization cannot rewrite every application to call cloud APIs directly but still wants cloud-backed capacity, archive or recovery workflows.

The gateway architecture usually includes a software or hardware appliance close to the workload and a local cache or buffer according to gateway type. Data is then transferred to AWS services in the background. This local component is important: Storage Gateway is designed to bridge environments, not simply to provide a new name for S3, EBS or a VPN connection.

File Gateway

S3 File Gateway provides file-based access to objects stored in Amazon S3. Clients can use familiar file-sharing protocols while the gateway maps files to S3 objects and keeps frequently accessed data in local cache. This is useful for hybrid file workflows, backups, data ingestion and environments where applications need file semantics on premises but the durable backend should be S3.

The mapping is not the same as replacing a high-performance local NAS with an infinitely fast cloud file server. Network connectivity, local cache behavior and the semantic mapping between files and objects affect the workload. File Gateway is strongest when its hybrid access pattern and S3 backend are deliberate architecture choices.

Volume Gateway and Tape Gateway

Volume Gateway presents iSCSI block volumes to on-premises applications. Cached-volume configurations keep the primary data in AWS-backed storage while caching frequently accessed content locally; stored-volume patterns retain primary data locally while asynchronously backing it up to AWS. The two modes reflect different priorities for local working sets and cloud-backed protection.

Tape Gateway presents a virtual tape library interface to existing backup software. It lets organizations retain tape-oriented backup workflows without managing the same quantity of physical tape media. Virtual tapes can participate in cloud archive storage while backup applications continue to interact through familiar virtual tape drives and media-changer concepts.

When hybrid storage is the requirement

Storage Gateway is most useful when an on-premises workload, legacy interface or local-latency requirement must coexist with AWS storage. It can support staged migration, centralized backup, cloud archive and hybrid data processing without forcing every application to change its storage protocol at once.

If an application already runs natively in AWS and can directly use S3, EBS, EFS or FSx, adding a gateway may be unnecessary. The gateway exists to solve the boundary between environments. Start with the reason local clients cannot or should not access the target AWS storage model directly, then choose the gateway interface that preserves what they need.

Key takeaways

  1. 01

    Storage Gateway connects on-premises applications with AWS-backed storage through familiar interfaces.

  2. 02

    File Gateway maps file access to cloud object or managed-file backends while using local caching.

  3. 03

    Volume Gateway presents iSCSI block storage; Tape Gateway presents a virtual tape library for backup workflows.

  4. 04

    Use a gateway for a genuine hybrid boundary; native AWS workloads should usually access native storage services directly.

Official AWS sources

Use these primary AWS resources for the source material behind this article and for deeper reference.