Hi all,
I actually cannot recommend the Amazon S3 implementation of the script. It is not very well thought and done. Some critics:
- The implementation simply does not work on many servers. Many need to use a workaround with the wget command in the CRON Job. Otherwise the CRON Job just fails.
Please see this thread for further information: viewtopic.php?f=19&t=642
- You lose all the google image searches since the image files are hosted on the s3.amazonaws.com domain instead of yoursite.com. Not very good for a image agency ;-/ There would be a possibility to configure a CNAME redirect to a Amazon bucket BUT the buckets name MUST be the same name as the subdomain you intent to use. Sadly, Antons script is adding "-files", "-previews", etc. to the end of each bucket automatically which renders this workaround useless. Big fail! Not very well thought through.
- There is NO possibility to move the files back from S3 to a local server or another Service. You are tight forever to your current cloud provider or you lose your whole Library. Fail! What happens if the service is discontinued? If you need to switch for whatever reason?
I for my part may have to upload thousands of images by hand because of this!
- The suitable Product for this kind of script is NOT S3 from amazon, but Amazon Cloudfront. S3 is made for personal Cloud hosting of files, not for distributed cloud hosting of files for the public or the web. Although it can be used and is used for web hosting sometimes you lose some advantages of Cloudfront like the faster transfer rates etc.
I hope at least some of the issues are getting resolved....