- Storage Gateway is ideal to use a migration product or extend the capacity of the on-premises storage.
- There are three different architectures; file, volume and tape gateway.
- Historically, you’d do regular backups to physical tape devices, dedicated for backup and restores. You can integrate Storage Gateway with your existing backup. You can configure an ISCSI interface and virtual tape shelf and mounts to Glacier. You can perform the live backup of the data and Storage Gateway would asynchronously replicate the data to S3, and then over to Glacier.
- File Gateway accesses the filesystem via SMB or NFS, useful if you have a large on-premises filesystem and you either extend or use as a first step before migration. File Gateway essentially orchestrates in between your on-premises filesystem and S3 object storage where objects will have the same name as the file path, 1to1 mapping.
- Block storage volumes, you can extend! Two key criteria is the capacity of storage on premises you have and how often you need to access certain data.
- Gateway Stored: That’s where you would have the primary storage within your storage device and you utilise S3 for snapshots.
- Gateway Cached: The primary storage is actually in S3 with snapshots going in there, only the cache is stored on-premises.