Question about the development of this module

Are you aware that the EC2 instances can be terminated at any time? I know some people handle this by simply making several backups a day and dump it on S3. Still, it can be very inconvenient for your business. What do you think?

Well, it depends what your goal is. If you're looking for one site environment than yes, it's not stable. However AWS come up very soon with Persistent storage, where you can assemble volumes on fly with RAID config and attach them to any instance.

But if you build the stable system, self curing and auto scaling with many servers - that's the perfect and not expensive solution for start up.

Right now I'm playing with https://www.scalr.net/faq.php. You can build the 'farm' with balance loaders, application servers and mysql servers. Mysql is pretty neat. You can have Master-slave servers with snapshot backup to S3 every minute. So that's stable. Application server (where Drupal resides) can rsync to S3 or wait until Scarl releases new option to sync content between servers (instances) in the farm. Thus one server fails it's automatically re imaging and syncing the content with other instances. In my scenario I have 1 web server, 2 mysql and 1 application instances. Of course you can double it and that can be 100% fault tolerant.

What I'm looking for is to leverage the static files (Drupal's 'files' folder) to S3 buckets. Thus I don't need to worry about backups and space expansion strategies. I thought if you can control it from Drupal's module will be really great.

Ok, I didn't know you were that knowledgeable on aws. I looked briefly to scalr as well but decided it is not mature yet to use it myself.
Anyway, what you are looking for is simply a driver for the Drupal file API which stores the data on S3 rather than in the local files folder.

I know dopry started with developing a file API which included drivers for s3, about 1,5 year ago. Don't know what the status is actually, but I have the feeling it never got out of development (no release).

The AWS_S3 module is an API for s3 but has not interface with the drupal core filesystem. Thats all I know and what I can say.

I'm not available for development work but I am curious for the result of this request. I would love to test it.

I let you know if I find some way to S3.

@autonetex

May I ask what S3 driver you eventually use for your Drupal websites running on EC2?

What is the current status and road map for this module? Is there a time frame for the first stable release? Any bounties of relevance for the development speed?

I have the feeling it has been abandoned. However, autonex is still active. I presume he will be reading this, so one of the possible solutions is to offer the module for adoption. Is that an option?
Edit: oops, the module is developed by DragonWize and not autonex. I was a bit hasty with my conclusions.

Sorry about the late response. I've been out the last 2 days, presidential inauguration in the US.

I have not abandoned the module but have not had much time to work on it of late. I have planned to get back into it and get a first release out in the next couple months if time permits. I've been focusing my efforts lately on working on D7 and better wysiwyg and format support.