> I also pay only for what I use - which by my estimates will hopefully be less than $30 per month (real data to follow)
Last I checked EC2 was around $70/month minimum just to have your instance running, so unless he plans on manually turning his instance off when he's not using it (which would equate to about half the time) he's going to be spending $70 + bandwidth.
I was actually hoping this would be an article about using EC2 instances as trackers and seeders for distributing your own material as opposed to some lame attempt at piracy.
From the S3 docs:
"Any publicly available data in Amazon S3 can be downloaded via the BitTorrent protocol, in addition to the default client/server delivery mechanism. Simply add the ?torrent parameter at the end of your GET request... "
There's a Webseed extension to Bittorrent that allows you to seed a torrent off a webserver: see http://www.bittornado.com/docs/webseed-spec.txt . It shouldn't be too hard to set up on an EC2 instance if you needed to do so.
I didn't assume that it would be technically difficult, but I thought that an article that took into consideration Amazon's architecture to make a horizontally scalable BitTorrent tracker/seed for high-volume high-availability transfers would be an interesting read.
Last I checked EC2 was around $70/month minimum just to have your instance running, so unless he plans on manually turning his instance off when he's not using it (which would equate to about half the time) he's going to be spending $70 + bandwidth.
I was actually hoping this would be an article about using EC2 instances as trackers and seeders for distributing your own material as opposed to some lame attempt at piracy.