Disclaimer: I work on Compute Engine.
Disclaimer: I work on Google Genomics.
We ended up moving towards AWS because they were willing to sign. It sucked from my perspective because we already had such a tie in with Google with our email/ collab platform.
In the couple years since then our agreements have only gotten stronger.
The best way for Google to address this is to sign something with Internet2 and then the institutions can use that contract instead of negotiating separately.
(The other terms were a bit easier to google)
Here are the other terms:
HIPAA: the acronym for the Health Insurance Portability and Accountability Act that was passed by Congress in 1996
PHI: Protected health information
Edit: link to relevant definition http://searchhealthit.techtarget.com/definition/HIPAA-busine...
Basically an agreement between organizations that there is an understanding that PHI (protected health information) is at stake and that both parties are aware of their obligations to protect it.
http://googlecloudplatform.blogspot.com/2015/11/introducing-Custom-Machine-Types-the-freedom-to-configure-the-best-VM-shape-for-your-workload.html
Which would let you adjust your RAM to vCPU ratio (as low as ~1 GiB per vCPU and up to 6.5).Disclaimer: I work on Compute Engine.
Frankly, CPU-hours and TB-years are still within 5-10% of the total cost providing sequencing results to the patients. What is really important is that the cloud allows us to determine exactly our cost-per-analysis without paying for excess capacity or maintenance.
What matters also is reliability, redundancy, and peak capacity, where the cloud (both Google and the other provider) win hands down.
Disclaimer: I work on Compute Engine.
Taking this to the extreme, you might even fire up a Windows VM so you could run some analysis or reporting tool there (say, Tableau), within GCP and then only need to egress the Dashboard or Report that it generated. You'd still have the raw data, but you would only be paying to store it. Especially if you're only keeping it around for archival purposes you could put it in a Nearline bucket and really minimize your costs.
(note: I work on GCE)
I bet your university has hundreds of computers idling at night - why not use them?
The biggest challenge we face is data protection. Sequencing data is not considered protected health information so theoretically HIPAA regulations do not apply, but this may change in future so nobody is willing to take responsibility. If sequencing data is considered PHI, HIPAA requires a BAA between the institution and Google. The process of getting these in place was so convoluted and difficult that it was just easier to use another provider more closely associated with our institution.