Introducing Transfer Appliance: Sneakernet for the cloud era
cloudplatform.googleblog.com
cloudplatform.googleblog.com
Coincidentally, Starbuck's first shipping container store is just a mile or two from Amazon's first use of the Snowmobile.
The data is encrypted, so that part is really just to impress the commoner.
Disclosure: I work on Google Cloud (but didn't work on this)
[1] https://3.bp.blogspot.com/-SnFabcStXhM/WW4SEhj6adI/AAAAAAAAE...
(work at G but not in any of these areas)
The aws way of doing this is nice: You rent the appliance like when importing data to the cloud and pay a (reduced) "bandwidth" fee for exporting the data to the appliance which will be shipped to you.
Another idea would be for GCP to handle export to a physical device and that device would be shipped to a known location (to both GCP and the client) and accessible by either but offline and cold stored. And similar to how paper records are stored you could put in a request to access the records and thereby verify their existence (which you can't do with cloud data other than the copy that you are able to access).
Fwiw, Iron Mountain lost about 60 physical records file boxes that we had ..
It likely wouldn't be very expensive to get a very high-capacity fiber connection going between GC/AWS datacenters in relative physical proximity.
Not expressing a particular/immediate personal need here, just noting that this could help keep the lock-in factor down and level of competition up.
I understand's Google's bias here but doesn't it usually make more sense to bring the programs/models to where the data already is?
It would be funnier if you could keep it indefinitely, but reads were $0.12/GB. ;)
I wonder if that's a viable business model...
(Disclosure: I work on GCP but this is a personal, not professional, endorsement)
https://www.synology.com/en-uk/knowledgebase/DSM/help/CloudS...