Persistent Storage for Amazon EC2 Services
Talk about serendipity…
I was just talking about using EC2 and S3 for backups and along comes a solution to actually make it easier to build.
Without persistent storage, it would be hard to persist the backed up data to S3 as you’d have to do the file to S3 mapping (I think) by yourself. With this feature, you effectively create a blob of S3 storage and use it as a drive in your EC2 machine instance.
Nice.
Actually, that’s how I thought it worked all along, but was weirded out earlier today when I found out that it didn’t.
Well, as of 9pm tonight it does.
Serendipity.
Categories:
Tags:
0 TrackBacks
Listed below are links to blogs that reference this entry: Persistent Storage for Amazon EC2 Services.
TrackBack URL for this entry: http://www.steve-lacey.com/cgi-bin/mt/mt-bar.cgi/1122
1 Comments
Leave a comment
About Me
Steve Lacey, software developer at Facebook, British, married to the lurvely Nabila, dad to the wonderful Julian and Jasmine. Living in Kirkland (near Seattle), WA.
steve@steve-lacey.com
+1 (425) 214-4716
Syndication
Popular Posts
Recent Entries
Recent Podcasts
- A Brit Abroad - April 16, 2006
- G'Day World!
- A Brit Abroad - November 26, 2005
- A Brit Abroad - October 13, 2005
- A Brit Abroad - September 20, 2005
- The First Britcaster Podcaster
- BritPack number 4 is alive!
- A Brit Abroad - August 15, 2005
- A Brit Abroad - July 13, 2005
- The BritPack #2 - The Very Best Of British Podcasting
- Subscribe...
Monthly Archives
- July 2010 (1)
- May 2010 (3)
- April 2010 (2)
- January 2010 (1)
- December 2009 (1)
- November 2009 (2)
- October 2009 (2)
- September 2009 (1)
- August 2009 (1)
- July 2009 (3)
- June 2009 (2)
- May 2009 (2)
- March 2009 (4)
- January 2009 (3)
- December 2008 (5)
- November 2008 (2)
- October 2008 (2)
- September 2008 (6)
- August 2008 (3)
- July 2008 (6)
- June 2008 (4)
- May 2008 (12)
- April 2008 (16)
- March 2008 (4)
- February 2008 (7)
- January 2008 (11)
- December 2007 (8)
- November 2007 (15)
- October 2007 (8)
- September 2007 (8)
- August 2007 (19)
- July 2007 (9)
- June 2007 (10)
- May 2007 (13)
- April 2007 (11)
- March 2007 (13)
- February 2007 (13)
- January 2007 (19)
- December 2006 (18)
- November 2006 (15)
- October 2006 (15)
- September 2006 (10)
- August 2006 (18)
- July 2006 (24)
- June 2006 (23)
- May 2006 (21)
- April 2006 (23)
- March 2006 (18)
- February 2006 (25)
- January 2006 (36)
- December 2005 (37)
- November 2005 (34)
- October 2005 (37)
- September 2005 (39)
- August 2005 (28)
- July 2005 (33)
- June 2005 (42)
- May 2005 (22)
- April 2005 (40)
- March 2005 (31)
- February 2005 (19)
- January 2005 (25)
- December 2004 (16)
- November 2004 (18)
- October 2004 (26)
- September 2004 (20)
- August 2004 (20)
- July 2004 (23)
- May 2003 (1)
- March 2003 (1)
- February 2003 (2)
- January 2003 (2)
- December 2002 (4)
- September 2002 (4)
- August 2002 (3)
- February 2002 (1)
- January 2002 (9)
- November 2001 (1)
- October 2001 (14)
Categories
Search
About this Entry
This page contains a single entry by Steve published on April 13, 2008 11:56 PM.
Backups Moved To Amazon S3 was the previous entry in this blog.
MarsEdit Now Supports Tags is the next entry in this blog.
Find recent content on the main index or look in the archives to find all content.
Statsorama
- 1050 posts
- 1333 comments
I believe S3 blobs and persistent storage for EC2 are separate but related. You can create S3 blobs of just about anything using a simple web service, and the data is replicated throughout the geographically dispersed S3 environment. Persistent storage, on the other hand, lives in some other NAS-like environment tied to a specific datacenter the EC2 instance is running in. You can, however, take snapshots of your persistent drives, which are then backed up to the geo-dispersed S3 environment.
This all makes some pretty interesting applications possible for drive images. Take an image of a persistent drive used for a database master, then use this image to prefill a new database slave instance with data so you don't need to replicate the entire database before bringing up the slave. Make 1,000 copies of a drive with some scientific database to do massive parallel processing on this dataset with native drive performance on each of 1,000 EC2 instances reading from the dataset. And so on.