Drupal Answers is a question and answer site for Drupal developers and administrators. It only takes a minute to sign up.
Sign up to join this community
I'm developing a Drupal 7 website that will be served from multiple servers behind a load balancer.
I want all static files generated by Drupal cache (JS, CSS, and also theme and modules images) to be served via an Amazon S3 bucket.
I already did this for my content types' file upload fields, using the Amazon S3 module, but it's missing the feature I described above.
I saw there's Media Mover module, but it's far from D7 production ready.
What other solutions are there?
I ended up using the S3AutoPush module. I migrated it to Drupal 7 and hacked the hell out of it to make it fit my needs.
If anyone reads this and is interested, I'd be happy to share my code. I won't put it on drupal.org for now since it's a real hack-job and not worthy yet.
Other Drupal 7 modules like the File API do this. However I have more experience with the Amazon S3 module.
The Drupal 7 AmazonS3 module still doesn't handle JS/CSS. There is a patch for this, however it's status for the past year has been set to "Needs work", because of the following response by Andrew Berry:
I see a few issues with this patch as-is: 1. It's possible to have two file records for the same file, under different paths. For example, public://bucket/image.jpg and s3://bucket/image.jpg. For managed files, this could lead to data corruption. 2. We had to patch quite a few modules for the S3 wrapper to work properly, since it requires a bucket in the URL. I imagine a ton of modules hardcode public:// file paths without normalizing the URL. 3. There's a performance issue in that S3 can be very slow to create new assets and do an initial stat. For image styles, we basically replaced the style generation with our own code, which is a pain to do for CSS and JS. And, we could have very similar problems with contrib modules.
Anyways, if we can address all of these I'd be interested in getting this in. However, I'm guessing to do this it a way that doesn't break all the things will have to wait for D8.
Speaking of Drupal 8, there is an s3 module by @cweagans that already handles aggregated CSS/JS files as well: https://www.drupal.org/project/flysystem_s3 Hopefully this will be helpful to someone.
It's the good advice that you just didn't take:
Don't place your images/css/js files on Amazon S3 storage since this will complicate the hell out of your Drupal installation, specially when it comes to synchronizing. You'll find a solution for sure, but it will be ugly.
Use a reverse proxy on your static content directly on your production server. You can separate the images/css/js on a separate static subdomain (eg. assets.yourdomain.com). You could utilize Static Server Drupal Module for this.
Use Amazon S3 for a higher purpose, like ec2 snapshot backups, database backups, etc.
