Archive for February, 2009

j3ffyang @ twitter

  • Share/Bookmark

Comments off

j3ffyang @ twitter 2009-02-26

  • Share/Bookmark

Comments off

Build My Private Open Source Cloud Computing with Eucalyptus

Building a private open source’d Cloud Computing environment isn’t that difficult as you think. Get the code from http://eucalyptus.cs.ucsb.edu and it took me about 3~ 4 days @ my spare time to complete the installation and configuration. This environment shares code with Amazon Elastic Compute Cloud (EC2), which means your Amazon Machine Image (AMI) can run on top of this.

Look @ some screenshots

euca_credential1

euca_usr

euca_config

  • Share/Bookmark

Comments off

AWS Case Study – MedCommons

Source: http://aws.amazon.com/solutions/case-studies/medcommons/

MedCommons, a health records services provider, gives consumers direct access to their medical information (via web browser or Web service APIs) and allows an easy way to share this information with healthcare providers. These services are evidence of a major healthcare trend in which consumers are taking control of their health and assuming ownership of their healthcare records.
MedCommons

One of MedCommon’s offerings, HealthURL is a personal account hosted on Amazon Web Services. MedCommons HealthURL provides a web-based storage repository for consumers to store and share access to their health records. These temporary or long-term accounts live on Amazon S3 where they meet HIPAA requirements of security and redundancy.

“We choose AWS because of their reputation and the scalability of their solution,” states Adrian Gropper MD, Co-founder and Chief Science Officer. “We use Amazon S3, EC2, Elastic IP to store and host individual HealthURL accounts. Compared to traditional hosting providers, Amazon EC2 was easy to set up and pretty inexpensive. The fact that there’s no bandwidth costs between our gateways and long term storage servers will be a huge cost savings.”

With HealthURL, consumers can open an account and upload PDF files, DICOM imaging, CCR information, and other relevant medical data. Then, using credentials, patients can share access with family members, physicians, specialty providers, large hospital networks, or even employers. The patient maintains control of their identity and privacy by granting or revoking access to others as needed.

HealthURL accounts are a $2/month subscription plus a hosting fee. To determine the hosting fee and charge the subscription cost, MedCommons utilized Amazon DevPay to charge and meter customer usage. “DevPay tracks the actual storage and communications expenses for very large diagnostic imaging objects as well as service fees to be paid by the patient/consumer. This billing system saves a great deal of work and enables our transactional business model to compete with the ad-supported model of Google and Microsoft.”

MedCommons also utilizes Amazon FPS to manage direct and third party billing transactions between consumers and MedCommons or patients and doctors. Both Amazon FPS and DevPay allow MedCommons’ customers to simply pay using the existing payment information stored in their Amazon.com account.

With a scalable solution in place, MedCommons also had to consider HIPAA compliance of their application. “Our app was designed to be hosted in the cloud and patient-centric from the ground up. In order to be HIPAA compliant, we had to design our application to allow careful identity management, detailed activity logs, a secure console system that facilitates audit of users and accounts, a clear access consent mechanism, and a locked down app deployment procedure that provides a minimum attack surface—encryption and SSL certificates.”

“We have saved many man-years of work by going with AWS for our in-the-cloud, on-demand healthcare information service. The capability of usage-based pricing at the patient level adds commerce capabilities not available anywhere else. The confidence in the Amazon brand by consumers everywhere makes it our best choice for in-cloud storage and computing,” says MedCommons’ CEO Bill Donner.

  • Share/Bookmark

Comments off

Does Amazon S3 really save money?

Source: http://news.ycombinator.com/item?id=422225

With a price tag of $0.150/GB/month, storing 1TB of data costs around $150/month on Amazon S3. But this is a recurring amount. So, for the same amount of data it would cost $1800/year and $3600/2-years. And this doesn’t even include the data transfer costs.

Consider the alternative, with colocation the hardware cost of storing 1TB of data on two machines (for redundancy) would be around $1500/year. But this is fixed. And increasing the storage capacity on each machine can be done at the price of $0.1/GB. Which means that a RAID-1+redundant copies of data on multiple servers for 4TB of data could be achieved at $3000/year and $6000/2-years in a colocation facility. Whereas on S3 the same would cost $7200/year and $14,400/2-years.

Also, adding bandwidth+power+h/w replacement costs at a colocation facility would still keep the costs significantly lower than Amazon S3.

Given this math, what is the rationale behind going with Amazon S3? The Smugmug case study of 600TB of data stored on S3 seems misleading.

I do see several services that offer unlimited storage which is actually hosted on S3. For example, Smugmug, Carbonite etc. all offer unlimited storage for a fixed annual fee. Wouldn’t this send the costs out of the roof on Amazon S3?

If your startup is using Amazon S3 for its storage needs, for the benefit of the startup community, can you please elaborate your rationale for choosing this service?

  • Share/Bookmark

Comments off