10 thoughts on “Persistent Storage Boosts Amazon Web Services; Enterprise Ambitions”

  1. I believe that the volumes can not be shared concurrently. While they can be disconnected and then reconnected to a separate instance, they can not be connected to two instances as the same time. Therefore it’s not a “shared drive” but a “portable drive”.

  2. While the cloud storage options such as this can only try to ‘simulate’ true storage, they never can achieve real storage feel that you get with your own dedicated cloud storage. The limitation discussed in this post is just one of the limitations of S3 and EC2. Author needs to discuss this with real users of S3 and EC2 to get a real feel.

    For real storage and backup options, try IBackup.

  3. The storage volumes can only be attached to a single instance at a time for now. However, using the snapshots, one can replicate the data extremely rapidly and mount the copies on many, many instances. No, that’s not read-write sharing across many servers, but doing that is tricky even with all the hardware in the world…

    MichaelMD: we’ve been actually using EC2 and S3 in production for a year and a half now and there is no way I’d go back to a traditional colo or hosting service. Having tested the new storage volumes I have to say that they’ve implemented the important features of SANs. Not all, but the ones that really make a difference and allow us and our customers to build more reliable and more scalable deployments in AWS. If you have your own SAN you might have more features, but you won’t have even close the flexibility of what Amazon offers, and you’d be out a lot more change!

    Thorsten – CTO RightScale – http://blog.rightscale.com

  4. @ Thorsten and other,

    Sorry for the multiple instance error. I might have let the imagination get the better of me. Fixing the problem right now.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.