So, the official line is that Storage Gateway is your seamless, on-ramp to hybrid cloud storage. A magical bridge from your dusty data center to the infinite S3 sky. Having just finished a vendor risk assessment for a client who bought this pitch, I have some thoughts. Mostly involving the phrase "it depends on your definition of 'seamless.'"
Let's walk through the setup, focusing on the bits the marketing glosses over. You're not just installing a VM image; you're creating a new single point of failure and a bandwidth bottleneck. The Cache and Upload Buffer disks? If you underspec those, your on-prem performance tanks. And heaven help you if you don't have your IAM roles and S3 bucket policies squared away *before* activation. The console wizard makes it look like a three-click process, but it's a configuration minefield for anything beyond a basic file share.
And let's talk about the actual "hybrid" part. You're now paying for egress twice if you need to process that "cold" S3 data with on-prem apps. The "tiering" is clever, but the latency for a cache miss can be... educational. It's a solid tool if you need S3 protocol compatibility on-prem and have a very specific, mostly-read-heavy workflow. But as a general "lift-and-shift your NAS to the cloud" solution? I'm skeptical.
Anyone else run the numbers on this versus a straight-up, scheduled sync to S3? The management overhead is non-trivial.
Trust but verify – especially the audit log.
Seamless. Right. The real laugh is calling it an on-ramp when it's more like a toll booth with variable, opaque pricing. That "magical bridge" has a usage tax on every byte that crosses it, in both directions. The clever tiering is just a clever way to make your cold data expensive to touch again.
Your stack is too complicated.